Pricing

Priced per agent. Never per event.

Billing per event would pay you to record less. So recording everything costs the same as recording something: a flat band by agent count, unlimited actions — and published.

Self-serve

Free

while you evaluate · 1 agent

Wire up one agent, check one record.

  • Records every kind of action an agent takes
  • Sealed so an edit cannot be hidden
  • Your auditor checks it offline, always
  • What each agent costs, and a ceiling
  • Community support
Start free

Scale

$4,000

per month, annual plan charged monthly · up to 50 agents

For a fleet, and the security reviews that follow one.

  • Everything in Team, up to 50 agents
  • Examiner packets on a schedule, not on request
  • Write-once storage and legal hold
  • SSO and audit log export
  • Named support with an SLA
Talk to us

Enterprise

$96,000+

per year · unlimited agents, self-hosted

For regulated deployments that run it themselves.

  • Everything in Scale, no agent limit
  • Runs entirely inside your own cloud
  • We never see the contents — only fingerprints of them
  • Your own DPA, and a custom retention schedule
  • Named support with an SLA
Talk to us
  • ✓ No card to start
  • ✓ Nothing is blocked until you say so
  • ✓ Your proof stays yours if you leave

Packaged counts, not a meter — you move band on passing the count, never mid-year.

Against the category

The number is on this page.

Vanta
quote only
depends on what they think you can pay
Drata
quote only
the same
Auditant
$18,000/yr
Team, ten agents, published
What actually happens

A week, and then nothing to do.

No implementation project, no consultants, nobody has to become a compliance expert.

  1. 01Day one

    Turn it on

    Two lines in one agent, or a config change at your gateway. It records; it blocks nothing.

  2. 02Week one

    Watch what it caught

    Every action shows up as you go — you see what your agents do before you stop any of it.

  3. 03When you are ready

    Draw the lines

    Write the limits in plain English. Each rule starts in monitor mode, so you see what it would stop before it stops anything.

  4. 04When they ask

    Hand over the packet

    One file for the examiner, the auditor, or your customer's reviewer. They check it themselves.

Why the meter matters

A meter is an instruction.

Whatever you charge for, your customer does less of. Both meters, on the same day of the same agent.

billed per eventthe incentive
01sample at 10% cheaper — and 9 in 10 actions gone-90%
02drop tool calls cheaper — and the actions are the evidence-40%
03shorten retention cheaper — and the question arrives later-70%
04record one agent only cheapest — and the fleet is unrecorded-95%
! The cheapest configuration is the one that records least.
billed per agentthe incentive
01sample at 10% no saving$0
02drop tool calls no saving$0
03shorten retention no saving$0
04chain everything same price$0
◎ The cheapest configuration is complete coverage.
Per agent
flat, by band
Per action
$0
Cap on actions
none

It also settles the question nobody wants to ask: whether our revenue grows when your agents misbehave more. It does not.

For both readers

What you pay for, and what you keep.

The two questions a buyer and an engineer ask differently, answered the same.

What you pay for

A band by how many agents you run. Recording more never costs more, because a meter that charged per action would pay you to record less — and an incomplete record is the one thing this product cannot be.

What you pay for

Flat bands: one agent, up to ten, up to fifty, unlimited. Recording is never metered. Retries, heartbeats, rule checks and verification cost nothing. You move band on passing the count, never mid-year.

What you keep if you leave

Everything. Export is always available and the file checks out without us. A record you can lose is not a record.

What you keep if you leave

Export at any time; the file carries its own verifier. Thirty days to export after you leave; write-once copies of the seals persist until their retention date, by design.

And the invoice has no surprises in it.

Keeping years of records has a real cost, so it is a line item rather than an upsell that arrives with the renewal — the invoice nobody budgeted for.

Everything on the right is metered by somebody in this category. None of it is metered here.

What actually gets recorded →
not billedever
—retries the same action, attempted twice—
—heartbeats how a quiet agent stays distinguishable from a dead one—
—policy checks every decision, allowed or refused—
—verification yours, your auditor's, or a stranger's—
—an agent in staging if it shares the production identity—
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.

01

Why per agent and not per event?

Because per-event billing on an audit product pays you to record less, and an incomplete record is the one failure this category cannot survive. Per agent, recording everything costs nothing extra.

02

What counts as an agent?

One deployed agent. Twelve support bots is twelve; the same bot in staging and production is two, unless they share an identity. Retries and internal bookkeeping are never billed.

03

Why is this published when Vanta and Drata quote privately?

Because a price you have to ask for depends on what they think you can pay. Ours is on this page, so you can decide before you talk to us.

04

Do you see our prompts?

Not by default. We record what happened and a fingerprint of it — the contents stay in your storage, and the record still proves nothing was altered.

05

What happens if we stop paying?

You keep your evidence. Export is always available and it checks out without us. A record you can lose is not a record.