Pricing
Metered by the change, budgeted in dollars.
A platform fee with usage included, then metered per model and per sandbox-second. Every figure below is read from our price book, not written into this page.
Pilot pricing, on request.
Our prices are read live from the price book, and it did not answer just now. Rather than print a figure from memory, this page shows none; ask us and we will send the current one.
- Seatsthe people who sign off; every engineer keeps their editor
- Budgetsa cap for the organisation, a ceiling per memberin dollars
- Per changethe dollars each change actually spent, stage by stagepriced per model
What is metered
The change is the unit.
Every stage reports what it spent, rolled up per change, then per project, then per organisation. Spend is priced per model, never at one flat rate.
- A cap for the organisation
One number the whole organisation spends against, enforced where the spend happens.
- The same ceiling for every member
A ceiling, not a share: nobody’s budget shrinks when someone joins, and nobody’s grows when someone leaves.
- A budget on every change
Set on the automation, spent by the run, shown on the pull request.
- At the limit, it stops and asks
A change that cannot proceed escalates with a named reason rather than stalling silently. A person raises the budget, splits the change, or stops it.
Budgets
Every dollar has a ceiling above it.
Three ceilings, all in dollars, and a run that reaches one stops and asks rather than spending on.
Plainly
What the numbers are, and are not.
Usage is recorded forward-only from the day metering began: a stage that reports nothing writes null, never zero, and the figures are the agent session’s own accounting rather than a reconciled statement.
In the application: usage and cost per project, per change and per stage, read from the same ledger these prices apply to — provisional until reconciled, and labelled so.
Ask for a quote against your own usage.
A number with a date on it, not a tier.