Free to start. A$600/mo for production teams. Custom for the enterprise.
Same platform at every tier — pay for scale, team tooling, and governance controls.
Prices are in Australian dollars. Your card is charged in AUD and converted by your bank at their rate on the day.
Self-host forever. Single workspace.
- Full SDK + self-hostable core
- Observe · replay · signed audit
- CI release gate · PII redaction
- Any model · OpenTelemetry compatible
- Single workspace · 1,000 runs/mo · 7-day retention
Small team, managed — no infra to run.
- Everything in Community, hosted
- Team & roles (RBAC) · 5 seats
- Alerting — email · Slack · webhook
- 20,000 runs/mo · 30-day retention
Teams with agents in production.
- Everything in Starter · 10 seats · 50k runs
- Golden suite — incidents auto-mined into regression tests
- Eval runner + CI gate · dataset management
- 60-day retention · multi-workspace
Multi-team, fleet visibility, policy control.
- Everything in Growth · 20 seats · 75k runs
- Fleet control-room dashboard
- Policy simulation + library
- Model diff · upgrade gate · cost attribution
- Policy causal attribution heat-map
Full platform, named support, managed SLA.
- Everything in Scale · 25 seats · 100k runs · 90-day retention
- Fleet benchmarks vs. vertical peers
- Inter-agent trust chain · signed delegation proofs
- Live runtime enforcement · advanced bisection
- Priority support · named contact · SLA
For regulated environments.
- Everything in Pro, in your perimeter
- SSO (OIDC) · managed audit keys · signed ledger
- Unmetered runs · unlimited retention
- Self-host in your VPC · data residency
- Regulatory dashboard — EU AI Act · ISO 42001 · NIST AI RMF · APRA CPS 230/234 · GDPR · ISO 27001
- Team chargeback with monthly budget caps
- Named support · SLAs · security review
Swipe to compare all six tiers →
| Capability | Community | Starter | Growth | Scale | Pro | Enterprise |
|---|---|---|---|---|---|---|
| Capture · replay · signed audit | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Evals — run against a dataset | — | — | ✓ | ✓ | ✓ | ✓ |
| In-process PII redaction · any model · OTel | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Seats | 1 | 5 | 10 | 20 | 25 | Unlimited |
| Runs / month | 1,000 | 20,000 | 50,000 | 75,000 | 100,000 | Unlimited |
| Retention | 7 days | 30 days | 60 days | 60 days | 90 days | Unlimited |
| Team roles (RBAC) | — | ✓ | ✓ | ✓ | ✓ | ✓ |
| Alerting (failures, errors, cost spikes) | — | ✓ | ✓ | ✓ | ✓ | ✓ |
| Approvals — human-in-the-loop review queue | — | ✓ | ✓ | ✓ | ✓ | ✓ |
| Golden suite | — | — | ✓ | ✓ | ✓ | ✓ |
| Incidents — auto-RCA on policy blocks | — | — | ✓ | ✓ | ✓ | ✓ |
| Fleet dashboard | — | — | — | ✓ | ✓ | ✓ |
| Policy simulation + library | — | — | — | ✓ | ✓ | ✓ |
| Model diff · drift detection · upgrade gate | — | — | — | ✓ | ✓ | ✓ |
| Cost attribution | — | — | — | ✓ | ✓ | ✓ |
| Policy causal attribution (block-rate heat-map) | — | — | — | ✓ | ✓ | ✓ |
| Corpus signals — fleet anomaly mining | — | — | — | — | ✓ | ✓ |
| Fleet benchmarks | — | — | — | — | ✓ | ✓ |
| Named support · SLA | — | — | — | — | ✓ | ✓ |
| Runtime enforcement + deep replay | — | — | — | — | — | ✓ |
| SSO + append-only ledger | — | — | — | — | — | ✓ |
| Per-team budgets & chargeback | — | — | — | — | — | ✓ |
| Regulatory mappings (EU AI Act · ISO 42001 · NIST AI RMF · APRA CPS 230/234 · GDPR · ISO 27001) | — | — | — | — | — | ✓ |
| Self-host in your perimeter | ✓ | — | — | — | — | ✓ |
| Data residency | Your infra | US cloud | US cloud | US cloud | US cloud | Your perimeter |
| Support | Community | Priority email | Priority email | Named · SLA | Named · SLA |
Community edition — free to self-host.
One command to deploy. Or skip the infra and start managed at A$49/mo with a free trial.
We already use LangSmith or Langfuse — why switch?
You don't have to. Those tools make traces readable. Runback makes them re-executable — re-run any step from the exact captured context, gate a model upgrade in CI, and export a signed artifact your auditor can verify independently. Most teams run both.
Where does our data actually go?
Community: your Postgres, your infra — nothing leaves your perimeter. Starter through Pro: traces are written to Runback-managed Postgres (US region); PII is redacted in-process before anything is sent. Enterprise: your Postgres in your own VPC. Data residency outside the US (EU, AU) requires Enterprise self-hosted.
What happens if Runback is down during policy enforcement?
Observation degrades gracefully — traces buffer locally and sync when the connection recovers. Policy gates fail open by default so your agent is never blocked by an infrastructure outage. Enterprise can configure fail-closed for environments where blocking is the safer default.
Can't we just build this ourselves?
The capture layer is a sprint. The parts that compound — policy simulation over 90 days of real decisions, a golden corpus that auto-mines regressions, fleet benchmarks that only become meaningful at scale — take a year and don't work without the data. Your logging history can't be back-filled.
Is the Community edition really free?
Yes, free to self-host forever. Starter (A$49/mo) gets your team on managed hosting with RBAC and alerting. Growth (A$600/mo) is where compound value starts — the golden suite builds your regression library from real failures, automatically.
What's the difference between free and paid?
Community gives you capture, replay, signed audit, and the CI gate — free under the Runback Community License. Enterprise features (team roles, SSO, fleet dashboard, policy enforcement) require a plan or a signed self-host license. An arbitrary RUNBACK_LICENSE string unlocks nothing — it's cryptographically gated.
How do we get through a security review?
Start with one agent in your own VPC — nothing leaves your perimeter, so most reviews are short. We'll join the call and answer questions directly. The procurement kit has the documents your assessment needs.
Can your team read our agent traces?
On managed cloud: infrastructure staff have database-level access to the server. PII is redacted inside your application process before anything arrives — card numbers, emails, and SSNs never reach us — but the redacted trace content is readable by anyone with database access. If that is not acceptable, self-host: your data never touches our servers and this question does not apply.
What happens to our audit records if Runback shuts down?
Self-hosted customers own the database. Nothing changes — your records stay in your infrastructure regardless of what happens to Runback. Managed cloud: cassette files use an open, documented format (runback.cassette/v1) with a public schema. They can be exported at any time and verified independently without Runback software. The verifier works on the files themselves, not on a Runback account.
GDPR right to erasure vs. your append-only ledger — how does that work?
This is a real tension. The append-only ledger is designed so that removing an entry breaks the hash chain for all subsequent entries — that is the point of tamper-evidence. Our approach: configure redaction before traces are sent and personal data does not reach the cassette in the first place. If PII did reach a managed-cloud cassette and a verified erasure request arrives, we delete the run record — that breaks the chain at that point, and the break is the honest record of what happened. Self-hosted: you own the database and the legal decision; execute erasure yourself.