Limits and Pricing for Render Sandboxes
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.
| Plan | Specs | Price |
|---|---|---|
|
| 1 CPU 2 GB RAM | $0.12 / CPU-hour + $0.038 / hour |
|
| 2 CPU 4 GB RAM | $0.12 / CPU-hour + $0.076 / hour |
|
| 4 CPU 8 GB RAM | $0.12 / CPU-hour + $0.152 / hour |
|
| 8 CPU 16 GB RAM | $0.12 / CPU-hour + $0.304 / hour |
How billing works
Sandboxes are billed differently for CPU and memory usage:
| Resource | Billing |
|---|---|
|
CPU |
Billed at $0.12 per CPU-hour, based on the total amount of CPU your sandbox actually uses:
|
|
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.
General limits
| Property | Limit |
|---|---|
|
Writable filesystem storage per sandbox |
40 GB |
|
Maximum runtime timeout |
Learn more about sandbox timeouts. |
|
Maximum idle timeout |
Learn more about sandbox 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. |
|
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.
-
Suspended 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 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 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 |