Pricing
We will not charge you per governed decision.
That is the commitment worth making first, because it is the one that shapes everything else. A control you are billed for using is a control you will use less — and a governance product that gets more expensive the more you govern is arguing against itself on the invoice.
Watching is free, permanently
The first two rungs of the enforcement ladder cost nothing and always will. Not a trial, not a pilot window, and not contingent on talking to anybody.
| Rung | What it does | |
|---|---|---|
observe |
Every decision evaluated and recorded. Nothing refused. A week of it tells you what enforcement would have stopped, over your own traffic, before it stops anything. | free |
shadow |
Refusals computed and recorded but not applied. The review queue and the approval path run for real, so you find out whether anybody answers them. | free |
canary |
Refusals bite, on a slice of traffic you choose. The first rung where an agent is actually stopped. | commercial |
enforce |
Refuses everything that exceeds the grant. | commercial |
One production environment, and the report at the end is yours whether or not you continue. We charge at the rung where an agent is actually stopped, because that is the rung where this stops being instrumentation and starts being a control. Everything before it is you finding out whether we are telling the truth.
Free, and staying that way
- The specification
- Apache 2.0, unbranded, and a competitor's engine may claim conformance to it. Read it.
- The SDKs
- Python, TypeScript, the MCP server and the proxy. Open source. A governance client you cannot read is a governance client you cannot check.
- The demo, and the verifier
- A running deployment with the whole product in it — nothing held back behind a tier, because a governance product you can only half evaluate is one you cannot evaluate. Ask for access. The verifier checks a signed artefact in your own browser and needs no account at all.
What you are never charged for
- Decisions, refusals, or evidence
- Not per authorisation, not per refusal, not per trajectory, not per evidence pack, and not per verification. Govern ten thousand actions or ten million; the invoice does not know the difference.
- Auditors and reviewers
- Read-only access is unmetered. A control that costs you money every time somebody checks it is a control that gets checked less, which defeats the purpose of buying it.
- Keeping your own records
- Evidence lives in your deployment. There is no retention tier and nothing to pay to get your data out, because it never left.
Whether this is you
Priced like a compliance system rather than like per-token infrastructure. If your reference point is the governance, risk and compliance platform your second line already runs — or your model risk tooling — the shape will not surprise you. If your reference point is an API bill, it will.
And if you are a small team shipping your first agent, the honest answer is that the free rungs, the SDKs and the specification are the right place to be, and there is nothing to buy yet. Come back when somebody starts asking you to prove things. The budget for the rest usually sits with the person accountable for the estate rather than with the team building on it, which is worth knowing before the first meeting.
What drives the number
A deployment is priced on its shape rather than on its throughput, and you can place yourself on these before speaking to anybody.
| Driver | Why it matters |
|---|---|
| Regimes in scope | An EU bank under the AI Act, GDPR and DORA is getting several times what a firm under one supervisor gets. Value tracks regulatory exposure more honestly than any usage meter. |
| Entities and environments | A dev instance and a production one are different governed
estates — identity is (workspace, environment, slug), and
that is the point rather than a billing lever. |
| Agents under governance | As a measure of the estate, not a meter. Ten agents making a million decisions costs what ten agents making a thousand do, and bringing the eleventh under governance is never the thing that changes the number mid-term. |
| Deployment model | Your cloud, your data centre, or airgapped. Airgapped costs more to support and less to run; on-premise sits between. |
| Support and deployment services | Whether you want engineers alongside you for the rollout, or the software and a good runbook. |
Pricing is set with the first deployments
We are early, and there is an advantage to being one of the first rather than a disclaimer about it. A published tier list assembled before we have enough deployments would be a guess dressed as a policy — the sort of number that gets quietly changed later, which is worse than not publishing one.
What a design partner gets is concrete: pricing set with you and held for the term, a direct line to the people who wrote the platform, and your instrument moved to the front of the clause-map queue. That last one is real and checkable: DORA, ISO 42001 and MAS FEAT are all unwritten and unclaimed today, and a map is data rather than a release. What we ask in return is stated in the packet rather than left vague.
The UK map was on that list in July and is not any more, which is the point.
You will get a straight answer quickly once we know the shape. If the answer is that we are not the right fit yet, you will hear it in the first conversation rather than the fourth.
How it starts goes further than this page does: the four rungs one at a time, and what changes at the one where refusals begin to bite.