Solutions for confident releases.
Simple pricing that maps to real delivery.
Test Kit turns recordings into maintainable regression coverage with evidence you can trust. Pricing is per workspace (a release/spec boundary), and each workspace includes a defined number of workspace completions (formal sign-offs) plus a monthly server testing compute time allowance.
Two terms, zero jargon
Workspace = one release/spec (the unit you deliver).
Workspace completion = a formal sign-off of that workspace (with a preflight warning in-app).
Testing compute time = server-side execution time for tests (runner time doesn’t count).
Example: “Magento upgrade — Sprint 3” is a workspace. You record journeys, review submissions, convert them into tests,
track objective coverage, then complete the workspace to capture a deliberate “done” milestone.
Why teams choose Pro
- Multiple sign-offs: UAT → Regression → Go-live (or hotfix) without re-creating a workspace
- Client delivery: you want clear, repeatable “done” milestones with evidence
- Iterative releases: you expect to re-open and re-complete a workspace as delivery evolves
Per workspace
Free
Ideal for a single sign-off cycle.
- Record journeys with the runner
- Review/approve submissions
- Convert approved work into real tests
- Track objectives coverage
- Workspace completions: 1 per workspace
- Testing compute time (server): 30 minutes / month
Per workspace
Pro
For iterative delivery and multiple sign-off cycles.
- Workspace completions: 3 per workspace
- Testing compute time (server): 10 hours / month
- Supports UAT → Regression → Go-live style sign-off
- Higher throughput for submissions and conversions
- Better for teams running ongoing delivery
For larger orgs
Enterprise
Governance, audit, and high-volume delivery.
- Priority support options
Free vs Pro — concrete differences
| Capability | Free | Pro |
|---|---|---|
| Workspace scope | Per workspace | Per workspace |
| Workspace completions (close out workspaces) | 1 / workspace | 3 / workspace |
| Testing compute time (server execution) | 30 minutes / month | 10 hours / month |
| Throughput (submissions / conversions) | Good for a single stream | Designed for ongoing delivery |
| Best for | Evaluating the workflow | Teams shipping regularly |
| Enterprise controls | — | Available in Enterprise (SSO/audit) |
If you need more than 3 sign-offs per workspace, that’s typically an Enterprise conversation.
A clearer “why Pro?”
Pro is for teams who need multiple deliberate sign-offs for the same release/spec (UAT, regression, go‑live).
You get 3 workspace completions per workspace, so the tool matches how real delivery actually works.
© 2026 Azzure · Test Kit