Usage & billing
Know what counts, what is included and when running time stops.
| Plan | Monthly price | Included hours | Concurrency | Overage |
|---|---|---|---|---|
| Free | $0 | 1 | 1 | Automatically pauses at limit |
| Basic | $20 | 250 | 10 | $0.08/hour |
| Pro | $99 | 1,250 | 100 | $0.06/hour |
What counts
Runtime adds up across browsers. Ten browsers running for thirty minutes use five browser-hours. Multiple connections to the same browser do not multiply the charge. Closing a viewer or CDP client does not stop runtime.
Concurrency
Creating or resuming reserves a running slot atomically. Paused browsers do not occupy active slots. Pro customers can request higher concurrency at no additional quota fee; extra runtime is still billable.
Monthly estimate
Basic = $20 + max(0, hours − 250) × $0.08
Pro = $99 + max(0, hours − 1250) × $0.06Billing periods and plan changes
Free includes one hour per UTC calendar month. At the limit, running browsers automatically pause and new starts are blocked until an upgrade or the next month. The enforcement worker checks every ten seconds; an in-flight pause can take longer.
Paid plans renew on their subscription anniversary. Runtime is accumulated across browsers at second precision. The monthly subscription and additional usage are separate invoices; additional usage is calculated at period close and rounded once to the nearest cent. Unused hours do not roll into the next period.
Basic to Pro takes effect after payment of the prorated price difference. Your unused hours remain available, plus the prorated increase in included time. Earlier overage keeps its original rate. Downgrades and cancellation take effect next period; browsers above the new concurrency limit pause.
Failed renewal or additional-usage payment blocks new starts and pauses running browsers. Update your payment method or pay the outstanding invoice through Usage & plan. Payment confirmation restores the ability to resume; browsers do not start automatically.
Manage billing
The workspace owner can choose a plan, preview an upgrade, schedule a downgrade, and open Stripe to manage cards and invoices. The API exposes billing/status, billing/checkout, billing/upgrade-preview, billing/plan, billing/portal and billing/refresh. Mutation requests for checkout and plan changes require an Idempotency-Key. Reuse the same key when retrying the same request. Billing returns 503 until Stripe is configured.
The Go CLI is not implemented yet. Use the Console for payments; the planned cloudbrowser usage command reports allowance, period and runtime.
Storage
Stored profile allowances, paused browser retention and deletion policies are still being finalized.
Explore plans and the cost calculator