Limits for Render Sandboxes
Render Sandboxes is in public beta.
APIs, defaults, and limits might change during the beta period.
The following limits apply to Render Sandboxes. All limits are subject to change during the beta period.
Compute plans
Each sandbox uses one of the following compute plans, which you specify when you create a sandbox:
| Plan | Specs |
|---|---|
|
|
1 CPU |
|
|
2 CPU |
|
|
4 CPU |
|
|
8 CPU |
General limits
| Property | Limit |
|---|---|
|
Writable filesystem storage per sandbox |
40 GB |
If a sandbox is suspended and later resumed, this limit resets. | |
|
24 hours (you can also disable idle timeout entirely) | |
|
Suspended sandbox resumability period |
30 days |
|
10 | |
|
Concurrent sandboxes per sandbox group |
1,000 |
|
Environment variables per sandbox |
100 variables, with a combined size of 256 KB across names and values |
|
Supported regions |
1 (Oregon) |
Need to increase these sandbox limits?
Reach out with details about your use case:
Concurrency per group
- Each sandbox group can have up to 1,000 concurrent sandboxes.
- Suspended sandboxes do not count toward this limit.
- You can reduce the concurrency limit for an individual group.
- To resume a suspended sandbox, its group must have available capacity.
- While a group is at its concurrency limit, requests to create or resume a sandbox fail with HTTP code
429.- To reclaim capacity, terminate 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 |
|---|---|
|
100 | |
|
1,000 | |
|
Execute a command |
1,000 |
|
Upload or download a file or directory |
1,000 |
|
Read sandbox and sandbox group resources |
400 |
|
Write sandbox group resources |
100 |
|
Capture a snapshot |
10 |