Nothing is enforced until you say so.

The ladder, and where we come into it

Enforcement is a mode on a grant, not a switch on the platform, and it moves one rung at a time. Each rung below says what the software does, what it costs, and what we are to each other while you are on it.

1. observe free

   Every decision is evaluated and recorded. Nothing is refused. A week of it tells you what enforcement would have stopped, over your own traffic, before it stops anything.

   We help you stand it up and wire the first agent. No contract, no commitment, and the report at the end is yours whether or not you continue — it is the conversation to have internally, and it is not a demo.

2. shadow free

   Refusals are computed and recorded but not applied. The difference from observe is that the review queue and the approval path run for real, so you find out whether anybody actually answers them.

   Still nothing to pay, and that is the standing position rather than a courtesy — see pricing. This is also where design partners live: a direct line to the people who wrote it and your instrument moved to the front of the clause-map queue, in exchange for letting us find out where the product is wrong.

3. canary commercial

   Refusals bite, on a slice of traffic you choose. The first rung where an agent is actually stopped, which is why it is a rung of its own rather than a step inside the last one.

   A production deployment: single tenant, your environment, your keys, your identity provider. Priced on the shape of the deployment rather than a count of decisions — charging per decision would price you for governing more of your estate.

4. enforce commercial

   Every consequential action, every time. The state the platform exists to reach — and the one nobody should arrive at on their first day.

   Deployment support, clause maps authored with your counsel for instruments we do not ship, and the rollout from one agent to the estate.

Most teams should not start at the top. Starting at enforce means discovering your own edge cases as production incidents, which is how a control gets switched off and never switched back on. The ladder exists because that failure is more common than the one it is meant to prevent.

Before any of it

What you are probably wondering about money

Is there a price list?

The part that matters is published. observe and shadow are free permanently, and we will never charge you per governed decision; both are commitments rather than offers. What is not published is the number for canary and enforce, because it follows the shape of a deployment and a tier list written to look decisive would be a guess dressed as a policy. You will have that number before you commit to anything, and you can reach the two free rungs without asking anyone for it.

What drives it?

The shape of the deployment — the regimes in scope, entities and environments, whether you need clause maps authored, how much of the rollout you want us in. Not the number of decisions governed, and not the number of agents you bring under governance mid-term.

What is actually free?

observe and shadow, the specification, the SDKs, the verifier, and read-only access to the running platform. The two free rungs are the two that produce the report you would use to decide, in one production environment, permanently — not a trial window. See pricing.

Where does it run?

Your VPC, your data centre, or airgapped. You do not send us data on any rung — see the security overview.