Every plan includes the complete framework build, unlimited executions, automated maintenance, and human-verified bug reports.
Priced per API — you pay for exactly what you cover, never rounded up to a bundle. Includes build, unlimited execution, maintenance & bug reports. Need 500+? Talk to us for custom volume rates.
* Unlimited runs are subject to a Fair Usage Policy (FUP) of 10,000 executions/month per account to protect sandbox performance and prevent load testing infrastructure abuse. Custom limits are available for high-frequency CI/CD requirements.
Take a typical 60-endpoint API surface and price the first year of automated coverage four ways. The numbers aren't close.
| In-house SDET hire | Hourly QA agency | Per-test platform pricing | QA Watch (60 APIs) | |
|---|---|---|---|---|
| Year-1 cost | $118k–146k salary + benefits Glassdoor, 2024–25 |
~$50–80/hr, open-ended scope | ~$40/test/mo × 180–300 tests ≈ $86k–144k/yr |
≈ $22k all-in build + 12 months |
| Time to coverage | ~3 months to hire, then ramp | 4–8 weeks | Weeks — you drive the tool | First batch in 5 days, live in 2 weeks |
| Execution costs | Your infra bill | Billed hourly | Metered runs / parallelism tiers | Unlimited runs bundled* |
| Maintenance when APIs change | Their job — if they stay | More billable hours | Your team's job | Included + self-healing |
| If you stop paying | Attrition risk, knowledge walks | Code quality varies | Tests locked in the platform | You keep the full Java codebase |
Illustrative comparison at 60 endpoints (≈180–300 TDS outcome tests). Per-test platform figure based on published list rates of incumbent managed-testing services (~$40/test/month).
Because an endpoint is a number you can count and verify — test counts can be inflated. One "API automated" means the endpoint is covered end-to-end and chained into its workflow, with its meaningful outcome tests (typically 3–5: happy path, auth/permission, validation/error, boundary), all defined by the public TDS v1.0 standard. You never pay more because we wrote more scripts.
Yes — there are no bands to round you up. A team with 40 APIs pays the 40-API rate on exactly 40 endpoints, not a padded 50-API bundle. The per-API rate falls smoothly as volume grows; the calculator above shows the exact figure at any count.
Changes to in-scope APIs are covered by the monthly fee — maintenance and self-healing are included, so the suite stays green as your API evolves. Net-new endpoints beyond the contracted volume are simply added at the (lower) per-API rate for your new total.
The one-time build is billed as each weekly batch is accepted — you pay for delivered, runnable coverage, not promises. The monthly subscription starts only at first go-live. Contracts are quoted in USD on a 12-month term, and an all-in option (build amortised into the monthly) is available if you prefer zero upfront cost.
Most platforms lead with UI and treat APIs as an afterthought. We start where your product's real logic lives — the API layer — with proper chained, stateful coverage.
The machine builds; an experienced QA engineer reviews, hardens, and derives the scenarios your team didn't think to ask for. Judgment, not just generation.
Tests are written in open-source Java & RestAssured. The code is exportable and yours from day one — stop any time and keep it all.
You don't operate a platform or hire a team. We handle build, runs, and maintenance end-to-end — at a fraction of doing it in-house.