Get started
What Hypervibe will do for a builder, what you will need, what is not available yet and the path through this section.
On this page
Hypervibe is the fully managed agentic factory. You describe a change you want; it plans the work, does it, has it checked independently and shows you what it cost. This page follows one builder from a goal to a decision, then lists what you will need and what is missing.
You hand over a goal with its terms and get back a decision to make #
You start by giving Hypervibe four things: a goal, the authority to act, a budget and a definition of done. The goal, the budget and the definition of done are written into a commission: what the task must achieve and the terms it runs under, fixed before any work starts. The authority is a set of grants, and each grant is checked again where its effect happens, never taken on trust from an earlier step.
Rocket!, the agent engine, plans the change, reads your repository, edits code and calls tools under the approvals you give. An approval is bound to the exact effect it allows, so what you approve is what runs. Throttle admits and routes every model call and holds every credential, so the agent never holds one. Throttle is designed to be provider-neutral: it serves every provider and model it supports, and it refuses a model its catalogue does not list.
When Rocket! proposes a change, Reactor runs the commission's checks on that exact change, called the candidate, through a verifier that did not write it. You then accept or reject the candidate. One receipt shows the full cost of the run, and any part of the cost that is not known yet reads Unknown, never zero.
Each step has one owner #
| Step | Who acts | What you see |
|---|---|---|
| Commission | You | A card with the objective, the source at an exact revision, the recipe, the budget, the receiver and the verifier |
| Work | Rocket! | The conversation, the plan, and approval prompts that show the exact effect |
| Inference | Throttle | Every model call admitted, routed and settled, with the credential kept away from the agent |
| Attention | Lanes | The running work and anything waiting for you, in one place |
| Verification | Reactor | A verdict on the exact candidate: pass, fail, inconclusive or error |
| Decision | You, as the receiver | Accept or Reject on the Result card |
| Cost | Hypervibe | One run receipt for the whole run |
Hypervibe itself holds identity, configuration and grants, and each component keeps its own records.
You will need a Linux machine, a model account and a repository #
The first release is designed for one person working alone and for teams. For the single-person profile, called Just me, you will need:
- a Linux machine on x86-64;
- an account with a model provider that Throttle supports, whose credential Throttle keeps;
- a Git repository to enroll.
The first release is planned to include every provider Throttle supports, not one provider first. The single-person record runs on Claude with an API key, and each other provider is planned to qualify by its own conformance tests and one recorded live call.
Just me has no sign-up and no sign-in. Joining a team adds an invitation and a Google account, and running a team server adds PostgreSQL 16. Choose a profile compares the options.
Several things are not available yet #
- No release, install command or download exists. A release page will list them, with their evidence, when they do.
- The first release targets Linux on x86-64 only. Unavailable macOS and Windows are not part of the first release. The phone companion comes after it.
- Tiles, which show several pieces of running work side by side, are not in the first release. Neither are connectors such as GitHub, Google and Linear, or a server hosted by Hypervibe.
Four pages take you from a choice to a receipt #
- Choose a profile: how the machine will be used, and what each use needs.
- Install: what the installer will change, and how diagnosis, updates and removal work.
- First verified change: the first run, step by step.
- Read a receipt: verdicts, decisions and cost.
Where to go next #
- Products describes each component and what it owns.
- Architecture explains how the parts fit together and who decides what.
- Standings explains what each standing on these pages means.
- Glossary defines the product's words.