What counts toward my monthly allowance?
Only AI-written tests: each test Verity generates for you — UI, API, visual, AI-agent eval or load test — counts once. Running tests never counts, so your suite can run on every commit.
Every plan — including Free — writes UI, API, visual, AI-agent, load and security tests. You pay for the tests Verity writes, never for runs in your own CI. Add a QAShift engineer when you want the suite owned for you.
Four self-serve plans, no sales call. Plans differ by how many tests Verity writes for you each month, self-healing, pull-request checks and projects.
A dedicated QA hire can cost $8,000+/mo. Managed Verity with a forward-deployed engineer starts at $499/mo. Or start self-serve from $0.
Everything you need to see it work on your own app. No card.
NOT INCLUDED
One product, tests that fix themselves, results on every PR.
For a team shipping one or a few products every week.
For several products, squads or services.
A forward-deployed QAShift engineer builds, maintains and triages your suite inside your release rhythm — you get the outcome, not another tool to run.
Same pricing across the QAShift platform. View full managed pricing →
Managed Testing pairs Verity with a forward-deployed engineer who works inside your release rhythm. They do not hand you reports; they keep the verification system useful.
Explore FDE Managed Testing →| Verity | DIY Playwright | AI per-test tools | Managed QA agency | |
|---|---|---|---|---|
| AI generates the tests | manual | |||
| UI, API, visual, AI-agent, load & security | usually UI + API | varies | ||
| Self-healing locators | from Pro | some | manual | |
| Flaky ≠ broken (auto-triage) | rare | manual | ||
| Runs in your own CI | sometimes | |||
| Regression & risk predictions | managed plans | |||
| A human engineer owns the suite | managed plans | |||
| Unlimited runs in your CI | free but DIY | credits per run | retainer | |
| You own the code | varies | varies |
Self-hosted execution keeps sensitive application access within your infrastructure, while Verity returns the verdict and retained evidence your team needs.
Only AI-written tests: each test Verity generates for you — UI, API, visual, AI-agent eval or load test — counts once. Running tests never counts, so your suite can run on every commit.
Yes, on every plan including Free. Your CI provides the compute, so Verity never meters executions there. Cloud runs (our browsers, no CI needed) are capped per plan.
All of them: UI, API, visual, AI-agent, load and security. Paid plans add volume, self-healing, pull-request checks and more projects.
Credit-based tools usually charge every time a test runs on their servers. Verity charges for writing tests and lets you run them free, forever, in your own pipeline — as plain Playwright code you own.
Yes. Tests are readable Playwright (plus a load-test script and an eval YAML file) committed to your repository. If you cancel, they keep running.
Yes. Pay monthly, or yearly to save 20%; there is no contract beyond the period you've paid for. Email hello@qashifthq.com to change or cancel. Your tests stay in your repo either way.
When you want the outcome owned rather than another tool to operate. A QAShift engineer takes responsibility for strategy, coverage, maintenance, failure triage and release reporting.
Tests and scans run inside your CI, so code and secrets stay in your infrastructure; only results are sent to Verity.