# Limits and Pricing for Render Sandboxes

> This article is part of the [Render Sandboxes documentation bundle](https://render.com/docs/sandboxes/all). Fetch the bundle for all related articles in one Markdown document.


> *Render Sandboxes is in public beta.*
>
> APIs, defaults, and limits might change during the beta period.

The following limits and pricing apply to Render Sandboxes. Limit and pricing details are subject to change during the beta period.

## Compute plans and billing

Each sandbox uses one of the following compute plans, which determines its specs and pricing. You specify which plan to use when you [create a sandbox](/docs/sandboxes-creating.md#compute-plan).

| Plan | Specs | Price |
| --- | --- | --- |
| `1c-2g` (default) | 1 CPU 2 GB RAM | $0.12 / CPU-hour + $0.038 / hour ($0.00200000 / CPU-minute + $0.00063333 / minute, $0.00003333 / CPU-second + $0.00001056 / second) |
| `2c-4g` | 2 CPU 4 GB RAM | $0.12 / CPU-hour + $0.076 / hour ($0.00200000 / CPU-minute + $0.00126667 / minute, $0.00003333 / CPU-second + $0.00002111 / second) |
| `4c-8g` | 4 CPU 8 GB RAM | $0.12 / CPU-hour + $0.152 / hour ($0.00200000 / CPU-minute + $0.00253333 / minute, $0.00003333 / CPU-second + $0.00004222 / second) |
| `8c-16g` | 8 CPU 16 GB RAM | $0.12 / CPU-hour + $0.304 / hour ($0.00200000 / CPU-minute + $0.00506667 / minute, $0.00003333 / CPU-second + $0.00008444 / second) |

### How billing works

Sandboxes are billed differently for CPU and memory usage:

------

##### CPU

Billed at $0.12 per CPU-hour, based on the total amount of CPU your sandbox _actually uses_:

- If a sandbox on the `1c-2g` plan constantly uses its full 1 CPU for one hour, Render bills $0.12 for CPU usage.
- If the same sandbox uses only 0.5 CPU for one hour, Render bills $0.06 for CPU usage.

##### Memory

Billed at $0.019 per GB-hour according to your sandbox's _total_ provisioned memory (regardless of actual usage).

------

A sandbox is _not_ billed for CPU or memory usage while [suspended](/docs/sandboxes-creating.md#idle-timeout).

## General limits

------

##### Writable filesystem storage per sandbox

40 GB

##### Maximum runtime timeout

- If you set a runtime timeout, the maximum allowed value is 30 days.
- You can also _disable_ this timeout entirely to prevent automatic termination.

Learn more about [sandbox timeouts](/docs/sandboxes-creating.md#timeouts).

##### Maximum idle timeout

- If you set an idle timeout, the maximum allowed value is 24 hours.
- You can also _disable_ this timeout entirely to prevent automatic suspension.

Learn more about [sandbox timeouts](/docs/sandboxes-creating.md#timeouts).

##### Suspended sandbox resumability period

30 days

##### Sandbox groups per workspace

10

##### Concurrent sandboxes per sandbox group

Default: 1,000 for *Pro* workspaces and above, 100 for *Hobby* workspaces

You can request an increase to 5,000 for a *Pro* workspace or 10,000 for a *Scale* workspace.

[See details below.](#concurrency-per-group)

##### Environment variables per sandbox

100 variables, with a combined size of 256 KB across names and values

##### Supported regions

1 (Oregon)

------

> *Need to increase any of these sandbox limits?*
>
> Reach out with details about your use case:

### Concurrency per group

By default, each sandbox group in a *Pro* workspace or above can have up to 1,000 concurrent sandboxes, and each sandbox group in a *Hobby* workspace can have up to 100 concurrent sandboxes.

- In some cases, Render might enforce a temporarily reduced concurrency limit for newly created workspaces with minimal billing history.
- You can request a limit increase to 5,000 for a *Pro* workspace or 10,000 for a *Scale* workspace. To request an increase, please [contact Render](/contact).
- [Suspended](/docs/sandboxes-creating.md#idle-timeout) sandboxes do not count toward concurrency limits.
  - To resume a suspended sandbox, its group must be under its concurrency limit.
- You can [reduce the concurrency limit](/docs/sandboxes-creating.md#setting-group-concurrency) for an individual group.

- While a group is at its concurrency limit, requests to create or resume a sandbox fail with HTTP code `429`.
    - To reclaim capacity, [terminate](/docs/sandboxes-creating.md#terminating-a-sandbox) sandboxes you no longer need.

## API rate limits

Sandbox API operations have separate default rate limits. These limits apply per user, shared across that user's API keys. Requests that exceed a rate limit fail with HTTP code `429`.

| Operation | Requests per minute |
| --- | --- |
| *[Create a sandbox](/docs/sandboxes-creating.md)* | 100 |
| *[Terminate a sandbox](/docs/sandboxes-creating.md#terminating-a-sandbox)* | 1,000 |
| *Execute a [command](/docs/sandboxes-executing.md)* | 1,000 |
| *[Upload or download](/docs/sandboxes-files.md) a file or directory* | 1,000 |
| *Read sandbox and sandbox group resources* | 400 |
| *Write sandbox group resources* | 100 |
| *Capture a [snapshot](/docs/sandboxes-snapshots.md)* | 10 |


---

##### Appendix: Glossary definitions

###### Render Sandboxes

Create a sandbox to execute untrusted code in a managed, ephemeral environment.

Ideal for agents, code interpreters, builds, tests, and other workloads that require isolated execution.

Related article: https://render.com/docs/sandboxes.md

###### compute plan

Specifies the CPU and RAM available to a running *instance* on Render.

For example, common compute plans for a new *web service* include:

- *`free`*: 0.1 CPU / 512 MB RAM
- *`0.5c-512mb`*: 0.5 CPU / 512 MB RAM
- *`1c-2g`*: 1 CPU / 2 GB RAM

Compute plans were previously known as *instance types*.

Related article: https://render.com/docs/compute-plans.md

###### region

Each Render service runs in one of the following regions: *Oregon*, *Ohio*, *Virginia*, *Frankfurt*, or *Singapore*.

Services in the same region can communicate over their *private network*.

Related article: https://render.com/docs/regions.md