Verity
The engine underneath QAShift. Playwright, axe-core, ZAP, Semgrep.
Useful when replacing: a pile of half-configured testing tools
Pricing · USD
Plans
From $49/mo
A hosted product with a free tier. Start on it, stay on it, or leave — no contract.
Free tier
Free tier · no card
Start free, no card. Upgrade when the limits bite, not before.
Start free: cloud sandbox, 15 AI-generated UI tests a month, unlimited CI runs once your pipeline is configured. Pro is $49/mo — 200 UI + API tests, self-healing locators, flake detection, 3 projects. Team is $149/mo — 750 tests, 10 projects, priority support. Want an engineer verifying every test? That's managed QAShift, from $499/mo. CI runs are unlimited on every tier; the AI test generation is what's metered, because that's what costs us money to run.
The problem
Playwright, axe-core, ZAP, and Semgrep are all excellent — and all separate. Wiring them into one pipeline, keeping them updated, and making their output readable is a full-time job nobody was hired for.
How Verity solves it
One engine, four disciplines
Functional, accessibility, security, and static analysis run as a single orchestrated suite with one unified report.
Runs in your infrastructure
Self-hosted, MIT licensed. Your code and test artifacts never leave your network.
CI-native
Drops into GitHub Actions, GitLab CI, or Jenkins as a single step. Fails the build with reasons, not noise.
Delivery terms — stated precisely
How Verity is delivered, what you control, and where the boundaries sit.
Managed cloud
Hosting and data terms are stated on the product plan.
Data and hosting
This is a managed product. Plan limits, data processing terms, retention, and any self-host option are stated for that product — not implied by a company-wide promise.
Compliance boundary
Residency, controls, and regulatory requirements are implementation decisions documented in the selected plan or delivery scope.
Built on
Verity — the questions buyers ask
Who owns the code and IP?
For a Build Sprint, the repository, deployment assets, and work-product IP described in the SOW are handed over to you. Pre-existing products retain the licence shown on their product page; hosted services remain services. We state that boundary before work starts.
What happens if a sprint misses its scope?
We finish it. Fixed price means the risk of estimation is ours, not yours — a missed scope item is completed without a new invoice. Changes you request are re-scoped explicitly, so the line between 'our miss' and 'new ask' stays honest.
How do time zones work with a pod in India?
Every engagement includes 4+ hours of overlap with US or EU working hours. Async by default — written updates, weekly clickable demos — and meetings only when they earn the slot. You'll never chase a status report.
How is our data and code kept secure?
Work happens in your repos and your infrastructure wherever possible — we hold the minimum access needed, revoked at handover. NDAs are standard on request, and everything we self-host for you runs behind your keys, not ours.
How fast can you actually start?
Scoping takes a day; most sprints start within a week of sign-off. Pods are deliberately small and senior, so your start date is confirmed in the sprint plan — not left floating.
Do we need a retainer afterwards?
No — that's the point. A sprint ends with handover docs and training. If you want us to keep maintaining what we built, that's an optional flat monthly add-on you can cancel any month, because the software keeps working without us.
Own Verity, don't rent it.
See the price, deploy on your infrastructure, keep the code. Or scope a sprint and we'll customise it and hand it over.