Write all the tests you want. Pay only for the runs.
Authoring, editing and keeping tests current never costs a token. You’re charged for execution, measured one step at a time, so the bill tracks what you actually ran.
Three plans. One unit: the executed step.
Prove it works on your own app before you pay anything.
Start free- Unlimited test generation
- Unlimited change intelligence
- API tests
- RCA reports
- MCP access
- 1 app, 1 seat
A full regression suite running on every build, for one engineer.
Get started- Everything in Trial
- 5,000 tokens a month
- 1 parallel execution
- 2 apps
- Forward-deployed engineer support
More authors, more apps, and runs on every pull request.
Talk to sales- Everything in Solo
- Custom token volume
- Custom parallel execution
- Custom apps and seats
- Forward-deployed engineer support
What a Drizz Token buys.
One token covers one executed step. Nothing else in the product is metered, so the only number that moves your bill is how much you run. A test you write and don’t run costs nothing, so there’s no reason to keep your suite small.
- 1Tap “Checkout”
- 2Type email
- 3Type password
- 4Tap “Sign in”
- 5Tap “Cart”
- 6Type “SAVE10”
- 7Tap “Apply”
- 8Validate discount
- 9Tap “Place order”
- 10Validate confirmation
Compare plans
Test generation and change intelligence are unlimited on every plan.
Sized to your simulated company.
Agent testing is priced by which twins your company needs, how much seeded history it carries, and the run volume you want. Every team starts with a scoped pilot on one scenario, so you see a report before you commit.
- Pilot: one scenario, twenty runs, a graded report, no charge
- Private twins per team, reset in one call
- The report is yours: fix the agent, compare models, or train on the runs
Pricing questions
Mobile app testing has three plans. Trial is free with 300 Drizz Tokens, around 30 test runs. Solo is $49 a month with 5,000 tokens, around 500 runs. Team is custom priced and sized to your suite, apps and seats. Agent testing is sized per team: book a demo and we’ll quote.
One token covers one executed test step. A typical test is around ten steps, so 300 tokens runs roughly 30 tests and 5,000 runs roughly 500. Writing and editing tests never consumes tokens; only execution does.
Runs are blocked once the balance reaches zero. Top up and execution resumes. Writing and editing tests keeps working.
By the size of the simulated company (which twins, how much seeded history) and the run volume you need. Every team starts with a scoped pilot on one scenario, so you see a report before you commit.