Free
$0
One machine, no card, no expiry
One person deciding whether this works, on their own machine and their own Claude Code.
- 1 machine running work at once
- 2 projects
- 5 repositories
- Human approval
- Auto pull request review
Plans
Every plan runs the work on machines you control, with the Claude Code you already pay for. You are paying for the platform (the state, the gate, the review and the cross-project view), not for tokens.
Team
most teams$29
per runner, per month · each extra runner $5
A team that writes its specs down. Everyone runs their own machine, and the work is visible across all of them.
- Up to 5 machines running work at once
- 10 projects
- 25 repositories
- Human approval
- Auto pull request review
- Cloud runners soon
Enterprise
Talk to us
Priced against what you run, not per seat
More repositories than a limit should be counting, or a Crewbit you host yourself.
- No limit on machines running work at once
- No limit on projects
- No limit on repositories
- Human approval
- Auto pull request review
- Cloud runners soon
A line marked soon is a promise, not a feature. It is listed because you would ask, and it is marked because it is not built: what a cloud runner would be.
What each plan includes
Every stage protects the quality of the pull request, so no stage is a paid extra. What the plans differ on is scale.
| Feature | Free | Team | Enterprise |
|---|---|---|---|
| Runners | 1 | 5 | no limit |
| Projects | 2 | 10 | no limit |
| Repositories | 5 | 25 | no limit |
| Human approval | Included | Included | Included |
| Auto pull request review | Included | Included | Included |
| Custom verify command | Included | Included | Included |
| Fix-round limit | 2 | 2 | 2 |
| Fix-turn budget | Included | Included | Included |
| Label trigger | - | Included | Included |
| Structured runner logs, ready for any collector | Included | Included | Included |
| Cloud runners | - | soon | soon |
| Billed for model tokens | Never | Never | Never |
What counts as what
A machine
A computer with your Claude Code on it, running work for you. It is counted while it is connected, not while it is idle. The plan limit is how many can run work at the same time.
A project
What specs and settings belong to. A project is not a repository: issues can come from one provider while the code lives on another, and one project can span several repositories.
A repository
A place specs are read from and pull requests are opened against. The verify command, the credential and the base branch belong to it, because they are properties of a tree.
About the bill
Does Crewbit charge for the model?
No. The work runs on the Claude Code seat you already pay for, on your own machine, so there is no token line on a Crewbit invoice. A merged Run is roughly $7 to $10 of shadow price: a locally computed estimate at list rates, not an amount owed.
What happens when I hit a limit?
The action is refused and names the limit and the plan it belongs to. Nothing is silently dropped and nothing overages onto next month's bill.
Is Team priced per person or per machine?
Per machine. $29 a month covers one runner; each extra runner is $5. A developer who never connects a machine costs nothing, and one developer with two machines is counted as two.
Can I move from Free to Team without losing anything?
Yes. Projects, sources and Run history belong to the org, not to the plan. Raising the plan raises the caps and changes nothing else.
When are the hosted machines real?
No date. They would run on your own API key rather than a subscription, which is what makes them a plan rather than a question for a lawyer. Until they exist, every Run needs a machine of yours.
What does Enterprise get that Team does not?
No caps, and the option to run the server yourself. Every stage of the pipeline is identical on all three plans, because cutting a stage would attack the thing that makes the pull request worth having.