BotGauge
Freemium
Startups and fast-moving engineering teams
Replay QA
FreemiumAgentic
AI coding tools ship apps in hours — but the QA layer still assumes you have a test suite, a QA team, and two weeks to triage. Replay QA exists for the gap between 'it works on my machine' and the first bug report from a real user.
$17/mo · Free tier: 25 credits a month, no time limit, no credit card required · Checked Oct 23, 2026
Similar tools
BotGaugeFreemiumThe core loop is: probe the agent with adversarial and real-world scenarios, trace every…
AxonQAFreemiumThe core loop: bring in a Jira ticket or let the AI explore your app, review the tests it…
Before Users DoPaidThe tool connects to MCP-compatible clients like Cursor or Claude Desktop, so the QA loop runs…
Bypass LabsPaidThe workflow is boundary-in, proof-out: you approve targets, exclusions, and stop conditions…
Summary
Point Replay QA at a URL or connect a GitHub repo, and it autonomously explores the app, generates Playwright tests, records every session, and files bug reports with root cause and a suggested fix attached. No test suite to author, no pipeline to configure. The GitHub integration posts that root cause directly on the PR, so the fix lands before the branch merges. The ceiling appears with complex, auth-heavy flows and multi-step user journeys where autonomous exploration misses paths a human tester would recognize. Teams shipping internal tools or greenfield AI-generated apps get the most coverage; teams with intricate role-based UIs will find the agent's exploration shallow.
Bottom line: Pick this when you are shipping an AI-generated app with zero test coverage and need a bug report in minutes — plan a different strategy when your app's critical paths sit behind OAuth flows or multi-tenant permission logic the autonomous explorer cannot navigate.
Pricing Plans
SubscriptionLast verified 2 weeks ago- Price
- $17/mo
- Free Tier
- 25 credits a month, no time limit, no credit card required
Free
Free
Try Replay with no commitment
- 25 credits a month
- no time limit
- no credit card required
Starter
$17per month
$204/yr
For individuals using Replay beyond the basics
- 50 credits a month
- right volume for solo builders running a handful of apps or workflows
Pro
$170per month
$2,040/yr
For startups and small teams moving fast
- 500 credits a month
- for teams that ship often and need consistent coverage
Private Cloud
Custom
For organizations that need to own their data
- storage bucket your company owns
- no egress to other systems
- cluster resources dedicated to processing your data alone
On-Prem
Custom
For running Replay inside your own infrastructure
- complete ownership of entire pipeline
- data and compute running on infrastructure you control
- volume-based usage can increase price
View full pricing on replay.io →
Pricing may have changed since last verified. Check the official site for current plans.
Find your fit
Before you choose Replay QA
More options in Test Generation. Compare pricing, platforms, and features side by side.
AxonQA
Freemium
QA engineers and teams shipping software
Pros
- Zero-setup URL testing — paste a link, get a structured bug report with recording and root cause in minutes, so teams without a QA function get a first-pass audit without writing a single test.
- GitHub integration posts root cause and fix suggestions directly on the PR, which means bugs surface before code merges rather than after a user files a ticket.
- Autonomous test generation writes its own Playwright tests against the live app, so teams carrying no prior test coverage get a test layer without the authoring cost.
- Session recordings tied to every bug give developers the full execution trace rather than a vague error message, so reproduction time drops from hours to minutes — a problem Glide's VP Engineering described as 'reproducibility purgatory' costing 1–2 hours per developer per day.
- API access lets AI coding platforms embed Replay QA as a quality gate on every app they generate, so generated code gets checked before it ships rather than after a user discovers the failure.
Cons
- Autonomous exploration cannot navigate apps behind OAuth, SSO, or complex login flows — the agent explores what it can reach unauthenticated, so critical paths that require a session token go untested. Teams with auth-heavy apps end up writing manual tests for the coverage that matters most, which defeats the no-test-suite promise.
- Multi-step, role-dependent user journeys — the kind where what a user sees depends on their permissions, their prior actions, and their account state — exceed what the agent can discover by crawling a URL. Teams with that kind of UX surface area will find the bug reports skew toward surface-level UI issues and miss the logic failures that actually reach production.
- Self-hosting is not available, so teams in regulated industries or with strict data-residency requirements cannot run Replay QA on their own infrastructure. Those teams evaluate on-premises testing solutions instead.
About
- API Available
- No
- Self-Hosted
- No
- Last Updated
- July 21, 2026
Best For
Who it's for
- Solo developers running multiple apps
- Startups and small teams shipping frequently
- Organizations needing scalable usage-based testing
- Teams integrating AI debugging into workflows
What it does well
- Continuous testing via GitHub integration
- One-time app URL analysis for bugs
- Providing root cause and fixes to coding agents
- Evaluating apps for real issues during development
Integrations
Frequently Asked Questions
- Is Replay QA free?
- Replay QA offers a free option alongside paid upgrades. Pricing: $17/mo. Check the current allowances and terms before choosing a plan.
Most AI-generated apps ship with no test coverage at all — not because the team doesn’t care, but because writing a test suite takes longer than writing the app did. Replay QA drops into that gap. Give it a URL or connect a GitHub repo, and an autonomous agent explores the running app, writes its own Playwright tests, records every test session using Replay’s time-travel recording engine, and files structured bug reports that include the root cause and a suggested fix. The GitHub path installs as a GitHub App with no config, then runs on every main-branch push, every PR, or both — posting findings directly on the pull request before code merges.
The differentiating layer is the recording engine, which the vendor describes as the same infrastructure used by engineering teams at Vercel, Glide, and Pantheon for debugging production issues. Every bug report comes with a session recording tied to the exact failure point, so the developer — or a coding agent receiving the report — has the full execution trace rather than a screenshot and a stack trace. That context is what makes the output useful as input to an AI coding agent: root cause plus reproduction plus fix suggestion, not just ‘something broke on line 42.’
Replay QA fits solo developers and small teams shipping frequently who cannot staff a QA function. For teams already running Playwright or Cypress, a separate integration records every existing test run, analyzes failures, and posts root cause to the PR automatically — without replacing the existing suite. The wall appears with apps that require authenticated sessions, complex role-based flows, or multi-step journeys the autonomous explorer cannot discover on its own. Teams with that kind of surface area will find the agent covers the easy paths and misses the ones that actually break in production. An API is available for teams building software factories or AI coding platforms that need Replay QA embedded as a quality gate on generated apps.
Contribute
- Work on Replay QA? Claim this listing.
- Embed a badge for your README or site.
Sign in to rate this tool or suggest an edit.