Choose a profile
The ways Hypervibe is designed to be set up on a machine, who each one is for, what each needs and which evidence each still lacks.
On this page
A profile says how a machine will be used. It decides which parts of Hypervibe run there, which records stay on the machine and whether anyone signs in. You choose a use, not a list of programs, and the installer works out what that use needs.
The first release is built for four profiles #
The installer's first question, "How will you use this machine?", offers Just me, joining a team, or a build or agent machine for a team. A team server is set up by its own explicit choice.
| Profile | Who it is for | What this machine does | Sign-in |
|---|---|---|---|
| Just me | One builder working alone | Runs Rocket! and Throttle for you and keeps your commissions and settings here; Reactor verifies each candidate | None: your operating-system account is who you are, and other accounts on the machine are refused |
| Team member | A person a team has invited, including people from outside its own domain | Runs Rocket! for you and keeps your commissions here; team settings come from the team server, and model calls use the team's shared pool | Sign in with Google after accepting an invitation |
| Team server | A team owner or administrator | Holds the team's people, devices and shared settings, and the shared inference pool with its credential; runs no agent or build work | Members sign in with Google; there are no passwords |
| Build or agent machine | A team administrator adding a machine for the team's builds and checks | Runs the build and verification jobs Reactor admits for the team, under a machine identity rather than a person's | An enrollment code from the team; a machine without a browser uses a device code instead of a browser sign-in |
Every profile in the first release runs on Linux on x86-64. Unavailable macOS and Windows are not part of the first release, and each other platform needs its own release evidence before it is supported.
Each profile waits for its own record #
A record is the evidence that a whole run worked on clean machines. The first release needs two: the single-person record, for Just me, and the team record, for the other three profiles. The first release exists only when both records exist.
| Profile | Prerequisites | Standing | Evidence still missing |
|---|---|---|---|
| Just me | An account with a model provider Throttle supports, and a Git repository to enroll | Planned | The single-person record: the whole first run on a clean machine with Claude and an API key, repeated on a second |
| Team member | An invitation, a Google account and a team server you can reach | Planned | The team record |
| Team server | PostgreSQL 16, a public host name, and a backup that has been restored in a test before the server goes live | Planned | The team record, repeated from a server restored onto a fresh machine |
| Build or agent machine | An enrollment code and the build tools its recipes need | Planned | The team record, including a verdict that runs on the enrolled machine and names it |
The team record covers a self-hosted server, two organizations, three people and an enrolled machine, then recovery and removal.
Later releases add more profiles #
These profiles are part of the approved design but not of the first release.
| Profile | What it is | Standing |
|---|---|---|
| Remote client | The hyper program alone, bound to a team server, with no local database, agent or inference | Planned |
| One component on its own | Throttle, Lanes, Reactor or Rocket! without the rest, reached from the installer's quieter "Choose components" option; each needs its own installed evidence | Planned |
| Fleet operations client | The hyper program for Fleet, the privileged operations workspace, acting under explicit grants | Planned |
| Hosted server | The team server's parts, operated by Hypervibe, as a packaging profile | Planned |
| Hosted multi-replica service | A shared, replicated service run for many teams. Deferred: it is not part of the approved design for these releases | Unavailable |
A lost connection never changes a profile #
You pick the profile when you set up the machine, and only an explicit choice changes it. A team machine that goes offline does not become an authority of its own: it carries on only within the grants and limits it already holds.
A machine can hold more than one profile. Profiles that need the same part share one installed copy, and removing one profile keeps whatever another still uses, along with its work.
Where to go next #
- Install explains what setup will change on the machine.
- First verified change walks through the first run on Just me.
- Deploy and operate covers team servers, enrollment, backup and recovery.
- Standings explains what a profile needs before it can be called Qualified.