The code that runs Detent Cloud is the code in the repository. Read it, run the Hub on your own host for free, or start on Detent Cloud's Free plan. Either way, you bring the model cost.
FSL-1.1-ALv2 lets you use, change, and self-host Detent for any purpose except offering a competing product, and each release becomes Apache 2.0 on its second anniversary. A self-hosted Hub needs no Detent Cloud account; the trade is that operating it is your job.
Detent is built on Detent Cloud. Its issues live on the Hub, runners pick them up, and the agents they dispatch write the changes that land in digitaldrywood/detent.
Its detent.yaml and WORKFLOW.md are in the repository, readable as a starting point for your first project.
Read Detent's detent.yaml ↗
One feature. Seven real issues. Four hours. Zero babysitting.
Every line here maps to something checked in, released, or running. Nothing on this site is a projection.
Detent Cloud's Free plan needs no card: two concurrent runs, with unlimited projects, members, repositories, and runners.
Run the same Hub on your own host. No Detent Cloud account, subscription, or billing is required.
Runners keep your checkout, your toolchain, and your Codex or Claude Code sign-in. Detent stores no model credentials.
One change lands at a time, on the base branch, after your gates clear. A change that cannot land goes to Blocked with its reason.
Enroll laptops, build servers, VMs, or Fly Sprites, and route each runner to the projects it may work.
Concurrent work is counted per organization. A claim at the limit waits in its lane until a slot frees; nothing is refused at filing.
The Hub exposes its board, issues, changes, runners, and settings over MCP, so your agent can file issues and review changes.
FSL-1.1-ALv2. Each release becomes Apache 2.0 on its second anniversary.
Detent's board dispatches agents against its own contracts, and human contributions go through the same gate and the same serialized landing.
Start free on Detent Cloud. Paid plans add concurrent work and hosted artifacts.
The Hub and runners, the state machine, the gate model, worktree isolation, and serialized landing.
The interaction-model argument, the default choices, and the comparison matrix.
Install a runner or your own Hub: platform-tabbed commands, requirements, and the first run.
The operator surface: lanes, agent activity, budgets and capacity, and MCP access.
Reviewed recordings of Detent moving real work through checked-in workflows.
The curated operator reference, mirrored from a pinned Detent release.