Priced per protected service. Never per incident.
We have not published a list price, because with the number of customers we have today any figure here would be a guess dressed up as a policy. What we can tell you before you talk to anyone is exactly what we meter, what we refuse to meter, and how a deployment actually starts.
One line item: the services you put under the gate.
A protected service is one deployable unit that Odonat guards end to end: its pull requests go through the pre-merge gate, its rollouts go through a Sentinel Cell, and its production anomalies are eligible for remediation.
You choose which services those are, and you can start with one. Annual contract, invoiced yearly. The number scales with your architecture, which you control, rather than with your incident count, which you do not.
- All three phases: pre-merge gate, Sentinel Cell rollout, autonomous remediation
- Unlimited engineers. Adding people to your team never increases the bill
- Unlimited incidents, alerts and reverts
- The full safety plane: allowlist, confidence gating, human approval queue
- Signed audit stream into your own SIEM
- VPC-native deployment with zero inbound ports
A pricing model is an incentive. Here is ours, stated plainly.
Before you ask what it costs, it is worth knowing what we have decided not to charge for, because that tells you what the vendor is rewarded for doing.
Per seat
Charging per engineer taxes you for growing the team. It also pushes companies to share logins, which wrecks the audit trail that makes autonomous action defensible in the first place.
Per incident
A reliability vendor billing per incident profits from your worst quarter. That is a broken incentive, and any SRE reading a contract will spot it. Our revenue should not go up when your production goes down.
Per alert or per event ingested
Volume-based observability billing is why teams sample telemetry and turn off noisy checks. We would rather see everything and price on something you control deliberately.
Nobody grants write access on day one.
You should not, and we do not ask you to. Odonat earns autonomy in stages, and the first one costs nothing.
Pilot
One service, in your VPC, running in shadow mode. Odonat watches and drafts what it would have done without touching production. You review the drafts and decide whether the judgement is good enough to trust. No commitment, no charge.
Guarded rollout
Autonomy switched on for a scoped set of services, with the approval queue routing everything to a human. Confidence thresholds tuned against your own incident history. Priced from here, annually, on the number of protected services.
Production standard
Autonomous remediation inside the allowlist for services you have signed off. Everything else keeps escalating to on-call. You raise or lower the threshold per service at any time.
Tell us how many services you would protect.
That is the only number we need to quote you. The shadow-mode pilot is free, runs in your own VPC, and touches nothing.
Contact Sales