Firecracker microVMs for running untrusted code from inside a Vercel deployment.
Logo assets
Vercel brand colours
Extracted from the artwork and ranked by how much of the mark each covers — not from a brand book, so treat them as observed rather than official.
What Vercel is
Vercel Sandbox runs Firecracker microVMs on the same infrastructure as Vercel Functions, exposed through an SDK meant to be called from a Vercel app. The product has moved a long way from its ephemeral launch: sandboxes are now persistent by default, snapshotting their filesystem on stop and resuming from it, with an explicit fork call, custom images from Vercel's container registry, and a per-sandbox egress firewall that takes a domain allowlist. Billing follows Vercel's active-CPU model, which is unusually kind to agent workloads that spend most of their life waiting. The catch is placement: it runs in a single US region.
Recent changes
- 2025-06-25Vercel Sandbox launches at Ship 2025
Vercel shipped ephemeral microVM sandboxes callable from a Vercel app, initially capped at 45 minutes each and billed on the active-CPU model. The duration cap has since risen to 24 hours on paid plans, and the product has picked up persistence, snapshots, fork and an egress firewall.