Vercel Sandbox
https://vercel.com/docs/vercel-sandbox
Vercel Sandbox is an on-demand, isolated Linux microVM (based on Firecracker) that safely runs arbitrary or untrusted code via an SDK or CLI. It is used by AI coding agents, AI code interpreters, and developer tools that need ephemeral, sandboxed execution environments for tasks such as running AI-generated scripts, executing user-submitted code, or previewing apps. Sandboxes support persistence, snapshots, and port exposure for live URLs.
| Pricing model | Per-second metering: $0.128/vCPU-hour (active CPU), $0.0212/GB-hour memory (full session), $0.60 per million creations |
|---|---|
| Pricing The headline compute price as the provider states it. Sorting ranks prices stated per vCPU over time, converted to hourly. Other pricing models sort after, unranked. | $0.128 per vCPU-hour (active CPU) |
| Free while idle Whether a stopped, paused, or sleeping sandbox costs nothing. | ✓ |
| Elastic Resources flex with what the sandbox actually uses, and the bill follows: yes when the provider bills on active or observed use, no when capacity is reserved or allocated and billed while it runs. | ✓ |
| Memory snapshots Whether RAM state survives a pause and resume, not just disk. | ✕ |
| Wake on request Whether a stopped sandbox wakes automatically on inbound traffic. | ✕ |
| Start / resume Typical time from create or resume to running. Sorting ranks stated times, converted to seconds; claims with no figure sort after, unranked. | Sub-second (millisecond-level startup with Firecracker microVMs) |
| Max runtime The longest a sandbox may run. | 24 h (Pro/Enterprise); 45 min (Hobby) |
| Isolation The isolation technology between sandboxes. | Firecracker microVM |
| GPUs Whether GPU instances are available for sandboxes. | ✕ |
| Docker Whether Docker containers can run inside the sandbox. | ✓ |
| SDKs | JavaScript, TypeScript, Python |
✓ yes · ✕ no · – no cited public fact.
Memory and in-memory process state do NOT persist across stop/resume cycles - only filesystem state is preserved. Memory is billed for the full session duration even during idle I/O waits.
Sources
- https://vercel.com/changelog/run-docker-containers-inside-vercel-sandbox
- https://vercel.com/docs/sandbox/sdk-reference
- https://vercel.com/docs/sandbox/python-sdk-reference
- https://github.com/vercel/sandbox
- https://vercel.com/changelog/sandbox-persistence-is-now-ga
- https://vercel.com/blog/vercel-sandbox-is-now-generally-available
- https://vercel.com/changelog/run-claude-managed-agents-with-vercel-sandbox
- https://vercel.com/changelog/vercel-sandbox-persistent-sandboxes-beta
- https://vercel.com/docs/sandbox/concepts/persistent-sandboxes
- https://vercel.com/docs/sandbox
- https://vercel.com/sandbox
- https://vercel.com/changelog/vercel-sandbox-can-now-run-for-up-to-24-hours
- https://vercel.com/kb/guide/how-to-run-a-multi-step-research-agent-on-vercel
- https://www.truefoundry.com/de/blog/claude-managed-agents-vs-vercel-eve
Last verified 2026-07-29. Corrections land through the update log.