Understand how Expand tiers affect browser concurrency and account limits.
Tiers unlock included browser concurrency as your organization builds successful spend history. They are calculated automatically from cumulative successful spend and the days since your first transaction. There is no plan to pick and no upgrade button to press.
Open your billing dashboard to check your current tier, read Pricing & Usage for the credit and usage model, or add browser concurrency when you need capacity before the next tier unlocks.
| Tier | Qualification | Included browser concurrency |
|---|---|---|
| 0 | Default | 2 |
| 1 | $10 successful spend | 5 |
| 2 | $50 successful spend + 7 days since first transaction |
Tier 0 is the default for every new account. For tiers 2 and up, both requirements must be met. See what counts toward spend, when the timer starts, and provisioned browser slots for the details behind each column.
Expand calculates your tier from two values: cumulative successful spend and days since your first successful transaction. Both requirements must be met. If multiple tiers match, Expand uses the highest matching tier.
The rules:
Successful spend counts toward tier spend. Pending or failed payments do not unlock tiers.
For accounts billed through Expand's billing provider, successful invoices count. The backend counts invoices in a successful state, derives cumulative spend from invoice totals, and uses the earliest successful invoice date as your first transaction date. For local billing, adding funds updates your cumulative spend, first transaction date, and tier directly.
Use the term successful spend when reasoning about tiers. Pending charges, failed charges, and not-yet-synced invoices do not move you up a tier.
Your tier can update after a successful payment, during billing synchronization, or when your account billing state is refreshed.
If you have just paid, expect a short delay while billing state syncs before your tier reflects the new spend. The tier itself is recomputed from your current billing state, so it catches up once the payment is recorded.
If your spend is high enough but your tier has not changed, check the time requirement first. Most tier surprises come from the days-since-first-transaction rule.
The concurrency number in the tier table is included browser concurrency. It controls how many browser-backed Fetch jobs can run at once before additional work queues.
Total browser concurrency = included tier concurrency + provisioned browser slots| Term | Meaning |
|---|---|
| Included tier concurrency | Browser sessions included by the current tier. |
| Provisioned browser slots | Additional paid browser sessions added on top. |
| Total browser concurrency | The effective browser session limit used by Fetch and Batched Fetch. |
This is browser concurrency: the number of live browser sessions running at once. It is not a generic request-rate limit. When you exceed it, additional Fetch and Batched Fetch work queues rather than fails.
Tiers increase included concurrency over time. If you need more capacity before the next tier unlocks, add provisioned browser slots. They are added on top of your tier limit.
Tier 2 includes 10 browser sessions. If you add 20 provisioned browser slots, your total browser concurrency is 30.
Provisioned slots buy capacity, not tier status. They are the right tool when you need parallel throughput now and do not want to wait for spend and time thresholds to catch up.
These follow the tier table exactly. Tier mechanics are easy to misread, so each case is worked through.
You spend $50 on day 1. You are not Tier 2 yet because Tier 2 also requires 7 full days since the first transaction. Until 7 full days have elapsed, the highest matching tier is Tier 1.
Your account is 30 days old but has only $10 in successful spend. Time alone does not unlock Tier 4; the spend threshold must also be met. You stay at Tier 1.
You spend $1000 after 30 full days have elapsed. Tier 5 still requires 60 full days since the first transaction, so the highest matching tier is Tier 4 until 60 full days have elapsed.
You are Tier 2 with 10 included browser sessions and add 25 provisioned browser slots. Your total browser concurrency is 35.
Work down this checklist:
The most common reason is that the spend threshold is met but the time threshold is not.
Storage and retention may appear in pricing copy, but this page does not claim tier-specific retention. Treat retention as confirmed only when the product source of truth says it is tier-backed.
Need concurrency beyond Tier 5 or a committed plan? Contact sales through your account team.
| 10 |
| 3 | $200 successful spend + 14 days since first transaction | 20 |
| 4 | $500 successful spend + 30 days since first transaction | 50 |
| 5 | $1000 successful spend + 60 days since first transaction | 100 |