---
title: "Plans & limits"
description: "What a subscription buys: browsers running at the same time and machines, counted across your whole account, plus what happens when a payment fails or a plan ends."
canonical: "https://scalebrowser.net/docs/account/plans"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://scalebrowser.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans & limits

> What a subscription buys: browsers running at the same time and machines, counted across your whole account, plus what happens when a payment fails or a plan ends.

Two numbers are sold, and neither of them is the number of profiles.

**Profiles are unlimited.** Make two thousand. What the plan limits is how many of them have a browser open at the same time, and on how many machines.

## The limits
| Plan     | Browsers at once | Machines |
| -------- | ---------------- | -------- |
| `none`   | none             | none     |
| `start`  | 1                | 1        |
| `solo`   | 5                | 1        |
| `studio` | 20               | 3        |
| `fleet`  | 50               | 10       |

Prices are on the [pricing page](/pricing), because they change without a code release and a number written here would be wrong the first time they do.

Both numbers count **across your whole account**, not per machine. Three machines with two browsers each is six browsers.

## Why concurrency and not profiles
Because a profile at rest costs nothing and a running browser costs 250 to 400 MB. Charging for profiles would charge for a row in a database, and it would push you into reusing identities, which is the one thing this product exists to stop.

The shape that follows is normal here: two hundred profiles, five running. That is why the [task list](/docs/agents/tasks) exists, and why [`lease_fleet`](/docs/fleet) hands back what it managed rather than failing.

## What happens at the limit
| Situation                                 | What you get                                                                          |
| ----------------------------------------- | --------------------------------------------------------------------------------------- |
| Your subscription's browsers are all busy | Error `4008`. Release a running browser anywhere, or move up a plan.                    |
| **This machine** is out of memory or slots | Error `4003`. Waiting helps; nothing about your plan is involved.                       |
| One profile is open on another machine    | Error `4012`. Close it there, or take it over. Costs nothing.                            |
| No account connected to this machine      | Error `4011`. Sign in.                                                                   |

<Note>

**`4003` and `4008` are opposite problems.** One is your machine, one is your subscription. A client that folds them together sends you to the wrong place: to the pricing page when you needed to close a tab, or the other way round.

</Note>

## Add-ons
Two, both per unit and both on top of any plan: extra concurrent browsers, and extra machines. They are the answer when one number is the constraint and the other is not, so you do not buy a whole tier for one extra browser.

## No free tier, and no unlicensed mode
There is no version of this that runs without a paid account. A free tier stood from August 18 to August 30, 2026 and was withdrawn: it carried the entire product at zero, with no feature gating between tiers, unlimited profiles, and the same engine download that is the moat itself.

An account with no subscription is `none`: zero browsers, zero machines, no engine download, no sync write. Reads and deletes stay open, so nothing you have made is ever held hostage.

**The way in is the trial.** Seven days, one browser. And [`/check`](https://scalebrowser.net/check) and [`/ai-agent-check`](https://scalebrowser.net/ai-agent-check) stay account-free forever: the visitor who arrives asking why they were blocked gets an answer without a card.

## When a payment fails
The subscription falls back to the entry tier rather than to nothing. One browser keeps working while you fix the card.

## When the control plane cannot be reached
A daemon that cannot reach the control plane keeps working for a grace window, because an outage on our side must not stop your work.

<Warning>

**A refusal is not an outage.** If your machine was explicitly removed from the account, it stops immediately rather than collecting the grace window. Hiding a removal for hours behind a screen that still says "connected" is worse than stopping.

The window is also anchored against the clock: winding your system time backwards does not extend it.

</Warning>

## Next
- [Machines & sign-in](/docs/account/machines): what a machine is and how one is added or removed.
- [Errors](/docs/errors): `4003`, `4008`, `4011` and `4012` in full.
- [Groups, presets & bulk](/docs/fleet): working a fleet that is larger than your concurrency.