Pricing

Priced per action, not per seat.

You pay for what is actually covered. Compliance value scales with how much of your agent fleet is recorded — not with how many people log in to look at it.

Self-serve

Free
while you evaluate

Install the SDK, instrument a real agent, verify a real bundle. This is where developers start.

  • All four capture planes
  • Hash chain and signed checkpoints
  • Offline verification, always
  • Native spend analysis and budgets
  • Community support
Start free
Most common

Usage

Per verified action
+ platform fee

A fixed rate per agent action logged and policy-checked, so cost scales with how much of your fleet is actually covered — never with seats.

  • Everything in Self-serve
  • Policy enforcement and human sign-off
  • Examiner packet with regulator mapping
  • Cost per agent, per run, per customer
  • Multi-year retention
  • External timestamping (RFC 3161)
Talk to us

Enterprise

Contract
annual, volume-based

For regulated deployments that run it themselves and bring their own security review.

  • Everything in Usage
  • Self-hosted — runs entirely in your VPC
  • Metadata-only mode (we never see payloads)
  • WORM storage and legal hold
  • SSO, audit log export, custom DPA
  • Named support with an SLA
Talk to us
Questions people actually ask

The ones that decide it.

Including the one most pricing pages avoid: what happens to your evidence when you stop paying for it.

Start free
01
Why isn't the per-action rate published?
Because we'd be guessing. The rate is being set with design partners against what comparable logging and observability tools actually charge per event — not picked to look good on a pricing page and then walked back on the first real contract.
02
What counts as a verified action?
One event written to the chain — a tool call, a decision, a model call, a policy decision. Retries and internal bookkeeping are not billed. If we cannot price an upstream call, the record says so rather than guessing.
03
Do you see our prompts?
Not by default. The standard mode records metadata and cryptographic hashes only; payloads stay in your storage. Integrity is still fully provable, because the hashes are what chain.
04
What happens if we stop paying?
You keep your evidence. Export is always available and the bundles verify without us — that is the point of offline verification. A compliance record you lose access to is not a compliance record.
05
Can we run it ourselves?
Yes, on Enterprise. Nothing in the architecture assumes our cloud: the chain, the policy engine and the verifier all run inside your VPC. External anchors work from anywhere.
06
How is this different from our observability tool?
Those answer “is the model behaving” for engineers, on mutable logs with short retention. This answers “prove what the agent did and that the record is unaltered” for the person who has to sign.