Pricing
The price is on the page because the product is, too.
Month to month, or two months free on annual. No minimum term, no seat negotiation, and no call required to find out what it costs.
Free
$0
Settle the argument before you pay anything.
- The gateway and detection engine
- Signed receipts for every call
- The CLI, the extension and both SDKs
- The open-source verifier
- 30 days of receipt history
Team
$499 /mo
One application, one team, real obligations.
- Everything in Free, kept indefinitely
- Approvals: hold a call for a person
- Compliance packs across 7 frameworks
- Transparency log and RFC 3161 anchoring
- One signing key, replaced on demand
BusinessMost companies
$1,499 /mo
Every application, and somebody who has to answer for them.
- Everything in Team, across every app
- Evidence connectors and SIEM push
- SSO, roles, and an activity log of its own
- Sealed mode: content keyed to you
- Your own signing key and key attestation
Self-hosted
$2,500 /mo
Your cloud. Nothing reaches us at all.
- Everything in Business, in your cloud
- Helm chart, Terraform, or the container
- Signing keys you hold and replace
- Whole-machine coverage via CONNECT
- Receipts signed under your own name
Running this for clients? Partner pricing starts at $199 per client, per month, from five clients.See the partner model
Verification is free for everyone, forever, including people who are not our customers.
Your auditor, your customer, your insurer and the opposing side in a dispute can all check a receipt with no account and no payment. Evidence you have to buy access to is not evidence.
Line by line, so nobody has to ask.
| Capability | Free | Team | Business | Self-hosted |
|---|---|---|---|---|
| Govern AI, API and MCP traffic | ||||
| Browser extension and on-device agent | ||||
| Signed receipts, verifiable offline | ||||
| Receipt history | 30 days | Unlimited | Unlimited | Your database |
| Applications covered | 1 | 1 | Unlimited | Unlimited |
| Approvals: hold a call for a person | — | |||
| Compliance packs, 7 frameworks | — | |||
| Transparency log and external timestamps | — | |||
| Evidence connectors | — | — | ||
| SIEM push: Sentinel, Splunk, HTTP | — | — | ||
| SSO, roles and scoped access | — | — | ||
| Sealed mode: content keyed to you | — | — | ||
| Signing key held by you | — | — | Sealed mode | |
| Whole-machine coverage (CONNECT) | — | — | — | |
| Your data reaches our servers | Yes | Yes | Yes | Never |
Questions people ask before they pay.
What happens to my receipts if I stop paying?
They keep verifying. The key that signed them stays published, and the open-source verifier does not check whether you are a customer. Export everything before you go; the archive works offline afterwards.
Do I have to send you our prompts?
No. Keeping request and reply bodies is a switch, off by default, and a receipt is complete without them: it carries digests, not content. On payment routes we never store bodies whichever way that switch is set.
Is the price per seat?
No. Charging per seat would push you to give fewer people access to the audit trail, which is the opposite of the point. Invite your auditor; it costs nothing.
What about a fleet of laptops?
Public-sector and large-fleet deployments are priced per device per month and quoted on request, because the number depends on how many machines run the agent and whether the service is hosted or in your cloud.
What counts as one application?
One codebase or product sending traffic under its own key. A staging copy of the same application is not a second one. If you are unsure, it is one.
Can we start self-hosted?
Yes, and many should. It is the same binary as the hosted service, starts in about a second against an empty Postgres, and the receipts it signs carry your name rather than ours.