Billing, credits, and overage

Credits are Tyrbo's single currency: building with AI, running automations, and run-time AI usage all draw from the same balance. This page covers the plans, what consumes credits, and what happens when you use more than your monthly allowance.

Plans

| | Light | Pro | Scale | | --- | --- | --- | --- | | Price | $29/month | $79/month | $199/month | | Credits included | 2,000/month | 8,000/month | 20,000/month | | Overage rate | $0.04 per extra credit | $0.03 per extra credit | $0.02 per extra credit |

Every plan includes the full platform — app integrations, browser automation, the AI builder, run-time AI steps, and cloud plus local runs. Bigger plans add larger allowances, lower overage rates, more seats and devices, a priority run queue, and more concurrent automations.

What consumes credits

Most prices are published and flat; the metered exceptions are agentic AI builds (by agent time + tokens) and run-time AI (by token usage), whose rates are posted too.

| Action | Credits | | --- | --- | | Building an automation with the AI agent | Metered by agent time + tokens (live ticker; per-build cap) | | Confirming an AI edit of an existing automation | 50, flat | | Running an automation on your own device | 5, flat | | Running an automation in the cloud | 10, flat — first 5 cloud browser minutes included | | Extra cloud browser time | 1 credit per started minute beyond the included 5 | | Run-time AI steps | Metered by token usage at posted per-model rates |

Cloud time counts only the minutes a cloud browser is actually working for your run — time spent waiting on your own device, or in app-integration steps, is never billed as cloud time. Runs are capped at 30 minutes of cloud browser time as a runaway backstop.

Chatting with the builder before you press Start build is free — you're charged only once the agent starts building, and a headroom check runs first. Editing an existing automation with AI stays a flat 50, charged on confirm. Runs are charged when they complete, and a pre-run balance check happens before each run is queued (for flows with AI steps, the check budgets a 10-credit allowance per AI step; the debit is always the measured usage). You can see the estimate on every automation card before you run, per-node cost chips in the editor, and a per-step breakdown in run history after. Details on AI metering: Run-time AI steps.

Monthly credits and rollover

Your allowance refreshes at the start of each billing cycle. Credits do not roll over — an unused balance resets to your plan's allowance at renewal, so pick the plan that matches your typical month rather than stockpiling.

Overage

If you use more than your included credits, your automations keep running — the extra usage is billed as overage at your plan's per-credit rate ($0.04 on Light, $0.03 on Pro, $0.02 on Scale) and appears on your next invoice. Overage is metered through Stripe, our payment processor, so the invoice line matches your ledger exactly.

The overage hard cap

If you want a guaranteed ceiling on spend, set an overage hard cap for your organization. Once usage reaches the cap, further runs are blocked until your credits renew (or you raise the cap) — no run can take you past the limit you set. An equivalent cap exists specifically for run-time AI spend: see Run-time AI steps.

The credit ledger

Every credit movement — monthly grants, build debits, run debits, AI usage debits, overage, and adjustments — is a separate entry in your organization's credit ledger, and your balance is exactly the sum of those entries. Nothing changes your balance without a ledger line you can see, and run-related entries link back to the run that caused them.

Managing your subscription

You can upgrade, downgrade, or cancel at any time from billing settings; changes take effect at the end of the current billing period. Payments are processed by Stripe. For the contractual details, see the Terms of Service.