Concurrency tiers

Each tier raises the number of browsers included with your account.

Tier table

Every new account starts at Tier 0. For Tiers 2 to 5, both conditions must be met.

How tiers are calculated

Expand calculates your tier from two values, the dollar value of the credits your organization has spent and the days since its first transaction. Your tier is the highest one whose spend and time conditions you both meet.

• Tier 0 is the default until you qualify for a higher one.
• Spend alone is not always enough. Tiers 2 to 5 also need days to pass.
• Time alone is never enough. Every tier above 0 has a spend threshold.
• The days count from your first settled operation, not from signup.

What counts toward spend

Spend is the value of the credits your organization has used, at the public rate of $1 per 1,000 credits. Every settled operation adds its credits to your spend, and your first settled operation starts the day count.

• Buying credits does not count. A purchase raises your balance, not your tier. The tier moves as you spend the credits.
• Failed, blocked, or empty operations cost nothing and add nothing.
• Spend is measured at the public rate whatever you paid per credit.
• Organizations that started on our previous billing system keep the spend and the first-transaction date of the invoices they paid there.

When your tier updates

Your tier is recomputed each time an operation settles. When a settlement carries you across a threshold, the new browser concurrency applies to your next request. There is nothing to do.

Settlement normally follows the operation within seconds. A Batched Fetch settles once the whole run finishes, so its spend lands when the run does.

Browser concurrency

The concurrency number in the tier table is the browser concurrency included with your tier. It is the number of browser captures your organization can run at once.

Browser concurrency is not a request rate limit. At your limit, a single Fetch is refused with 429 FetchConcurrencyLimitExceeded and Batched Fetch queues instead. See Limits.

Provisioned browsers

If you need more browsers before the next tier, add provisioned browsers on top of your tier. They raise your total browser concurrency and leave your tier unchanged. Cost and timing are on Provisioned browser concurrency.

Examples

Each example follows the tier table.

Spend before time

You spend $50 on day 1. Tier 2 also needs 7 days since your first transaction, so until then you are at Tier 1.

Time without spend

Your account is 30 days old and has spent $10. Tier 4 needs $500, so you stay at Tier 1.

Higher spend, waiting on time

You have spent $1,000 after 30 days. Tier 5 needs 60 days, so you are at Tier 4 until day 60.

Provisioned browsers

You are at Tier 2 with 10 included browsers and add 25 provisioned browsers. Your total browser concurrency is 35.

Why am I not in the next tier?

Work down this list:

• Have you spent enough? See What counts toward spend.
• Have enough days passed since your first settled operation?
• Have your operations settled? A Batched Fetch that is still running has not been counted yet.
• Are you counting purchased credits? Only spent credits count.
• Are you reading your tier concurrency, or your total after provisioned browsers?

The most common cause is that the spend threshold is met and the time threshold is not.

What tiers do not change

• Tiers are not pricing plans.
• Tiers do not change what an operation costs in credits. See Pricing & Usage.
• Tiers do not add or remove provisioned browsers.
• Tiers do not set time or size limits. See Limits.

For browser concurrency beyond Tier 5, or a committed plan, email support@expand.ai.

Next steps

• Pricing & Usage: credits, costs, and provisioned browsers.
• Limits: what happens at your concurrency limit, and every other limit.
• Batched Fetch: fetch many URLs within your concurrency.
• FAQ: short answers to billing questions.