Pricing
Subscribe per seat and get monthly AI and compute credits, or pay as you go from a prepaid balance with no monthly bill. Every plan includes every test engine.
$25 to start
No monthly bill · Single seat
Annual billing saves 10%. Default list prices shown. Your workspace's billing page is authoritative.
Plans differ by seats and included credits, not by features. A solo developer on Pro and a 25-person team get the same engines, evidence and integrations.
Browser missions, site explorations, API, load, responsive, i18n and security tests, and MCP server missions all draw on the same credits. No add-ons per test type.
Upload PRDs, user stories and feature docs; the AI plans risk-based scenarios from them and keeps a test plan current as specs change.
Screenshots, network traffic, console errors and step-by-step reproduction for each bug, UX issue and spec mismatch.
axe-core WCAG audits and a nine-lens UX evaluation run as part of every browser scenario at no extra charge.
A REST API with pipeline exit codes, plus Markdown, JUnit and SARIF exports, so a run can gate a pull request.
Passing runs become baselines. Cheap regression profiles and cached-path replays re-check them for a fraction of a first run.
Is It Ready meters two things separately, because they cost different amounts to provide. AI credits cover the language-model work in a run: reading your specs, planning scenarios, choosing every browser action, judging outcomes, and scoring the experience. Compute credits cover the runner — the real browser or protocol client executing the test — at 1 minute of wall-clock time per credit.
Pro and Team include 1,000 AI credits and 500 compute credits per organization each month. Pro is a single seat at $99 per month; Team is $125 per seat for 2 to 25 people. Top-up packs are available on every plan whenever a busy release cycle needs more.
Before a run starts, Is It Ready checks both balances and reserves an estimate based on your own recent runs, so you can never start work you cannot cover. When a run finishes, it is debited for what it actually used, and the run page shows the cost broken down by phase and by scenario so you can see where the spend went.
The biggest lever on cost is the cost profile on each mission. A thorough profile plans more scenarios and lets the agent take more steps; a regression profile replays a known-good path with a cheap planner. Teams typically explore a new feature thoroughly once, then gate every pull request with a regression replay.
Security and data handling are part of the product, not an upsell.
Domain-verified security testing
Security scans and red-team missions only run against domains your organization has verified.
Credentials never stored in evidence
Sign-in values are redacted from run evidence; only the outcome and landing page are recorded.
Configurable retention
Run evidence is redacted after 90 days by default, adjustable per organization.
Isolated workspaces
Every app, spec, run and API key belongs to one organization and is invisible to every other.
CI-native output
Exit codes for pipelines, plus Markdown, JUnit and SARIF exports for GitHub code scanning.
Plug runs into GitHub Actions, GitLab CI, Jenkins, Azure Pipelines or CircleCI with the REST API: start a run, poll it, and exit non-zero when findings cross your severity threshold. See how it works on the spec-driven testing page.
Turn PRDs, user stories and feature docs into risk-based test scenarios an AI agent runs in a real browser.
Exercise, contract-test and red-team Model Context Protocol servers the way a real MCP client would.
axe-core WCAG audits on every page the agent visits, with UX scoring and evidence alongside each violation.
Start on pay as you go with no commitment, or get a free scan of your site first.