Billing & Credits
VeriWasp is pay-per-use: there's no subscription, no monthly minimum, and no expiring plan. You buy credits, and every run spends credits from your balance at the moment you start it.
How much a run costs
| Run type | Cost |
|---|---|
| Normal run | 1 credit |
| Run with Chaos Mode enabled | 3 credits |
This is flat regardless of step count. A 3-step scenario and a 20-step scenario cost exactly the same, 1 credit (or 3, with Chaos Mode). The billing page states this explicitly: "1 credit = 1 test run, no matter how many steps it has."
Free signup credits
The first time you create a VeriWasp account, you're automatically granted a small number of free credits (currently 3), enough to try the product without entering payment details first. This grant happens exactly once per account, the moment your very first magic link is verified.
Three was chosen deliberately to match the cost of a single Chaos Mode run (see the table above): a new account can spend its free credits on three standard runs, or use them all at once to try Chaos Mode a single time.
Buying more credits
The Billing page (/billing, linked from the top nav wherever you're
logged in) shows your current balance and three credit packs to purchase:
| Pack | Credits | Price | Effective rate |
|---|---|---|---|
| Starter | 1 | $0.99 | $0.99/test |
| Popular | 10 | $7.99 | ~$0.80/test (19% off) |
| Bulk | 25 | $14.99 | ~$0.60/test (39% off) |
Each pack's card shows both its total price and its effective per-credit price, so the discount from buying in bulk is explicit rather than something you have to calculate yourself.
Clicking Buy on a pack redirects you to a Stripe Checkout session, Stripe's own hosted payment page, so your card details never pass through VeriWasp's own servers at all. After a successful payment, Stripe sends a webhook back to VeriWasp confirming the purchase, which is what actually credits your account. See How crediting works below for the short delay this can introduce.
How crediting actually lands in your balance
Your visible credit balance is a cached number on your account; the actual source of truth is an append-only ledger. Every credit grant (a purchase, the free signup bonus) and every credit spend (starting a run) is recorded as its own entry, and the balance is the sum of that ledger.
When you complete a Stripe Checkout purchase, Stripe processes the payment and then calls VeriWasp's webhook endpoint asynchronously to confirm it. This typically happens within a few seconds, but isn't instantaneous. If you land back on VeriWasp's success page and your balance doesn't reflect the purchase yet, that's why: the payment succeeded, but the webhook confirming it to VeriWasp hasn't been processed quite yet. Give it a few seconds and refresh.
Insufficient credits
If you try to start a run (from a draft, a re-run, or a CI trigger) and your balance doesn't cover its cost, you're shown an out of credits message with a direct link to the billing page, rather than the run silently failing or getting queued anyway. No partial deduction happens: either the full cost is available and gets deducted, or nothing is deducted at all.