AI Potluck
Contribute
Back to Gap Map Infrastructure / Deployment

Vercel Sandbox

Vercel
closed / Overall score: 4.6(leading)

Vercel Sandbox runs untrusted or agent-generated code in a Firecracker microVM with its own filesystem and network, started from a Vercel-managed Linux image or a custom OCI image in the Vercel Container Registry. Sandboxes persist by default, resuming where they stopped, and can be snapshotted, given root and system privileges, or split per agent by Linux user. JavaScript and Python SDKs and a CLI drive it, and each sandbox runs in a Vercel region the caller chooses.

Openness

1 high confidence
1.0
source
closed
service
proprietary Vercel Fluid-compute managed cloud (no self-host of the Firecracker microVM plane)
open-part
client SDK/CLI only (@vercel/sandbox JS + Python, vercel/sandbox on GitHub)
license
Proprietary, proprietary service

Vercel Sandbox is a closed managed service: the SDK and CLI are open, but they are only a client for Vercel's proprietary microVM cloud, which cannot be self-hosted, so an open client over a closed runtime does not amount to open core. It sits with the other proprietary sandbox clouds — Google Cloud Run, Fly Sprites and Northflank.

  • https://vercel.com/docs/sandbox recorded 2026-09-29

    The Vercel docs overview says "Each sandbox runs in a secure Firecracker microVM with its own filesystem and network" on Vercel, and the only code it points to is the GitHub repo: "View the Sandbox repository on GitHub contained the SDK and CLI codebase." The microVM runtime itself is not distributed, and no self-host or on-prem option appears on the page.

  • https://vercel.com/docs/sandbox/pricing recorded 2026-09-29

    The pricing page meters usage by Active CPU and Provisioned Memory across Hobby, Pro and Enterprise plans, and says "Sandbox is available in 19 regions" of the Vercel cloud. Searched the body for self-host, on-prem, source-available and license: none.

Adoption

5 medium confidence
5.0

Adoption is measured by npm downloads of @vercel/sandbox, confirmed by registry metadata as the product's own SDK, over the trailing month ending 2026-08-09. Package downloads include the usual CI and mirror inflation that overstates distinct human users, so confidence stays moderate even though Vercel's large install base and the SDK's general-availability status support genuine production use.

Capability

4 high confidence
4.0

Vercel Sandbox isolates each run in a Firecracker microVM with persistent, snapshot-capable state. Vercel says sandboxes start in milliseconds, while independent benchmarks put the cold start in the hundreds of milliseconds, still under a second. Its support for custom OCI images and root access is broad, but AWS Lambda's native language runtimes, Runtime API and longer production record keep Vercel Sandbox a step below Lambda.

  • https://vercel.com/docs/sandbox recorded 2026-09-29

    The docs overview says "Sandboxes run Linux images, with Ubuntu, Arch Linux, or any other Linux distribution you need", that "Sandboxes start in milliseconds", and that system-privileged workloads run "such as container runtimes like Docker, VPN clients, and FUSE filesystem drivers".

  • https://vercel.com/docs/sandbox recorded 2026-09-29

    The docs overview describes persistence as "Sandboxes that auto-save state on stop and resume where you left off" and says "Persistence is the default. No manual snapshot management needed." and lists Snapshots and Drives pages.

  • https://vercel.com/docs/sandbox/pricing recorded 2026-09-29

    The limits tables list Maximum vCPUs, Concurrent sandboxes and Max Session Duration by plan, and the page says "Sandbox is available in 19 regions" with regional pricing for each.

  • https://www.computesdk.com/benchmarks/sandboxes/ recorded 2026-07-09

    ComputeSDK TTI leaderboard (independent, 100 iters/day, 2026-07-09 run): median time-to-interactive ~390ms sequential / ~490ms burst @100 concurrent; 9th of 19 providers

Verified 2026-09-29