Rank #5 of 8 in Agent Sandboxes & Code Execution
Install
npm i @vercel/sandbox
vs E2B
vs Daytona
vs Modal Sandboxes
vs Cloudflare Sandboxes
vs Runloop
vs Blaxel
vs MaritimeShowcase
Products
Vercel, product by product →Vercel ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Vercel | Edge & App Platforms | #4/6 | 25/100 | 44/100 |
| v0 | Vibe-Coding App Builders | #4/6 | 21/100 | 24/100 |
| Vercel Sandboxthis page | Agent Sandboxes & Code Execution | #5/8 | 25/100 | 41/100 |
| Vercel AI Gateway | Model Gateways & Routers | #3/7 | 29/100 | 41/100 |
| skills.sh | Agent Skills & Extensions | #5/5 | 18/100 | 29/100 |
Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Capabilities hardware — stories about capabilities hardware in this arenaCapabilities hardwareevidence →
Stories about capabilities hardware in this arena
Code execution — stories about code execution in this arenaCode executionevidence →
Stories about code execution in this arena
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experienceevidence →
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Isolation security — stories about isolation security in this arenaIsolation securityevidence →
Stories about isolation security in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Performance scale — stories about performance scale in this arenaPerformance scaleevidence →
Stories about performance scale in this arena
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycleevidence →
Creating, updating, and tearing down resources across their lifecycle
Snapshot persistence — stories about snapshot persistence in this arenaSnapshot persistenceevidence →
Stories about snapshot persistence in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Vercel Sandbox stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓9/10
unlocks → Webhooks · Scoped API keys · MCP server · Versioning policy · Full data export
Subscribe to events via webhooks
—–
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
—–
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
unlocks → Interactive API docs · MCP server
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
✓8/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
—–
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Capabilities hardware — stories about capabilities hardware in this arenaCapabilities hardware
Stories about capabilities hardware in this arena
Code execution — stories about code execution in this arenaCode execution
Stories about code execution in this arena
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Isolation security — stories about isolation security in this arenaIsolation security
Stories about isolation security in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Performance scale — stories about performance scale in this arenaPerformance scale
Stories about performance scale in this arena
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle
Creating, updating, and tearing down resources across their lifecycle
Snapshot persistence — stories about snapshot persistence in this arenaSnapshot persistence
Stories about snapshot persistence in this arena
Sorted by importance (agentic first) (high → low) · 51/51 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 8/10 | Cclaimed | |
Execute untrusted, AI-generated code without risking my own infrastructure C Untrusted code | developer | Code execution — stories about code execution in this arenaCode execution | 3 | full | 9/10 | Cclaimed | |
My agent can provision its own sandbox, execute code, read the results, and tear it down — end to end without a human C Agent lifecycle | ai-native user | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 3 | full | 8/10 | Cclaimed | |
Spin up an isolated sandbox with one API/SDK call and get a live environment in seconds C Lifecycle | developer | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 3 | full | 8/10 | Cclaimed | |
Rely on a documented hard isolation boundary (microVM or equivalent) between sandboxes and my systems C Isolation | platform-engineer | Isolation security — stories about isolation security in this arenaIsolation security | 3 | partial | 6/10 | Cclaimed | |
Snapshot a sandbox and later restore or fork new sandboxes from that snapshot C Snapshots | developer | Snapshot persistence — stories about snapshot persistence in this arenaSnapshot persistence | 3 | partial | 6/10 | Cclaimed | |
Pay per second only for the compute a sandbox actually uses G Pricing | platform-engineer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | partial | 4/10 | Cclaimed | |
Run large concurrent fleets of sandboxes with documented concurrency limits C Scale | platform-engineer | Performance scale — stories about performance scale in this arenaPerformance scale | 3 | partial | 3/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Start sandboxes with documented sub-second-to-few-second cold starts C Latency | developer | Performance scale — stories about performance scale in this arenaPerformance scale | 3 | none | 0/10 | ||
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Restrict or allow the sandbox's network egress with explicit policy C Network policy | platform-engineer | Isolation security — stories about isolation security in this arenaIsolation security | 3 | none | untested | none yet | |
Define custom sandbox templates or bring my own container image C Runtimes | developer | Code execution — stories about code execution in this arenaCode execution | 2 | full | 9/10 | Cclaimed | |
Give an agent a sandbox where host secrets and credentials are unreachable by the code it runs C Isolation | ai-native user | Isolation security — stories about isolation security in this arenaIsolation security | 2 | full | 8/10 | Cclaimed | |
Pause a running sandbox and resume it later with filesystem and memory state intact C Snapshots | developer | Snapshot persistence — stories about snapshot persistence in this arenaSnapshot persistence | 2 | full | 8/10 | Cclaimed | |
Run arbitrary shell commands and install packages inside the sandbox C Untrusted code | developer | Code execution — stories about code execution in this arenaCode execution | 2 | full | 8/10 | Cclaimed | |
Set timeouts so sandboxes shut down automatically and stop billing when idle or done G Lifecycle | developer | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 2 | full | 8/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | full | 7/10 | Tprobed | |
Execute code in multiple language runtimes (Python, JavaScript, and more) and get rich results back C Runtimes | developer | Code execution — stories about code execution in this arenaCode execution | 2 | full | 7/10 | Cclaimed | |
Keep a sandbox session running for hours or days for long agent tasks C Scale | developer | Performance scale — stories about performance scale in this arenaPerformance scale | 2 | partial | 6/10 | Cclaimed | |
Read, write, upload, and download files in the sandbox filesystem via the SDK C Files | developer | Code execution — stories about code execution in this arenaCode execution | 2 | partial | 6/10 | Cclaimed | |
Run coding agents like Claude Code or Codex inside the sandbox following the vendor's own recipe C Agent workloads | ai-native user | Capabilities hardware — stories about capabilities hardware in this arenaCapabilities hardware | 2 | partial | 6/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Cclaimed | |
Expose a port from the sandbox on a public preview URL to reach services running inside C Preview access | developer | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 2 | partial | 5/10 | Cclaimed | |
Attach GPUs to sandboxed workloads C Workloads | developer | Capabilities hardware — stories about capabilities hardware in this arenaCapabilities hardware | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Run a headless browser or full desktop environment inside the sandbox C Workloads | developer | Capabilities hardware — stories about capabilities hardware in this arenaCapabilities hardware | 2 | none | untested | none yet | |
Start building with a free tier or included credits without talking to sales G Pricing | developer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 31 stories with headroom
What would move Vercel Sandbox’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Vercel Sandbox is an execution/infrastructure product (not itself an agent), so an official MCP server exposing it to agents is a fair, applicable axis; however no evidence in the pack mentions MCP, an MCP server, or any agent-protocol integration—only SDKs, CLI, and REST/OpenAPI docs are described.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Performance scale — stories about performance scale in this arenaStart sandboxes with documented sub-second-to-few-second cold starts
nonemoves PA Scoreimpact 30
Missing: documented benchmark numbers or explicit cold-start time claims, any independent performance measurement.
Isolation security — stories about isolation security in this arenaRestrict or allow the sandbox's network egress with explicit policy
nonemoves PA Scoreimpact 30
No evidence in the pack mentions network egress controls, firewall rules, or outbound traffic policy for Vercel Sandbox—coverage focuses on isolation via microVMs, filesystem, images, and multi-agent user separation but never explicit egress allow/deny configuration.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: any documented export/download-all-data capability, explicit open-format guarantees for drives/snapshots, or migration tooling to leave the platform.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Vercel Sandbox is a fully managed, hosted service running on Vercel's own microVM infrastructure (iad1/sfo1/cle1/cdg1 regions); there is no evidence of any self-hostable core, open-source runtime, or on-prem deployment option — it is inherently tied to Vercel's cloud.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
Missing: any NL command parser, chat-driven CLI, or natural-language API for controlling Sandbox operations.
Showing the top 8 of 31 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map4 surfaces · 27 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs27 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Download a machine-readable API spec (OpenAPI or equivalent)
- Test against a sandbox environment without touching production data
- Run coding agents like Claude Code or Codex inside the sandbox following the vendor's own recipe
- Read, write, upload, and download files in the sandbox filesystem via the SDK
- Define custom sandbox templates or bring my own container image
- Execute code in multiple language runtimes (Python, JavaScript, and more) and get rich results back
- Execute untrusted, AI-generated code without risking my own infrastructure
- Run arbitrary shell commands and install packages inside the sandbox
- My agent can provision its own sandbox, execute code, read the results, and tear it down — end to end without a human
- Rely on a documented hard isolation boundary (microVM or equivalent) between sandboxes and my systems
- Give an agent a sandbox where host secrets and credentials are unreachable by the code it runs
- Do everything through the API that I can do in the UI
- Run large concurrent fleets of sandboxes with documented concurrency limits
- Keep a sandbox session running for hours or days for long agent tasks
- Pay per second only for the compute a sandbox actually uses
- Choose where my data is stored (region/residency)
- Set timeouts so sandboxes shut down automatically and stop billing when idle or done
- Spin up an isolated sandbox with one API/SDK call and get a live environment in seconds
- Expose a port from the sandbox on a public preview URL to reach services running inside
- Pause a running sandbox and resume it later with filesystem and memory state intact
- Snapshot a sandbox and later restore or fork new sandboxes from that snapshot
OpenAPI spec4 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
1 of 15 testable claims verified · 0 contradicted → integrity 7/100
32 distinct capability claims found in Vercel Sandbox’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
1
Verified
14
Unverified
0
Contradicted
12
Undersold
Verified (1)
“Supports access tokens for authenticating from external CI/CD or non-Vercel environments”
Run the product headlessly / in CI for automationfullproof ↗
Unverified (25)
“Runs untrusted or AI agent-generated code inside isolated Linux microVMs”
Execute untrusted, AI-generated code without risking my own infrastructurefullproof ↗
“Runs untrusted or AI agent-generated code inside isolated Linux microVMs”
Rely on a documented hard isolation boundary (microVM or equivalent) between sandboxes and my systemspartialproof ↗
“Executes untrusted code (AI output, user uploads, third-party scripts) without exposing production systems”
Execute untrusted, AI-generated code without risking my own infrastructurefullproof ↗
“Executes untrusted code (AI output, user uploads, third-party scripts) without exposing production systems”
Give an agent a sandbox where host secrets and credentials are unreachable by the code it runsfullproof ↗
“Can run development servers with live previews”
Expose a port from the sandbox on a public preview URL to reach services running insidepartialproof ↗
“Offers an official @vercel/sandbox SDK for JavaScript and TypeScript”
“Supports arbitrary Linux distributions (Ubuntu, Arch, etc.) as sandbox images, with a default image bundling Node.js LTS, Python, and coding agents”
Define custom sandbox templates or bring my own container imagefullproof ↗
“Supports arbitrary Linux distributions (Ubuntu, Arch, etc.) as sandbox images, with a default image bundling Node.js LTS, Python, and coding agents”
Execute code in multiple language runtimes (Python, JavaScript, and more) and get rich results backfullproof ↗
“Sandboxes persist state automatically on stop and resume where left off, with no manual snapshot management required”
Pause a running sandbox and resume it later with filesystem and memory state intactfullproof ↗
“Supports snapshotting a running sandbox's state to resume later and skip reinstalling dependencies”
Snapshot a sandbox and later restore or fork new sandboxes from that snapshotpartialproof ↗
“Can mount external object stores like Amazon S3 via a FUSE driver, exposed as sandbox filesystem paths”
Read, write, upload, and download files in the sandbox filesystem via the SDKpartialproof ↗
“Lets you build custom system packages/tooling into a shared image reused across projects and teams”
Define custom sandbox templates or bring my own container imagefullproof ↗
“Supports creating sandboxes from custom Docker images stored in Vercel Container Registry”
Define custom sandbox templates or bring my own container imagefullproof ↗
“Can retrieve an existing sandbox by name, resuming it if stopped”
Pause a running sandbox and resume it later with filesystem and memory state intactfullproof ↗
“Commands can be run in blocking (wait for completion) or detached (return immediately) mode”
Run arbitrary shell commands and install packages inside the sandboxfullproof ↗
“Sandbox timeout is configurable at creation and can be extended at runtime via extendTimeout()”
Set timeouts so sandboxes shut down automatically and stop billing when idle or donefullproof ↗
“Sandboxes can run in multiple regions (iad1, sfo1, cle1, cdg1), selectable per sandbox or as a project default”
Choose where my data is stored (region/residency)partialproof ↗
“Provides visibility into agent/user-submitted code behavior including logs, file edits, and live previews during test runs”
Expose a port from the sandbox on a public preview URL to reach services running insidepartialproof ↗
“Offers an official sandbox CLI for manual testing, agentic workflows, debugging, and one-off operations”
“CLI supports creating a sandbox with an explicit name”
“Sandboxes can be started from Vercel Managed Images, shared/public images, or custom OCI images in Vercel Container Registry”
Define custom sandbox templates or bring my own container imagefullproof ↗
“Restoring from a snapshot is faster than a fresh sandbox because it skips reinstalling dependencies and setup steps”
Snapshot a sandbox and later restore or fork new sandboxes from that snapshotpartialproof ↗
“Sandbox SDKs provide a programmatic interface to create sandboxes, run commands, and manage files”
“Sandbox SDKs provide a programmatic interface to create sandboxes, run commands, and manage files”
Read, write, upload, and download files in the sandbox filesystem via the SDKpartialproof ↗
“Default sandbox timeout is 5 minutes, configurable and extendable”
Set timeouts so sandboxes shut down automatically and stop billing when idle or donefullproof ↗
Undersold (12)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Test against a sandbox environment without touching production datafullproof ↗
Run coding agents like Claude Code or Codex inside the sandbox following the vendor's own recipepartialproof ↗
My agent can provision its own sandbox, execute code, read the results, and tear it down — end to end without a humanfullproof ↗
Do everything through the API that I can do in the UIfullproof ↗
Run large concurrent fleets of sandboxes with documented concurrency limitspartialproof ↗
Keep a sandbox session running for hours or days for long agent taskspartialproof ↗
Pay per second only for the compute a sandbox actually usespartialproof ↗
Spin up an isolated sandbox with one API/SDK call and get a live environment in secondsfullproof ↗
Claims outside our story set (10)
Real capability claims found in Vercel Sandbox’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Can be used to build interactive tools like code playgrounds and AI-powered UI builders”
source ↗“Authentication to the sandbox API is automatic when running on Vercel in production”
source ↗“Can run system-privileged workloads such as container runtimes, VPN clients, and FUSE drivers”
source ↗“Supports multi-agent isolation by giving each agent its own Linux user/home directory and shared groups for file sharing”
source ↗“Sandboxes can be tagged with key-value pairs for categorization (environment, team, etc.)”
source ↗“Beta 'Drives' feature attaches persistent filesystem storage reusable across sandbox runs”
source ↗“Supports streaming logs from a detached command in real time”
source ↗“Sandboxes can be manually stopped from the Vercel Dashboard”
source ↗“Spend Management lets you set alerts or pause projects to control sandbox costs”
source ↗“Local development authentication uses `vercel link` and `vercel env pull` to obtain a dev token”
source ↗
Business model
Billed per active CPU time, provisioned memory, and sandbox creations, metered per-second on top of Vercel's Hobby/Pro plans with included monthly allotments.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% · openapi.json 100% (30d, checked every 6h since Sep 8 '26)