Question 1

What's the difference between the plans?

Accepted Answer

The plans differ by credit allotment. Free gives you 25 credits per month — enough to evaluate Replay QA with no time limit. Starter ($20/mo) and Pro ($200/mo) unlock more volume and all integrations. Private Cloud and On-Prem are for organizations that need dedicated data ownership or self-hosted infrastructure.

Question 2

Can I upgrade or downgrade at any time?

Accepted Answer

Yes. Start on Free and upgrade whenever you're ready — no commitment required. You can downgrade to a lower plan at the end of your billing period.

Question 3

What counts as a credit?

Accepted Answer

A credit maps to any meaningful work done by Replay QA. A user journey discovered, a bug found and analyzed. To run QA on a web app of average complexity, expect to spend around 20 credits. The more complex an app is, the more credits it will require.

Question 4

What happens if I hit my credit limit?

Accepted Answer

You can always upgrade to a higher plan, and the credits for the new plan will become available immediately. Additionally, you can earn credits by sharing your Replay QA projects on social platforms. Open the project's settings and paste in the link to your public social post. Once it's set, the project is free — all credits already spent on it are refunded, and future QA on it is free. That's it: QA runs exactly the same, at no cost. Shared projects are public and searchable, so others can see the results — it also works great for QA'ing an app someone else posted to help them out.

Question 5

How is this different from Datadog, Sentry, or LogRocket?

Accepted Answer

Those tools surface what went wrong. Replay captures the full runtime — every DOM mutation, network call, and JS execution frame — and analyzes it to tell you exactly why, with a specific fix. No human needs to read a trace.

Question 6

Does the Security Scan cost extra credits?

Accepted Answer

Security Scan runs are billed the same way as standard QA passes — credits consumed depend on the complexity of your app, not the scan type. The same credit allotments apply across all QA modes.

Question 7

Can I schedule Replay QA to run on a set cadence?

Accepted Answer

Yes. You can configure daily or weekly scheduled runs in project settings. Great for teams who want a nightly batch of fresh issues ready when the workday starts.

Question 8

Does Replay QA work with my existing tooling?

Accepted Answer

Yes. We've built Replay QA to work well with your existing tooling.  1)  You can ask your coding agent to kick off a Replay QA project with a prompt. Then your agent will be able to get updates on the progress, and when we find bugs, they'll be ingested automatically for your agent to fix.  2)  If you've got Playwright tests set up in your CI/CD pipeline, you can configure your tests to also trigger Replay recordings, and our Github bot will kick off analyses on failed tests automatically (sending them to the Replay QA), and the root cause and suggested fixes will be posted as a comment on your PRs. It's magical.

Simple pricing.
Based on usage.

Try Replay with no commitment

For individuals using Replay beyond the basics

For startups and small teams moving fast

For organizations that need to own their data

For running Replay inside your own infrastructure

Common questions

Simple pricing.Based on usage.