Priced per person, not per test run
Run as often as you like. You are never charged for executing a test, so nobody has to ration the suite to stay in budget.
How the model works
Every plan is a number of seats. A seat is a person who signs in; what that person records, runs, schedules or exports is not metered. A suite that runs on every deploy costs the same as one that runs on Fridays, which matters because the moment a run has a price, somebody starts deciding which tests are worth it — and the suite stops being the thing you trust.
Two things hold across all four plans. Every plan runs on your own
infrastructure: the browsers are yours, and healing happens locally rather
than on someone else's server (see where it runs).
And your tests export to plain C# whenever you want to leave — a normal
.NET project that compiles and runs with dotnet test, with or
without QAright.
The plans
Free
One person testing their own app, on their own machines.
$0 forever · No card. One seat.
- Unlimited tests, suites and runs
- Ranked locator candidates, scored for stability
- Self-healing cascade and healing report
- Element inspector and assertion builder
- Reports, screenshots and analytics, with PDF/CSV export
- Unlimited export to a standalone C# Playwright project
- Two environments and two data profiles
- Five of each AI feature a month
- 30 days of run history
Solo
One engineer keeping a suite alive alongside everything else.
$15 / month · Introductory price. Billed monthly. One seat.
- Everything in Free, plus
- Guardian drift detection, on up to 5 URLs
- Scheduled runs, CI/CD triggers and API keys
- Your AI assistant (Claude Code, Cursor, VS Code) connected over MCP
- Parallel runs across two browsers at once
- Unlimited environments and data profiles
- Up to 3 projects
- 100 AI generations a month, and 50 of everything else
- 90 days of run history
Team
A QA team sharing suites across environments and a pipeline.
Custom · Per seat, 3 to 10 seats. Talk to us.
- Everything in Solo, plus
- Up to 10 seats, with roles and user management
- Guardian on every URL you record
- Parallel cross-browser runs, up to 4 at once
- Unlimited projects, and webhook notifications
- Version history and audit log
- Test executions: named test cycles, assigned per tester, manual and automated together
- Spec-driven testing, and page divergence diagnosis on failed runs
- 500 AI generations a month, and 250 of everything else
- A year of run history
A note on paid pricing
Questions people ask before paying
- What happens to my tests if we stop paying?
You export them. Suites become a self-contained .NET project that compiles and runs with
dotnet test, including the resilient execution engine and your recorded fallbacks. There is no proprietary run format holding your work hostage.- Do I need to know how to code?
No. Recording, editing and running a suite is entirely visual, and each step can be read as a plain-English description. If you do write code, every suite exports to a normal C# Playwright project you can own outright.
- Which browsers are supported?
Chromium, Firefox and WebKit, headed or headless, and a suite can be run across several of them in parallel in a single execution. How many at once depends on the plan: two on Solo, up to four on Team.
- Does connecting my AI assistant use my AI allowance?
No. On Solo and above, Claude Code, Cursor, VS Code or Claude Desktop connects over MCP with a key you create in Settings. The reasoning is your assistant’s; QAright runs the tests and answers its questions, so your plan’s AI generations are untouched. It works as you, with a tester’s permissions.
- Can it test an app behind a login?
Yes. Authentication is recorded once as a reusable preamble and replayed to establish a session, which the suite and Guardian both reuse. Credentials live in an environment, not in the test.
Free forever, and no card. Record your first test in about the time it would take to write one.