Skip to main content
Vercel Sandbox provides on-demand, isolated Firecracker compute for running untrusted code, tests and builds, tied to a Vercel team and project. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to vercel and these variables:
  • VERCEL_TOKEN
  • VERCEL_TEAM_ID
  • VERCEL_PROJECT_ID
For CI runners, CostGraph sets vCPUs; Vercel gives 2 GB of memory per vCPU. providerTemplate takes a snapshot id. To see what Vercel costs, connect the Vercel integration.

​
Key and permissions

VERCEL_TOKEN is a Vercel access token created at vercel.com/account/tokens (name, Scope, expiration; shown once). VERCEL_TEAM_ID is the team ID from team settings; VERCEL_PROJECT_ID is the project ID from project General settings. Access tokens are the documented method for external CI (OIDC otherwise). Token scope levels: Full Account, Team (all projects of one team) or Project. The Sandbox auth page requires “a Vercel access token with access to the team”, so a team-scoped token (Scope > team > All Projects) is the documented minimum; whether a project-scoped token works for Sandbox is not documented. No finer permissions exist on access tokens. Sources: vercel.com: authentication, vercel.com: access tokens, vercel.com: pricing.

​
Limits

  • Max session duration: Hobby 45 min, Pro/Enterprise 24 h; default timeout 5 min, extendable via extendTimeout(); limit is per session, resets on stop/resume. (source)
  • Max per sandbox: Hobby 4 vCPU/8 GB, Pro 8 vCPU/16 GB, Enterprise 32 vCPU/64 GB; 64 GB disk; 2 GB RAM per vCPU. (source)
  • Concurrent sandboxes: Hobby 10, Pro/Enterprise 10,000; Hobby creation pauses once monthly quota is used. (source)
  • Available in 19 regions, default iad1. Architecture not documented. (source)