Become a design partnerApply now
Simple, volume-based pricing

Debug smarter.
Pay for what you use.

Replay records your web app, delivers an AI root cause analysis, and proposes a fix — right where you work.

IDE via MCP+Chrome extensionComing soon

Both access points draw from the same session pool — use whichever fits your workflow.

Starter

For individuals & small teams

When hard bugs come up occasionally and you need answers fast.

$TBD

per month · billed annually

~XX sessions / month

Includes

  • Full session recording & replay
  • AI root cause analysis per session
  • Proposed fix with code context
  • IDE (MCP) + Chrome extension access
  • 7-day session history
  • Community support
Get started
Most popular

Professional

For teams shipping fast

Growing teams with no dedicated QA, where every debugging hour is an hour not shipping.

$TBD

per month · billed annually

~XXX sessions / month

Everything in Starter, plus

  • Higher monthly session volume
  • Team sharing & collaborative sessions
  • 30-day session history
  • Priority RCA queue
  • Slack-based support
  • Usage analytics dashboard
Talk to us

Enterprise

For high-stakes, high-volume teams

When production bugs affect revenue or user trust at scale. Custom volume, custom terms.

Custom

volume-based · negotiated annually

Unlimited or defined session cap

Everything in Professional, plus

  • Dedicated Replay engineer support
  • Custom data retention & compliance
  • SSO & advanced access controls
  • SLA guarantees
  • Private deployment options
  • Roadmap input & joint planning
Contact us

Early access · Design partners

Shape what Replay becomes

We're working with a small group of engineering teams to build and refine Replay MCP. Design partners get free access during the program and favorable pricing when they convert — in exchange for real usage and regular feedback. If your team ships a React or Next.js app and hard bugs are costing you hours, we'd like to talk.

Common questions

A session is one recorded debugging interaction — a bug captured, analyzed, and returned with a root cause and proposed fix. Whether you use the Chrome extension or IDE via MCP, it draws from the same monthly pool.