Vercel Sandbox vs Blaxel

Both run each sandbox in a Firecracker microVM with its own kernel. Vercel Sandbox is built for runs of code in 19 regions; each session stops after 24 hours and resumes from a snapshot. Blaxel sandboxes go to standby seconds after the last connection and wake in under 25 ms with their memory intact.

The companies and products

Vercel Sandbox

Vercel is a cloud platform for web apps and agents, and Vercel Sandbox is its product for running untrusted or agent-written code in isolated Linux microVMs.

Each sandbox is a Firecracker microVM with its own kernel, started from a Vercel image, your own OCI image, or a saved snapshot. You drive it with the JavaScript or Python SDK or the sandbox CLI: run commands, move files, open ports, fork sandboxes, mount Drives and set network rules. Sandboxes are persistent by default: each stop saves the filesystem, and the next session resumes from it. Vercel aims it at code interpreters, app builders, test runs, developer environments and agent workspaces. Its docs suggest a VM for 24/7 hosting.

Blaxel

Blaxel is a San Francisco company that runs cloud infrastructure for AI agents. Since September 2026 it is part of Baseten.

You get sandboxes, batch jobs, MCP server hosting and a model gateway. Each sandbox is a Firecracker microVM with its own kernel. It goes to standby when nothing is connected and resumes in under 25 ms with its memory and running processes. It is built for agent products that start many sandboxes and keep them asleep most of the time.

Which use cases each one fits

For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “27th cheapest of 336” means 26 of the other 335 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.

Use case and its workloadVercel Sandbox: price rankBlaxel: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Blaxel fits at $2,373 a month with a desktop image and a Docker image. Vercel Sandbox is listed with limits ($3,351): no built-in desktop and no /dev/kvm. boat fits at $634 and adds /dev/kvm for emulators.
259th of 365, with limits
$3,351 a month
15th cheapest of 365
$2,373 a month
5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
Blaxel fits mostly idle assistants that sleep and wake on request: $2,832 a month here. Vercel is listed with limits ($3,657) because each session stops at 24 hours. boat fits at $657 with auto-stop off.
75th of 361, with limits
$3,657 a month
17th cheapest of 361
$2,832 a month
6th cheapest of 361
$657 a month
Code interpreter bursts
100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month
Both fit short code bursts: Blaxel at $144 a month and Vercel Sandbox at $216. boat's start limits make it a compromise here.
27th cheapest of 336
$216 a month
18th cheapest of 336
$144 a month
189th of 336, with limits
$2,000 a month
Sandboxes for your users
300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month
Vercel Sandbox fits 300 users at once at $1,267 a month. Blaxel ($926) is listed with limits: its self-serve tiers stop at 200 at once. boat fits at $209.
25th cheapest of 349
$1,267 a month
105th of 349, with limits
$926 a month
3rd cheapest of 349
$209 a month
RL rollouts
1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month
Vercel Sandbox is a full match at $15,761 a month, with high concurrency on Pro. Blaxel ($4,378) is listed with limits because of its 200 cap on self-serve tiers.
7th cheapest of 349
$15,761 a month
82nd of 349, with limits
$4,378 a month
39th of 349, with limits
$2,000 a month
Agent evals
250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month
81st cheapest of 359
$1,508 a month
140th of 359, with limits
$704 a month
10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
112th cheapest of 374
$1,144 a month
55th cheapest of 374
$431 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
Blaxel fits a dev box at $114 a month, with SSH through its Tailscale tutorial. Vercel is listed with limits ($145): sessions stop every 24 hours. boat is $26 with SSH built in and auto-stop off.
283rd of 371, with limits
$145 a month
125th cheapest of 371
$114 a month
19th cheapest of 371
$26 a month
Computer-use agents
50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month
Blaxel fits at $634 a month with a desktop image and VNC. On Vercel Sandbox you set up a browser yourself, so it is listed with limits ($952). boat fits at $200 with a 60 fps desktop you can embed.
263rd of 367, with limits
$952 a month
17th cheapest of 367
$634 a month
7th cheapest of 367
$200 a month
Browser-use agents
50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month
Blaxel fits at $317 a month and boat at $200. On Vercel you install Chromium and agent-browser yourself, so it is listed with limits ($486).
100th of 356, with limits
$486 a month
16th cheapest of 356
$317 a month
7th cheapest of 356
$200 a month
Scraping & bots (startup scale)
50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month
109th cheapest of 343
$468 a month
19th cheapest of 343
$215 a month
6th cheapest of 343
$90 a month
Mass scraping & bots (undetectable)
1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month
234th of 327, with limits
$9,960 a month
143rd of 327, with limits
$4,292 a month
73rd of 327, with limits
$1,800 a month
Parallel red teaming
200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month
31st cheapest of 351
$554 a month
5th cheapest of 351
$217 a month
3rd cheapest of 351
$200 a month
GPU eval jobs
10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month
Not ranked: misses a requirementNot ranked: misses a requirementNot ranked: misses a requirement
macOS agents
5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month
Not ranked: misses a requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureVercel SandboxBlaxelboat
IsolationFirecracker microVM with its own kernelFirecracker microVM with its own kernelFull VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Longest session24 hours on Pro and Enterprise, 45 minutes on Hobby; a persistent sandbox resumes from its snapshot in a new sessionNo session cap; Tier 0 and Tier 1 delete sandboxes after up to 7 or 30 days, Tier 2 and up keep themNo session cap once you turn auto-stop off on a paid plan; auto-stop defaults to 1 hour
Sleep and wakeMemory billed while the session runs; a stop saves the filesystem, and the next session boots from itStandby about 5 to 15 seconds after the last connection; wakes in under 25 ms with memory and processesA running sandbox bills at full rate, busy or idle; stop and resume by API, and a resume is like a reboot
Saving filesFilesystem snapshot at every stop, $0.08/GB-month, kept 30 days after last use by default; Drives for storage that outlives sandboxesWritable files live in RAM (about half of it) and are kept in standby snapshots; one block volume at creation, or Agent Drive (private preview)A disk on every size (51 GB at 4 vCPU / 8 GB), saved every minute and at each stop; kept at least 14 days after a stop
Desktop, browser, computer useNo built-in desktop or computer-use API; you install Chromium and agent-browser yourself (Vercel guide) or connect an external browserA desktop image with VNC, and browser imagesBuilt in: 1920x1080, 60 fps desktop and Chrome, computer tools and a browser-control API, embeddable stream
Nested virtualizationNo; Firecracker does not expose /dev/kvm to guestsNot documented by Blaxel; upstream Firecracker does not give guests /dev/kvmYes, /dev/kvm (Android emulator, VMs)
SSH and systemdCommands through the SDK or CLI; no SSH serverRoot and a terminal through bl connect; you set up SSH with Tailscale (documented tutorial)SSH, root and systemd
Docker insideYes, with sudoYes, with a Docker-in-sandbox imageYes, with root and systemd
ForkSandbox.fork() starts children from a sandbox's latest filesystem snapshotFork with memory and running processes (private preview)Fork a running sandbox from its last 1-minute disk snapshot; the fork boots fresh
Custom imagesYour own OCI images from a Dockerfile, via Vercel Container RegistryCustom images built from Docker imagesStart from boat's image or a saved snapshot; you cannot boot your own Docker or OCI image
Coding agentsClaude Code, Codex, OpenCode and pi preinstalled; you start them as commandsClaude Code and Codex images you drive from their terminal or your own harnessClaude Code, Codex, pi, OpenCode, Prime Agent, Kimi Code and Mistral Vibe, with an API to prompt, steer and stream events
Inbound accessPublic URLs for up to 15 ports, no built-in auth; no raw TCP or public IPPreview URL per port, public or token-protected; no public inbound IPUp to 50 HTTPS URLs, token-gated by default; SSH; raw ports over IPv6 (some sandboxes have no IPv4 of their own); no static IP
Egress rulesAllow-all, deny-all or a domain and CIDR allowlist, changeable while running; static IPs on EnterpriseDomain allow and deny lists with method and path rules (public preview); dedicated egress IPs (free during beta)No provider-side allowlist; filter inside the VM with nftables
Keys kept outside the sandboxCredentials brokering injects headers for any HTTPS domain you allowProxy fills secrets into outbound HTTPS requests to any host (public preview)Optional AI credentials proxy ($1 per day on, plus $1 per 1,000 requests) for model providers and any HTTPS API you add
Regions19 regions across the US, Europe, Asia, South America, Africa and AustraliaOregon, North Virginia, London, FrankfurtGermany, Finland and France; you cannot pick a region; no US or Asia region
ComplianceSOC 2 Type 2, ISO 27001, PCI DSS; HIPAA on EnterpriseSOC 2 Type II, ISO 27001; HIPAA BAA as a $250/month add-onNo SOC 2 report today; SOC 2 is in progress
Every feature Battleships tracks (43)
FeatureVercel SandboxBlaxelboat
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationNo documented wayNo documented wayYes
RootYesYesYes
SystemdNot publishedNo documented wayYes
Desktop GUINo documented wayYesYes
BrowserWith your own setupYesYes
Computer-use APINo documented wayYesYes
SSHNo documented wayWith your own setupYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesYesYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkNo documented wayYesNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopNo documented wayYesNo documented way
Wake on requestNo documented wayYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistYesYesNo documented way
Secret proxyYesYesYes
Secret proxy for any APIYesYesYes
Preinstalled agentsYesYesYes
Agent harness APINo documented wayNo documented wayYes
MCP serverYesYesNo documented way
GPUNo documented wayNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayNo documented wayNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayYesNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedYesYes
Spend limitsYesNo documented wayYes
Usage per sandbox (API)No documented wayYesYes
Audit logsNot publishedNot publishedNo documented way
SSOYesYesNo documented way
SOC 2YesYesNo documented way
HIPAAYesYesNo documented way
EU data residencyYesYesNo documented way
Zero data retentionNot publishedYesYes

Performance

Vercel Sandbox12.66 runs/s
Blaxel18.03 runs/s
boat28.06 runs/s

All three are in StarSling's run of 3 October 2026 (run 37073680030), on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB. boat did 28.06 runs per second, second of 15. Blaxel did 18.03 and Vercel Sandbox 12.66; both share rank 7, so the run cannot separate them. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. Providers ran on different hardware in different regions. For start time, ComputeSDK measured Blaxel at 364 ms and Vercel at 533 ms median with 100 at once (6 November 2026), each at its default size; boat is not in ComputeSDK.

V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Blaxel measured on: Sandbox (active time, RAM-only pricing, CPU bundled). Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure.

Pricing in five scenarios

Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario. Start limits, per-start fees and plan minimums are in the price, boat's included.

ScenarioVercel Sandbox, a monthBlaxel, a monthboat, a month
One coding agent, workdays
4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days
$57 · Pro$33 · Pay-as-you-go Tier 1$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$236 · Pro · with limits$120 · Pay-as-you-go Tier 1$26 · $20/mo
50 agents in parallel
50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside
$2,884 · Pro$1,489 · Pay-as-you-go Tier 1$317 · $20/mo × 3 seats
Sandboxes for your users
2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once
$828 · Pro$396 · Pay-as-you-go Tier 2 · with limits$200 · $100/mo × 2 seats
1,000 short jobs at once
2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month
$3,152 · Pro$876 · Pay-as-you-go Tier 2 · with limits$8,800 · $2000/mo · with limits

Vercel Sandbox: Vercel charges for CPU only while your code uses it ($0.128 per vCPU-hour in iad1), and for memory for the whole time the sandbox runs ($0.0212 per GB-hour). It adds $0.60 per million sandboxes created, $0.08 per GB-month of snapshots, and $0.05 per GB-month for Drives plus reads and writes. Rates are up to 1.73x higher outside the US. The $20 Pro credit is shared with your other Vercel usage.

Blaxel: Blaxel charges $0.0000115 per GB of allocated RAM per active second, with CPU included: 8 GB comes with 4 cores, about $0.33 an hour. Active means a connection is open. In standby you pay only snapshot storage ($0.20 per GB-month), and volumes cost $0.12 per GB-month on their full size. New accounts get up to $200 of free credits.

Blaxel: boat charges a flat price per size, per second, while the sandbox runs, busy or idle: $0.036 an hour for 4 vCPU / 8 GB. Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A card is required, also for the 7-day trial. A stopped sandbox has no compute charge, but saved snapshots above the plan's count and the optional AI credentials proxy still charge. Starts above the plan's included number cost $0.03 to $0.07 each.

Limits in those scenarios

For one agent that never stops, Vercel ends each session at 24 hours; it resumes from its snapshot, but running processes start again. Blaxel and boat keep going. For sandboxes for your users and 1,000 short jobs at once, Blaxel's self-serve tiers allow 10, 50 or 200 sandboxes at once, standby ones included, so you need a sales tier; Vercel fits both on Pro. boat fits 300 users at once but not the 1,000-job burst: the $2,000 plan includes 90 starts a minute and 2,400 a day, extra starts cost $0.03 to $0.07, and starts above 270 a minute fail with 429. boat also keeps a stopped disk at least 14 days unless you save a snapshot, and a machine failure loses what was written after the last 1-minute snapshot.

ScenarioVercel SandboxBlaxelboat
One coding agent, workdaysNone for this scenarioNone for this scenarioNone for this scenario
One agent that never stops
  • Pro: sessions capped at 24 h
None for this scenarioNone for this scenario
50 agents in parallelNone for this scenarioNone for this scenarioNone for this scenario
Sandboxes for your usersNone for this scenario
  • Pay-as-you-go Tier 2: max 200 concurrent
None for this scenario
1,000 short jobs at onceNone for this scenario
  • Pay-as-you-go Tier 2: max 200 concurrent
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use Vercel Sandbox when

you run many short bursts of code in parallel, already build on Vercel, or need to run close to users far from the US and Europe.

  • Regions all over the world. Useful if your users are spread out: Vercel Sandbox runs in 19 regions, from Virginia to Tokyo and Sydney.
  • Room for big bursts. Pro allows up to 10,000 sandboxes at once, so large parallel runs fit without a sales call.
  • Fits a Vercel stack. If you already deploy on Vercel, sandboxes boot from your Dockerfile image and use your project's login tokens.

Use Blaxel when

your sandboxes sit idle most of the time and must wake in milliseconds with their memory, or need provider-side network rules, US regions, or a HIPAA BAA.

  • Sleeps in seconds, wakes in milliseconds. Useful if sandboxes sit idle most of the time: one sleeps after the last connection and wakes in under 25 ms with its memory.
  • No 24-hour cut. A Blaxel sandbox has no session cap, so a long agent task is not stopped in the middle.
  • A desktop image and provider-side network rules. Computer-use agents get a desktop image with VNC, and a sandbox can be limited to chosen domains, methods and paths.

Where boat fits

If your agents work for hours on one machine, look at boat. It is a full Linux VM with a disk that is saved every minute, a built-in 60 fps desktop, and an API to drive the agents inside. Check its start limits first: each create, fork and resume counts as a start.

A whole Linux machine

Vercel's Firecracker guests get no /dev/kvm, and Blaxel does not document it, so an Android emulator or a VM will not start there. Neither has SSH built in; on Blaxel you add it with Tailscale. boat has /dev/kvm, systemd and SSH.

Long work on a disk

Vercel stops each session at 24 hours; it resumes from its snapshot, and processes start again. Blaxel keeps writable files in RAM, about half of it, unless you attach a volume. boat has a 51 GB disk at the default size and saves it every minute.

More CPU work per second in one public run

In StarSling's run of 3 October 2026, boat did 28.06 runs per second on the V8 Web Tooling Benchmark, Blaxel 18.03 and Vercel Sandbox 12.66, at 4 vCPU / 8 GB. The boat sandbox ran on an AMD Ryzen 9 9950X host; boat also places sandboxes on other hosts.

Use boat when your agents work for hours on one machine: builds, tests, Docker, emulators and a built-in desktop with a browser, with an API to drive the agents inside. Check the start limits of your plan first. Compare it one to one: boat vs Vercel Sandbox and boat vs Blaxel.

boat's own limits
  • Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
  • Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
  • A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
  • Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
  • boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
  • Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
  • Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
  • Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source

Questions people ask

Is Vercel Sandbox cheaper than Blaxel?

In the scenarios where Blaxel fits, Blaxel costs less: one workday agent is $33 a month against $57 on Vercel, and 50 parallel agents are $1,489 against $2,884. One agent that never stops is $120 on Blaxel, and Vercel does not fit it as one session. Blaxel's self-serve tiers cap you at 200 sandboxes at once, so the 300-user and 1,000-job scenarios need a sales tier, while Vercel fits them at $828 and $3,152. boat is $20, $26 and $317 for the first three.

Which is faster, Vercel Sandbox or Blaxel?

In StarSling's run of 3 October 2026, Blaxel did 18.03 runs per second on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, and Vercel Sandbox 12.66. Both share rank 7, so the run cannot separate them. boat did 28.06, second of 15, on an AMD Ryzen 9 9950X host. For start time with 100 at once, ComputeSDK measured Blaxel at 364 ms and Vercel at 533 ms.

Can Vercel Sandbox and Blaxel run Docker?

Yes, both. Vercel lets you run Docker with sudo, and Blaxel has a Docker-in-sandbox image. Vercel gives no /dev/kvm, and Blaxel does not document it, so Android emulators and VMs need boat, which exposes /dev/kvm.

Can they run 24/7?

Vercel Sandbox cannot as one session: it stops after 24 hours on Pro, then resumes from its snapshot with processes starting again. Blaxel has no session cap, but its lower tiers delete sandboxes after up to 7 or 30 days. boat has no session cap once you turn auto-stop off (default 1 hour) on a paid plan.

Which one has a desktop for computer use?

Blaxel offers a desktop image with VNC. On Vercel Sandbox you install Chromium and agent-browser yourself, with Vercel's guide, and a full desktop has no documented recipe. boat streams a 60 fps desktop with Chrome, computer tools and a browser-control API.

Where do they run?

Vercel Sandbox runs in 19 regions around the world. Blaxel runs in Oregon, North Virginia, London and Frankfurt. boat runs on machines in Germany, Finland and France, and you cannot pick a region. Snapshot copies can be stored outside the EU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons