Vercel Sandbox pricing and limits
- Each sandbox can use a maximum of 8 vCPUs with 2 GB of memory allocated per vCPU
- Sandboxes have a maximum runtime duration of 5 hours for Pro/Enterprise and 45 minutes for Hobby, with a default of 5 minutes. You can configure this using the
timeoutoption ofSandbox.create(). - You can run Node.js or Python runtimes. Review the system specifications.
- Sandboxes can have up to 4 open ports.
Vercel tracks sandbox usage by:
- Active CPU: The amount of CPU time your code consumes, measured in milliseconds. Waiting for I/O (e.g. calling AI models, database queries) does not count towards Active CPU.
- Provisioned memory: The memory size of your sandbox instances (in GB), multiplied by the time they are running (measured in hours).
- Network bandwidth: The incoming and outgoing network traffic in and out of your sandbox for tasks such as installing packages and sandbox usage by external traffic through the sandbox listening port.
- Sandbox creations: The number of times you started a sandbox.
| Metric | Monthly amount included for Hobby |
|---|---|
| CPU (hour) | 5 |
| Provisioned Memory (GB-hr) | 420 |
| Network (GB) | 20 |
| Sandbox creations | 5000 |
You can use sandboxes under Pro and Enterprise plans based on the following regional pricing:
| Active CPU time (per hour) | Provisioned Memory (per GB-hr) | Network (per GB) | Sandbox creations (per 1M) |
|---|---|---|---|
| $0.128 | $0.0106 | $0.15 | $0.60 |
Currently, Vercel Sandbox is only available in the iad1 region.
Sandboxes can run for up to several hours based on your plan. The default is 5 minutes.
| Plan | Duration limit |
|---|---|
| Hobby | 45 minutes |
| Pro | 5 hours |
| Enterprise | 5 hours |
You can configure the maximum runtime duration using the timeout option of Sandbox.create() and extend it later using sandbox.extendTimeout():
const sandbox = await Sandbox.create({
// 3 hours timeout
timeout: 3 * 60 * 60 * 1000,
});
// Extend by 2 hours
await sandbox.extendTimeout(2 * 60 * 60 * 1000);You can extend the timeout as many times as you need, until the maximum timeout has been reached.
At any time, based on your plan, you can run up to a maximum number of sandboxes at the same time. You can upgrade if you're on Hobby. For Pro and Enterprise, this limit will only apply during the Beta period.
| Plan | Concurrent sandboxes limit |
|---|---|
| Hobby | 10 |
| Pro | 2000 |
| Enterprise | 2000 |
Please get in touch with our sales team if you need more concurrent sandboxes.
The number of vCPUs you can allocate to active sandboxes depends on your plan. If you need more, you can upgrade.
For example, with the Pro plan's 200 vCPUs per minute limit, you can create:
- 25 large sandboxes (8 vCPUs each) every minute
- Or 100 small sandboxes (2 vCPUs each) every minute
| Plan | Sandboxes vCPUs allocation limit |
|---|---|
| Hobby | 40 vCPUs/10 minute |
| Pro | 200 vCPUs/minute |
| Enterprise | 400 vCPUs/minute |
Please get in touch with our sales team if you need a higher rate of sandboxes vCPUs allocations.
Was this helpful?