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

# Limits

> Default organization-wide capacity and billing limits

Limits apply to the organization as a whole, across every member, API key, CLI,
SDK, dashboard, and CI job. They are safety defaults rather than pricing
tiers and can be reviewed individually.

## Organization defaults

| Limit                                 |                   Default | What counts                                                                                                                                |
| ------------------------------------- | ------------------------: | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Sandboxes                             |            100 concurrent | Every sandbox that has not been permanently destroyed, including paused and stopped sandboxes. Creates in progress also reserve a slot.    |
| Reserved CPU                          |                 300 vCPUs | The CPU requested by those sandboxes. CPU used above a sandbox's reservation through automatic bursting does not count against this limit. |
| Reserved memory                       | 1,024,000 MiB (1,000 GiB) | The memory requested by those sandboxes.                                                                                                   |
| Active tunnels                        |                       100 | Published, unexpired tunnels attached to live sandboxes. Each sandbox may have up to 8 active tunnels.                                     |
| Unpaid usage without a payment method |                       \$5 | Accrued run.cloud usage that has not been paid or covered by prepaid credit.                                                               |
| Unpaid usage with a payment method    |                     \$500 | The default credit backstop after metered billing is enabled. This is separate from any monthly free grant.                                |

Sandbox creates from the dashboard, CLI, SDK, snapshot restores, and run.cloud CI
all use the same sandbox, CPU, and memory budgets. Whichever limit is reached
first blocks additional creates with `429`. Destroy sandboxes you no longer need
to release their capacity.

Prepaid credit increases the unpaid-usage ceiling. An organization owner can set
a lower spend limit from the billing dashboard; when that customer-set limit is
lower, it becomes the effective ceiling. Reaching the effective ceiling blocks
new resources and stops active sandboxes and simulator sessions.

## Request a higher limit

Email [support@run.cloud](mailto:support@run.cloud) from an address associated
with your organization. Include:

* your organization name or ID;
* the limit you want raised and the requested value;
* the workload and expected duration;
* when you need the additional capacity.

We will review available capacity and billing status, then confirm the limit and
when it takes effect. For planned launches or large temporary bursts, contact us
before the workload starts so we can reserve capacity.