Skip to main content

Built by makers, shipped in public

Sign in

ID side vs Runback

A side-by-side comparison built from both listings. Blank cells mean the company has not given that detail; we never guess.

ID side compared with Runback
DetailID side logo ID sideRunback logo Runback
What it doesThe control layer for AI See, trace, stop, and prove what your AI agents do
StageNot given Startup
FoundedNot given 2026
Based inNot given AU
Pricing modelFreemium Freemium
PricingFree plan: €0/month with 10,000 proofs included per month. Starter: €59/month with 50,000 proofs, then €0.0015 per proof above. Growth: €249/month with 500,000 proofs, then €0.0005 per proof, then €0.0002 after 2,000,000 proofs. Enterprise: from €990/month or €15,000/year licence with 5,000,000 proo Free: Community edition (1,000 runs/month, 1 workspace, 7-day retention, self-hosted). Starter: A$49/month (20,000 runs/month, 5 seats, 30-day retention). Growth: A$600/month (50,000 runs/month, 10 seats, 60-day retention). Scale: A$1,800/month (75,000 runs/month, 20 seats, 60-day retention). Pro: A
Key features
  • Wraps AI provider clients with policy enforcement before calls execute
  • Enforces provider-level privacy parameters like store=false for OpenAI
  • Generates signed, non-reusable ACT tokens for each request
  • Maintains append-only, hash-chained ledger for audit verification
  • Embedded preference widget with cross-app persistence
  • Global Privacy Control signal detection and enforcement
  • Fails closed when unreachable; no fallback mode
  • Python and Node.js SDKs with source-available licence
  • Policies defined in dashboard, not in code
  • Record every model call, tool use and agent step
  • Replay decisions from original context
  • Policy enforcement before tool execution
  • Turn failures into regression tests
  • Tamper-evident audit records
  • MCP gateway integration
  • Incident tracking from failed runs
  • Prompt registry and playground
  • Fleet control room and policy simulation
  • Signed audit records with integrity verification
What makes it different
  • Cryptographic proof of compliance: signed, verifiable tokens and append-only ledger that auditors can verify without vendor involvement
  • Policies live in dashboard, never touch code, preventing unauthorized modifications
  • Separates user preference control from developer code, ensuring developer cannot alter consent
  • Replay over retell: hold context fixed, run the model fresh to verify behavior actually changed
  • Block before it ships: enforce policy at release time, not after a failure in production
  • Self-hosted by default: full control with deployment in customer's own network
  • Tamper-evident records checkable without Runback
  • Turn production failures into future test cases
Community votes00
DR (Domain Rating by Ahrefs)Not checked yet no change since last checkNot checked yet no change since last check
Trust Flow (Majestic)00
Citation Flow (Majestic)09
Referring domains (Majestic)01

5 details filled in for both companies.

More alternatives to ID side More alternatives to Runback

Ask us