Vercel Sandbox vs Instabox
Both run each sandbox in a Firecracker microVM with its own kernel. Vercel Sandbox is built for many runs of code in 19 regions, with 24-hour sessions that resume from a snapshot. Instabox gives each agent a Linux machine with a free plan, pause with memory, SSH and a desktop, and paid plans from $20 a month plus usage.
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.
- Default image
- Ubuntu; the universal image adds Node.js 24, Python 3.14, Bun, and Claude Code, Codex, OpenCode and pi preinstalled
- Longest session
- 24 hours on Pro and Enterprise, 45 minutes on Hobby; a persistent sandbox resumes from its last snapshot with no cap on total lifetime
- Biggest sandbox
- 8 vCPU / 16 GB on Pro, 32 vCPU / 64 GB on Enterprise
Instabox
Instabox gives each AI agent its own Linux machine in the cloud. It has a free plan with one machine and paid plans from $20 a month plus usage.
Each Instabox machine is a Firecracker microVM with its own kernel, root and Docker. It starts from a template (agent-browser by default, universal, t3, herdr, orca, android, omarchy or ci), from your own snapshot, or from a Docker image that you import as a snapshot. The default size is 4 vCPU / 8 GiB, and paid plans go up to 32 vCPU / 64 GiB. You drive it from a CLI, a TypeScript SDK, an HTTP API or an MCP server, with SSH, mosh, HTTPS port URLs and a desktop for computer use.
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 workload | Vercel Sandbox: price rank | Instabox: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Instabox fits a software factory at $410 a month in this preset, with Docker, a desktop on most templates and machines up to 32 vCPU. Vercel is a compromise: a 24-hour session cap, no built-in desktop and no nested virtualization. boat fits at $634, with /dev/kvm and an agent API. | 259th of 365, with limits $3,351 a month | Cheapest of 365 $410 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB Instabox fits always-on assistants once you turn off its idle pause (default 30 minutes) on a paid plan. Vercel resumes across 24-hour sessions, but processes start again, so it is a compromise. | 75th of 361, with limits $3,657 a month | 4th cheapest of 361 $534 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. Vercel bills CPU only while code uses it ($216 a month here); Instabox bills per second while a machine runs, at a lower list rate ($56 here). | 27th cheapest of 336 $216 a month | 4th cheapest of 336 $56 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 Both fit sandboxes for your users. Vercel Pro runs up to 10,000 at once. Instabox runs 100 to 500 at once by plan, so 300 at once needs its $500 Team plan. boat fits at $209 a month here. | 25th cheapest of 349 $1,267 a month | 10th cheapest of 349 $500 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 fits many short parallel rollouts. Instabox is a compromise here: its Team plan runs at most 500 machines and 100 starts a minute. | 7th cheapest of 349 $15,761 a month | 16th of 349, with limits $845 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 | 34th cheapest of 359 $500 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 Instabox fits CI at $89 a month here, with a ci template that works as a GitHub Actions runner. Vercel fits too, at $1,144. For Android emulators or VM builds you need /dev/kvm: Vercel has none, Instabox does not document it, and boat exposes it. | 112th cheapest of 374 $1,144 a month | 3rd cheapest of 374 $89 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Instabox fits a cloud dev box with SSH, mosh and pause with memory. On Vercel the files stay, but the session stops every 24 hours and it has no SSH server. | 283rd of 371, with limits $145 a month | 14th cheapest of 371 $24 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 Instabox fits computer use: a VNC desktop with a browser on most templates and a screenshot and click API; you bring the model. Vercel has no built-in desktop; you install one with root. boat streams a 60 fps desktop with computer tools. | 263rd of 367, with limits $952 a month | 4th cheapest of 367 $122 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 | 100th of 356, with limits $486 a month | 49th of 356, with limits $61 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 | 5th cheapest of 343 $83 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 | 31st of 327, with limits $1,658 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 | 2nd cheapest of 351 $100 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 requirement | Not ranked: misses a requirement | Not 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 requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | Vercel Sandbox | Instabox | boat |
|---|---|---|---|
| Isolation | Firecracker microVM with its own kernel | Firecracker microVM with its own kernel and root | Full VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared |
| Machine sizes | Up to 8 vCPU / 16 GB on Pro, 32 vCPU / 64 GB on Enterprise | 4 vCPU / 8 GiB on Free; up to 8 / 16 on Pro, 16 / 32 on Builder, 32 / 64 on Team | Up to 8 vCPU / 16 GB on the $20 plan and 16 vCPU / 32 GB on $100 and above |
| Longest session | 24 hours per session on Pro and Enterprise, 45 minutes on Hobby; a persistent sandbox then resumes from its snapshot, with no cap on total lifetime | No cap on paid plans once you turn off the idle pause (default 30 minutes); Free pauses after 8 hours of running | No session cap once you turn auto-stop off on a paid plan; auto-stop defaults to 1 hour and goes up to 30 days |
| Pause and resume | Stop saves the files; memory and running processes start again | Pause keeps memory and running programs; resume usually takes about a second; a port visit wakes an idle-paused machine | Stop keeps the disk; memory is not saved, so a resume is like a reboot |
| Saving files | Filesystem snapshot at every stop, on by default, $0.08/GB-month; expires 30 days after last use, or never if you set it. Plus Drives: mounted storage kept until you delete it | Snapshots saved by hand, free; 5 on Free, unlimited on paid plans; no automatic save | Disk saved every minute and at each stop, at no charge; a stopped disk is kept at least 14 days; saved snapshots never expire, each one above the plan's count costs $0.056 a day |
| Desktop and computer use | No built-in desktop, browser or computer-use API; you install Chromium and agent-browser yourself (root access, Vercel guide) or connect an external cloud browser | VNC desktop with a browser on most templates, screenshot and click API, shareable view or control links; you bring the model | Built in: 1920x1080, 60 fps desktop and Chrome, computer tools for every built-in agent, embeddable stream |
| Nested virtualization | No; Firecracker does not expose /dev/kvm to guests | /dev/kvm not documented; an android template runs Android natively, with no emulator | Yes, /dev/kvm for Android emulators and VMs |
| Docker inside | Yes, with sudo | Docker and Docker Compose, with root and systemd | Yes, with root and systemd |
| Custom images | Your own OCI images from a Dockerfile, via Vercel Container Registry | Templates, your own snapshots, or a Docker or OCI image imported as a snapshot | Start from boat's image or a saved snapshot (template), shareable by code; you cannot boot your own Docker or OCI image |
| Coding agents | Claude Code, Codex, OpenCode and pi preinstalled; you start them as commands | Claude Code, Codex and OpenCode on some templates; CLI, skills and an MCP server; you run the agent yourself | Seven agents preinstalled, with an API to prompt, steer and stream events |
| Public port URLs | Up to 15 ports, no built-in auth; no raw TCP or public IP | HTTPS on up to 16 ports, public by default, token-protected with --private; raw TCP through the port gateway | HTTPS on up to 50 ports, token-gated by default; raw ports over IPv6 (some sandboxes have no IPv4 of their own); no static IP |
| SSH | No SSH server; you use the SDK or the sandbox CLI | SSH through a gateway with short-lived certificates, paste-anywhere SSH tokens and mosh | SSH into every sandbox |
| Keeping API keys out of the sandbox | Credentials brokering injects headers for any HTTPS domain you allow | Secrets proxy swaps a placeholder for the real key in outbound HTTPS headers to allowed hosts | Optional AI credentials proxy ($1 per day while on, plus $1 per 1,000 requests) for model providers and any HTTPS API you add |
| Regions | 19 regions across the US, Europe, Asia, South America, Africa and Australia | Not published; you cannot choose where a machine runs | Germany, Finland and France; you cannot pick a region; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Vercel Sandbox | Instabox | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | No documented way | Not published | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Yes | Yes |
| Desktop GUI | No documented way | Yes | Yes |
| Browser | With your own setup | Yes | Yes |
| Computer-use API | No documented way | Yes | Yes |
| SSH | No documented way | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Yes | Yes |
| Memory fork | No documented way | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | No documented way | Yes | No documented way |
| Wake on request | No documented way | Yes | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No documented way | Yes | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Not published | No documented way |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | Yes | Yes | Yes |
| Preinstalled agents | Yes | Yes | Yes |
| Agent harness API | No documented way | Not published | Yes |
| MCP server | Yes | Yes | No documented way |
| GPU | No documented way | Not published | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | No documented way | Not published | No documented way |
| Self-hosting | No documented way | Not published | No documented way |
| BYOC | No documented way | Yes | No documented way |
| Open source | No documented way | No documented way | No documented way |
| Scoped API keys | Not published | Yes | Yes |
| Spend limits | Yes | Yes | Yes |
| Usage per sandbox (API) | No documented way | Yes | Yes |
| Audit logs | Not published | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Not published | No documented way |
| HIPAA | Yes | Yes | No documented way |
| EU data residency | Yes | Not published | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
On the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, boat did 28.06 runs per second and Vercel Sandbox did 12.66 (about 2.2x), in StarSling's run of 3 October 2026 (run 37073680030). 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. Instabox is not in the public benchmarks we use, so we cannot say how it compares. Instabox says a new machine's shell is ready in under a second; we have not measured that.
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. 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. Instabox is not in the public benchmarks we use, so we cannot say which is faster.
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.
| Scenario | Vercel Sandbox, a month | Instabox, a month | boat, 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 | $0 · Free | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $236 · Pro · with limits | $25 · Pro | $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 | $269 · Pro | $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 | $500 · Team | $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 | $500 · Team · 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. The $20 Pro credit is shared with your other Vercel usage.
Instabox: Instabox Free costs $0 for one 4 vCPU / 8 GiB machine. Pro ($20), Builder ($100) and Team ($500) a month each include usage credit equal to the fee. Usage costs $0.004 per vCPU-hour and $0.00225 per GiB-hour, per second while a machine runs, which is $0.034 an hour at 4 vCPU / 8 GiB. Disk above the included pool costs $0.08 per GiB-month, and egress above the allowance $0.02 per GiB. Snapshots and a paused machine's memory are free.
Instabox: 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; the sandbox resumes from its snapshot, but running processes start again. Instabox Free allows 1 machine and 3 starts a minute; Pro runs 100 machines at once, Builder 200 and Team 500, at 30, 50 and 100 starts a minute. So 1,000 short jobs at once do not fit Instabox. Vercel fits them at $3,152 a month. boat does not fit them either: even the $2,000 plan includes 90 starts a minute and 2,400 a day, starts above that are paid, and starts above 270 a minute fail with 429. Other boat limits: a stopped disk is kept at least 14 days unless you save a snapshot, no GPU, and no US or Asia region.
| Scenario | Vercel Sandbox | Instabox | boat |
|---|---|---|---|
| One coding agent, workdays | None for this scenario | None for this scenario | None for this scenario |
| One agent that never stops |
| None for this scenario | None for this scenario |
| 50 agents in parallel | None for this scenario | None for this scenario | None for this scenario |
| Sandboxes for your users | None for this scenario | None for this scenario | None for this scenario |
| 1,000 short jobs at once | None for this scenario |
|
|
Which one should you use?
Use Vercel Sandbox when
you run many short bursts of code at once, want images from your Dockerfile, or need to run close to users outside Europe.
- Many sandboxes at once. Useful for large fleets or bursts: Pro allows up to 10,000 sandboxes at once, while Instabox Team runs up to 500.
- Regions all over the world. Useful if your users are spread out: Vercel Sandbox runs in 19 regions, from Virginia to Tokyo and Sydney.
- A firewall you control from outside. A running sandbox can be switched to deny-all, or to a list of allowed domains, without a restart.
Use Instabox when
you want a free machine to start with, a low hourly rate, pause with memory, SSH with mosh, or machines up to 32 vCPU.
- A free plan and a low hourly rate. One 4 vCPU / 8 GiB machine is free, and paid use costs $0.034 an hour at that size, per second while running.
- Pause with memory. A paused machine keeps its memory and running programs and usually resumes in about a second.
- SSH gateway with mosh. Useful if you live in a terminal: mosh keeps a session alive through sleep and network changes, and SSH tokens paste anywhere.
Where boat fits
Look at boat if your agents work for hours on one machine and you want to drive them through one API. boat saves the disk every minute with no action from you, exposes /dev/kvm, and gives private port URLs by default. boat runs only in Europe, has no free plan and caps starts per plan.
Emulators and VMs inside
Vercel Sandbox has no nested virtualization, and Instabox does not document /dev/kvm. Instabox's android template runs Android natively, but other emulators and VM builds have no documented path. boat exposes /dev/kvm in every sandbox.
Disk saved every minute, with no action
Vercel snapshots at each stop, and on Instabox you save snapshots yourself. boat saves the disk every minute while a sandbox runs and once more at stop. A machine failure loses what was written after the last good snapshot, and memory is not saved.
Drive the agents inside from outside
On both, you start the coding agent yourself, so you write the code that prompts it, steers it and reads its output. boat gives you one API for that across seven agents.
Use boat when your agents work for hours on one machine: builds, tests, Docker, emulators and a built-in desktop with a browser, with private port URLs and 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 Instabox.
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 Instabox?
In our scenarios Instabox costs less in four of five. One workday agent is $0 on Instabox Free and $57 on Vercel, 50 parallel agents are $269 and $2,884, and 300 user sandboxes are $500 and $828. For 1,000 short jobs at once only Vercel fits, at $3,152. boat is $20, $317 and $200 for the first, second and third; it does not fit the 1,000-job burst.
Which is faster, Vercel Sandbox or Instabox?
We cannot say, because Instabox is not in the public benchmarks we use. Vercel Sandbox did 12.66 V8 Web Tooling runs per second at 4 vCPU / 8 GB, and boat did 28.06 on a Ryzen 9 9950X host, in StarSling's run of 3 October 2026.
Can Vercel Sandbox and Instabox run Docker?
Yes. Vercel runs Docker with sudo, and Instabox runs Docker and Docker Compose. For Android emulators or VMs inside, Vercel has no nested virtualization and Instabox does not document /dev/kvm; Instabox's android template runs Android natively. boat exposes /dev/kvm.
Can either one run 24/7?
Vercel Sandbox cannot as one session: Pro sessions stop after 24 hours, and the sandbox resumes with processes started again. Instabox runs with no cap on a paid plan once you turn off its idle pause (default 30 minutes). boat does the same once auto-stop is off (default 1 hour).
Do they have a desktop for computer use?
Vercel Sandbox has no built-in desktop; you install a browser or desktop with root, or connect a cloud browser. Instabox has a VNC desktop with a browser on most templates, with a screenshot and click API, and you bring the model. boat streams a 60 fps desktop with Chrome and computer tools for its built-in agents.
Can anyone sign up for Instabox?
Yes. Instabox has self-service sign-up with GitHub or Google, a Free plan, and paid plans that need a card. Vercel Sandbox has a free Hobby plan with 45-minute sessions, plus paid Pro and Enterprise plans.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Vercel Sandbox
- boat vs Instabox
- E2B vs Vercel Sandbox
- Daytona vs Vercel Sandbox
- Modal vs Vercel Sandbox
- Vercel Sandbox vs Cloudflare Sandbox
- Vercel Sandbox vs Blaxel
- Vercel Sandbox vs Runloop
- Vercel Sandbox vs Tensorlake
- Vercel Sandbox vs Morph Cloud
- Vercel Sandbox vs CodeSandbox SDK
- Vercel Sandbox vs Northflank