Pricing and Limits
Vercel Sandbox pricing and limits
- Each sandbox can use a maximum of 8 vCPUs with 2 GB of memory allocated per vCPU
- You cannot use the
sudo
command. Your code is executed as thevercel-sandbox
user - Sandboxes have a maximum runtime duration of 45 minutes, with a default of 5 minutes. You can configure this using the
timeout
option ofSandbox.create()
. - You can run Node.js or Python runtimes. Review the system specifications.
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 | Monthly amount included for Pro |
---|---|---|
CPU (hour) | 5 | 5 |
Provisioned Memory (GB-hr) | 420 | 420 |
Network (GB) | 20 | 20 |
Sandbox creations | 5000 | 100000 |
If you exceed the above allotment, you can continue using 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, only
iad1
is available for sandboxes.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 | 150 |
Enterprise | 150 |
Last updated on July 4, 2025
Was this helpful?