When regulators ask, show them.
“Show me every agent decision affecting customer money.”
Support refund agent126 calls · 48 stopped
Claims triage agent119 calls · 26 held
Billing agent117 calls · 18 held
362 decisions48 stopped44 held270 went aheadLive from the public demosynthetic customers, last 14 days
- EU AI Act
- ISO/IEC 42001
- NIST AI RMF
- APRA CPS 230
- GDPR
- ISO/IEC 27001
- APRA CPS 234
22 of 32 clauses, across 7 frameworks, answered by one run record.
Signed.Sample record, checked on this server
One record for incident, audit and board.
The call, the rule, and who decided.
Your auditor checks it offline. How →
22 of 32 clauses, one record.
- 0.00sRun starts
- 0.04sModel thinks
- 0.71sLooks up customer
- 0.90sModel decides to refund
- 1.71sRefund blockedDisputed refunds over A$100 must be escalated to a person
- 2.20sRun ends
Signed
Technical details
Each step's hash covers the one before it. The record's fingerprint: 90b762f284e4
The agent's id: support-refund-agent
The rule's id: escalate-large-disputed
Signed.
$ npx @runback/verify audit-export.json- EU AI Act
- ISO/IEC 42001
- NIST AI RMF
- APRA CPS 230
- GDPR
- ISO/IEC 27001
- APRA CPS 234
All frameworks, clause by clause →
One gap we state plainly: a reviewer step taken outside Runback is not in the record. Article 12(3) →
This page maps Runback's capabilities to named controls. It is not legal advice and not an assessment of your compliance — whether an obligation applies to you, and whether you meet it, is your assessor's or regulator's determination.
The incident is a real demo-agent request; the audit's record is the scripted sample, checked on this server.
Your traces. Your keys. Your building.
Self-host, and none of it leaves your network.
- Self-host in your VPCA Next.js app + Postgres, free as the Community edition. Traces never touch our servers.
- Private data stays privateKeys, emails, card numbers, SSNs: with the SDK, scrubbed inside your process. OpenTelemetry spans are scrubbed on arrival, before storage.
- You own the storeYou set retention and access. Runs age out on your retention schedule.
- Open formatOpen SDKs and OpenTelemetry, a published format. Take your history with you.
- If we're unreachableYou choose. Each policy assignment fails closed (deny) or open (run, and report) while Runback is unreachable; agents declared critical default to closed. A failed trace send retries in-process on the next flush; that buffer isn't persisted, so events not yet flushed are lost if the process exits first.
- Hand-offsHand-offs between agents are signed: nobody can widen an agent's permissions unseen. How it works →
| Tier | Where traces go | AU residency | EU residency | DPA |
|---|---|---|---|---|
| Community (self-hosted) | Your Postgres, your infra | ✓ your region | ✓ your region | n/a |
| Starter · Growth · Scale · Pro | Runback cloud (Sydney) | ✓ | Enterprise only | On request |
| Enterprise (self-hosted) | Your Postgres in your VPC | ✓ your region | ✓ your region | Included |
Bring us your security review.
The person answering it wrote the code it asks about. A DPA on request.