Pricing
Seats and projects are the meter.
A plan decides how many people work in a workspace and how many projects it will hold. It does not switch off the gateway, the terminal, the IDE connection or the runner: those are the same in every plan, including the Evaluation tier.
Plans
What each plan holds.
Every new workspace opens on thirty days of Team with no payment details. What differs afterward is the size of the estate each plan will hold. Enterprise is quoted rather than published, because the price is set against seats, access model, identity and rollout scope.
| Plan | Price | Who it is for | What it includes |
|---|---|---|---|
| Evaluation | $0per month, after the evaluation | Every new workspace starts with 30 days of Team, no card required. This is what remains when the trial ends — everything you recorded stays readable. A smaller working limit, and everything already recorded stays readable. |
|
| Team | Arrangeddirectly | A delivery group running a real portfolio, where somebody has to answer for what is verified and what is only mapped. No payment details are required to begin, and none are held until a workspace chooses to keep the plan. |
|
| Enterprise | Arrangeddirectly | Several delivery groups, one register, and an audience that will ask where a number came from. Priced against the estate: seats, access model, identity and rollout scope. |
|
Where these figures come from. The seat price is read from the price object the payment processor will bill against, not from a constant on this page, so the page and the invoice are the same fact. When that source cannot be read, no number is shown at all, because a stale price presented confidently is worse than an honest “arranged directly”: a reader can act on it.
In every plan
What a plan does not switch.
A plan sets two limits, seats and projects, and the database enforces both. The four ways an engineer reaches the workspace below are the same on every plan.
Through the gateway
Point Claude and Codex at your project's gateway address with a personal token. Each call is checked against the models your workspace approves, the content it carries, your network posture and your budget before it reaches a provider. The provider key never leaves the platform.
In the terminal
Ask, plan and propose changes with a personal token. No provider key sits on the laptop; each call is classified and routed under workspace policy.
In the IDE
Connect an IDE through Model Context Protocol (MCP) to propose plans and changes, read requirements, risks and gates, and report sessions and test runs. Engineers can keep their existing tools while working within the project's authority.
On your machines
Codex works a delegated item in its own worktree on a runner you enrol, tests it with your repository's suite and hands it to a second agent for review.
How a limit is enforced
A limit is enforced where the row is written.
Hiding a button is not a limit. Both caps are triggers on the table being written, so the number a plan quotes is the number the database will refuse at, however the record arrived.
Every path meets it
A person in the workspace, a server action, an import, a direct database session and a path nobody has written yet all arrive as one insert into one table, and the plan cap runs before that row can exist.
Two requests cannot both pass
The check takes a per-organization advisory lock for the length of the transaction, so two requests cannot both read “nine of ten” and both proceed.
The refusal says why
At the cap the insert is refused, and the message names the plan, the cap, the count the organization already holds and the plan that lifts it.
No job to be late
An expired evaluation is enforced by the next write that would exceed the free cap, not by a nightly job.
The evaluation
Where a workspace lands afterward.
A governance product does not hold evidence hostage when an evaluation ends. The limits tighten; the record does not close.
For the first thirty days
Every new workspace opens on Team: 10 seats, no project cap, and no payment details.
After that
The Evaluation tier remains after the 30-day Team trial. Everything already recorded stays readable if you do not upgrade, the register, the trail and the findings, inside a working limit of 1 seat and 10 projects.