Credits and What They Cover
Cloud TestVibe uses one workspace credit balance for model usage and execution time.
| Activity | What can use credits |
|---|---|
| Generation | Model tokens plus sandbox time for authoring, browser checks, repairs, and verification. |
| Assistant | Model calls and background sandbox time. |
| Test runs | Execution time while the sandbox runs tests and collects evidence. |
| Load testing | Execution time across the load machines used by the run. |
| Coverage and optional analysis | Their model calls and execution time when requested. |
Editing features, reviewing saved results, and browsing settings do not spend credits. Pre-written starter scripts need no paid generation, but running them still uses execution credits.
Model rates depend on the model and token types, including cache reads. Execution rates depend on the activity and allocated machines; a minute of a sharded load test is not one machine-minute. Review the estimate and selected model before starting substantial work.
Balance order
Included plan allowance is consumed first, followed by purchased credits. Paid allowances reset on the date displayed in Billing and do not roll over. Free's welcome credits are a one-time grant, not a recurring monthly allowance. Purchased packs persist.
New work is stopped when no usable credits remain on every cloud plan. TestVibe does not offer an automatic unlimited paid-plan overage balance. Add credits or change plan in Settings → Billing to continue.
Credit packs and usage
A pack grants the credits listed in checkout, with no extra percentage bonus. Use the currently offered pack sizes and prices in Billing rather than an older price table.
Settings → Credit Usage shows consumption by activity. Settings → Billing shows the balance, plan, and additions. Self-hosted instances do not use TestVibe credits; operators pay their own infrastructure and provider costs.