Beam vs Deno Sandbox
Beam is a serverless GPU platform whose gVisor sandboxes can run until you stop them, with separate CPU VMs that keep their disk. Deno Sandbox gives short runs of untrusted code a locked-down 2 vCPU Firecracker microVM that lives up to 30 minutes. Since November 2026, Deno Sandbox is closed to new customers.
The companies and products
Beam
Beam is a serverless cloud for GPU inference, sandboxes, VMs and background jobs, built on its open-source runtime Beta9.
Beam runs functions, REST endpoints, task queues, pods, sandboxes and VMs on CPUs and GPUs, from a Python or TypeScript SDK. A sandbox is a container isolated with gVisor by default. It lives until you terminate it or its time to live runs out, and you can save it as a filesystem image or a memory snapshot. Beam VMs are a separate CPU product: a microVM with its own kernel, systemd, a root disk that stays when it stops, and a browser desktop. A VM can pause with its memory, fork and take disk snapshots. CPU work runs on Spot, Shared or Performance tiers at different prices.
Deno Sandbox
Deno Sandbox comes from the company behind the Deno runtime and runs untrusted or AI-generated code in Linux microVMs. Since November 2026 it is not part of Deno Deploy plans and is not available to new customers.
Each sandbox is a Firecracker microVM with 2 vCPU, 768 MB to 4 GB of memory and a 10 GB disk that is wiped when it ends, created from a TypeScript or Python SDK. A bootable volume (Chicago only) can be the root disk and keep its files. Deno Deploy can limit outbound traffic to a host allowlist and swap placeholder secrets for real ones. A sandbox can be promoted to a Deno Deploy app.
- Isolation
- Firecracker microVM per sandbox
- Lifetime
- Up to 30 minutes
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. “7th cheapest of 365” means 6 of the other 364 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 | Beam: price rank | Deno Sandbox: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month A software factory runs installs, builds and Docker for hours, which is longer than Deno's 30-minute lifetime. Beam VMs and boat sandboxes have Docker, systemd and a disk that stays; boat adds /dev/kvm. | 7th cheapest of 365 $1,200 a month | No published price | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 12th cheapest of 361 $1,495 a month | No published price | 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 Beam fits short code runs: sandboxes bill per millisecond and end when their time to live runs out. Deno says its sandboxes start in under 200 ms, but it is closed to new customers, and existing organizations get 5 at once by default. | 21st cheapest of 336 $161 a month | No published price | 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 Beam and boat both fit a sandbox per user. Deno Sandbox is closed to new customers. Beam sandbox URLs and Deno URLs have no built-in auth; boat URLs are token-gated by default. | 14th cheapest of 349 $567 a month | No published price | 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 | 332nd of 349, with limits $984 a month | No published price | 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 | 16th cheapest of 359 $258 a month | No published price | 10th cheapest of 359 $200 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Beam and boat both run Docker for CI jobs. Builds that need Android emulators or VM images need /dev/kvm, which boat documents and the other two do not. | 29th cheapest of 374 $300 a month | No published price | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Beam VMs and boat both keep their disk while stopped, so either works as a dev box. On Deno, a bootable volume in Chicago keeps the files for the next sandbox. | 44th cheapest of 371 $55 a month | No published price | 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 Beam VMs have a browser desktop with an SDK for clicks and screenshots. On Deno you install a browser yourself with apt-get, within 2 vCPU and 4 GB. boat streams a desktop with Chrome at 60 fps. | 12th cheapest of 367 $431 a month | No published price | 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 | 73rd of 356, with limits $272 a month | No published price | 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 | 16th cheapest of 343 $196 a month | No published price | 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 | 44th of 327, with limits $967 a month | No published price | 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 | 6th cheapest of 351 $219 a month | No published price | 3rd cheapest of 351 $200 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month Beam has GPUs, from RTX 4090 up to H100 and B200. Deno Sandbox and boat have no GPU. | Cheapest of 102 $547 a month | No published price | 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 | No published price | Not ranked: misses a requirement |
Key features
| Feature | Beam | Deno Sandbox | boat |
|---|---|---|---|
| Isolation | gVisor container by default for sandboxes, with an opt-in VM-backed mode; Beam VMs are CPU microVMs with their own kernel | Firecracker microVM with its own kernel | Full VM with its own kernel, on physical hosts dedicated to boat; vCPUs are shared |
| Machine size | You request CPU and memory per sandbox; Beam VMs have a 50 GiB root disk by default, up to 100 GiB | 2 vCPU (no CPU option documented), 768 MB to 4 GB memory, 10 GB disk | 2 to 16 vCPU and 4 to 32 GB, with 51 to 251 GB of disk; 16 vCPU needs the $100 plan or higher |
| Lifetime | Sandbox default 10 minutes, or -1 to run until you terminate it; VMs run until you stop them | Up to 30 minutes; for longer work, start a new sandbox or promote it to a Deno Deploy app | Auto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no cap |
| Disk between runs | A sandbox keeps files through a saved image, a memory snapshot or a volume; a Beam VM keeps its root disk while stopped | Default root disk wiped at the end; a bootable volume (300 MB to 20 GB, Chicago only) can be the root disk and keeps its files | Disk saved every minute and at stop, with no code; kept at least 14 days after a stop; memory is not saved |
| Snapshots and fork | Sandbox memory snapshots with running processes; VMs pause with RAM kept, fork and take disk snapshots | Read-only snapshots of a volume that many new sandboxes can boot from (Chicago only) | Automatic disk snapshots; fork a running sandbox from its last 1-minute snapshot |
| Docker, systemd and nested virtualization | Beam VMs have Docker and systemd; sandboxes run Docker with docker_enabled; /dev/kvm not documented | Root access; Docker, systemd and nested virtualization not documented | Docker, systemd, root and /dev/kvm for Android emulators and VMs |
| GPUs | GPU sandboxes, serverless GPUs and GPU machines up to H100, H200 and B200 | No GPU | No GPU on any size |
| Desktop and browser | Beam VMs have a browser Linux desktop with Chrome and an SDK for screenshots, clicks and typing; documented for VMs, not sandboxes | No desktop documented; a VS Code editor in the browser and SSH; you install a browser with apt-get | Desktop and Chrome in every sandbox at 1920x1080 and 60 fps, with computer tools for agents |
| Inbound access | Sandboxes: a public HTTPS URL per port, no built-in auth. VMs: token-protected URLs and TCP ports on a persistent public IPv6 address | A public HTTPS URL per exposed port, without authentication; SSH | Up to 50 HTTPS URLs per sandbox, token-gated by default; SSH; raw ports on public IPv6, and on IPv4 where the sandbox has its own address |
| Outbound rules | Block all, or allow up to 64 hosts, wildcard domains, IPs or CIDRs, changeable while running | Host allowlist per sandbox (allowNet), enforced outside your code | Open internet, no provider-side allowlist |
| Keeping API keys out of the sandbox | Brokered secrets: the guest sees a placeholder, and Beam puts the real key into HTTPS headers to approved hosts | Any secret swapped in on outbound HTTPS requests to approved hosts; the sandbox only sees a placeholder | Optional AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests) for supported model providers; other secrets still enter the sandbox |
| Coding agents | You install agents and run them through process exec; Beam's MCP server plugs into Claude Code, Codex and Cursor | A root image with Claude Code, run through the shell command API | Seven agents installed, with a prompt, steer and events API |
| Start time | 534 ms median with 100 at once (ComputeSDK, 2026-11-06, default size) | Under 200 ms, as stated by Deno; not in ComputeSDK | Boots a full VM; not in ComputeSDK |
| Regions and availability | US by default; another region if you choose one; self-serve plans | Amsterdam or Chicago; closed to new customers since November 2026 | Germany, Finland and France; you cannot pick a region; no US or Asia region; self-serve plans |
Every feature Battleships tracks (43)
| Feature | Beam | Deno Sandbox | boat |
|---|---|---|---|
| Full VM (own kernel) | No documented way | Yes | Yes |
| Docker inside | Yes | Not published | Yes |
| Nested virtualization | No documented way | No documented way | Yes |
| Root | Yes | Yes | Yes |
| Systemd | No documented way | Not published | Yes |
| Desktop GUI | No documented way | No documented way | Yes |
| Browser | No documented way | No documented way | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | With your own setup | Yes | Yes |
| Pause/resume | No documented way | No documented way | Yes |
| Automatic snapshots | No documented way | No documented way | Yes |
| Fork/clone | Yes | No documented way | Yes |
| Live fork (no pause) | Yes | No documented way | Yes |
| Memory fork | Yes | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | No documented way | Yes |
| Idle auto-stop | No documented way | No documented way | No documented way |
| Wake on request | No documented way | No documented way | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No documented way | No documented way | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | No documented way | Yes | Yes |
| Preinstalled agents | No documented way | Yes | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | Yes | No documented way | No documented way |
| GPU | Yes | No documented way | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | No documented way | No documented way | No documented way |
| Self-hosting | Yes | No documented way | No documented way |
| BYOC | Yes | No documented way | No documented way |
| Open source | Yes | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | Not published | Yes | Yes |
| Usage per sandbox (API) | No documented way | No documented way | Yes |
| Audit logs | Not published | Not published | No documented way |
| SSO | No documented way | No documented way | No documented way |
| SOC 2 | Yes | Not published | No documented way |
| HIPAA | Yes | Not published | No documented way |
| EU data residency | Not published | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Neither Beam nor Deno Sandbox is in the public CPU benchmark we use, so we cannot say which runs CPU work faster. For reference, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15 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. For start time, ComputeSDK measured Beam at 534 ms median with 100 at once (2026-11-06), at Beam's default size. Deno says its sandboxes start in under 200 ms; Deno and boat are 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. 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. Beam and Deno Sandbox are 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 | Beam, a month | Deno Sandbox, 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 | $20 · Developer | No published price | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $58 · Developer | No published price | $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 | $836 · Team | No published price | $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 | $312 · Team | No published price | $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 | $527 · Team · with limits | No published price | $8,800 · $2000/mo · with limits |
Beam: Beam bills sandboxes per millisecond while they run, for each vCPU and GiB, on Spot, Shared or Performance tiers; new accounts default to Performance. For 4 vCPU / 8 GiB that is $0.28 an hour on Performance, $0.088 on Shared and $0.036 on Spot. VMs bill per second while running, and nothing for compute while stopped. Developer is $20 a month with $20 of credit; Team is $89 a month plus usage. There are no egress fees, and storage is not billed yet.
Deno Sandbox: Deno Sandbox is no longer part of Deno Deploy plans and is not available to new customers (November 2026). Deno publishes no current sandbox rates. The launch post listed $0.05 per hour of CPU time, $0.016 per GB-hour of memory and $0.20 per GiB-month of volume storage.
Deno Sandbox: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs. A stopped sandbox has no compute charge and keeps its disk for at least 14 days, but saved snapshots above the included count and the AI credentials proxy still charge. The $20 plan includes 12 starts a minute and 200 a day; extra starts cost $0.03 to $0.07.
Limits in those scenarios
Deno Sandbox is closed to new customers, so it has no price in our scenarios. For existing organizations, a sandbox lives up to 30 minutes on 2 vCPU with up to 4 GB of memory, and 5 sandboxes run at once by default. Beam's Developer plan allows 30 vCPUs at once, so 50 parallel agents need Team, and Beam does not bill storage yet, so no disk cost is counted for it. For 1,000 short jobs at once, Beam Team allows 1,000 vCPUs at once where the burst needs 2,000, and boat's $2,000 plan charges for starts above 90 a minute and refuses them above 270. boat's auto-stop defaults to 1 hour.
| Scenario | Beam | Deno Sandbox | boat |
|---|---|---|---|
| One coding agent, workdays |
|
| None for this scenario |
| One agent that never stops |
|
| None for this scenario |
| 50 agents in parallel |
|
| None for this scenario |
| Sandboxes for your users |
|
| None for this scenario |
| 1,000 short jobs at once |
|
|
|
Which one should you use?
Use Beam when
your work needs GPUs, when sandboxes must run longer than half an hour, when you want CPU VMs that keep their disk, or when you must self-host.
- GPUs in the same platform. For work that needs a GPU, Beam offers GPU sandboxes, serverless GPUs and GPU machines from RTX 4090 to H100, H200 and B200.
- Sandboxes and VMs that run as long as you need. A Beam sandbox can run until you terminate it, and Beam VMs keep their root disk while stopped and can pause with memory.
- Open source and your own cloud. Its Beta9 runtime is AGPL-3.0 and free to self-host, and Beam can also run in your own cloud for a fee.
Use Deno Sandbox when
Use Deno Sandbox if your organization already has it and you run short pieces of untrusted code that must start fast and reach only the hosts you allow. New customers cannot sign up since November 2026.
- Fast starts for short code. Good for short bursts of code: Deno says a sandbox starts in under 200 ms.
- Locked-down outbound traffic and secrets. Each sandbox can be limited to a list of hosts, and real secrets are swapped in only on requests to those hosts.
- Two regions and a path to Deno Deploy. Sandboxes run in Amsterdam or Chicago, and one can be promoted to a Deno Deploy app. New customers cannot sign up since November 2026.
Where boat fits
If your agents install, build and test for hours, run Docker or emulators, or need a browser they can see, look at boat. Every boat sandbox is a full VM with its own kernel, /dev/kvm, a desktop and coding agents. boat saves the disk every minute and lets you fork a running sandbox.
A full VM with /dev/kvm
Beam VMs have their own kernel and systemd, but Beam documents no /dev/kvm. Deno is fixed at 2 vCPU and 4 GB and documents neither Docker nor nested virtualization. Every boat sandbox has Docker, systemd and /dev/kvm, up to 16 vCPU / 32 GB.
A disk saved with no code
A Deno sandbox ends after 30 minutes, and a volume in Chicago keeps its files. A Beam sandbox keeps files through a saved image or a volume, and a Beam VM keeps its disk. boat saves the disk every minute and at stop, and has no session cap once auto-stop is off on a paid plan. A resume is like a reboot.
Agents, desktop and gated URLs
On Beam you install agents yourself, and on Deno you run Claude Code through shell commands. Beam sandbox and Deno URLs have no built-in auth. boat installs seven agents, streams a 60 fps desktop and token-gates up to 50 URLs per sandbox.
Use boat when your agents work for hours or days: installs, builds, Docker, emulators and a browser on a full VM whose disk is saved every minute. Compare it one to one: boat vs Beam and boat vs Deno Sandbox.
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 Beam cheaper than Deno Sandbox?
We cannot compare today. Deno Sandbox is closed to new customers since November 2026 and publishes no current rates. In this page's scenarios, Beam costs $20 a month for one agent on workdays, $58 for one agent that never stops and $836 for 50 agents in parallel. boat costs $20, $26 and $317.
Which is faster, Beam or Deno Sandbox?
Neither is in the public CPU benchmark we use, so there is no fair CPU comparison. ComputeSDK measured Beam at 534 ms to start with 100 at once. Deno says a sandbox starts in under 200 ms, but Deno is not in ComputeSDK.
Can Beam or Deno Sandbox run Docker?
Beam runs Docker in a sandbox with docker_enabled and in its VMs. Deno's docs do not mention Docker inside a sandbox. boat runs Docker and systemd in a full VM and exposes /dev/kvm for emulators and VMs.
How long can a sandbox run on each?
A Deno sandbox lives up to 30 minutes, and you can promote it to a Deno Deploy app for longer work. A Beam sandbox defaults to 10 minutes but can run until you terminate it. boat has no session cap once auto-stop is off on a paid plan (the default is 1 hour).
Do Beam and Deno Sandbox keep files?
A Deno sandbox wipes its default root disk when it ends; a bootable volume in Chicago keeps its files. A Beam sandbox keeps files through a saved image, a snapshot or a volume, and a Beam VM keeps its root disk while stopped. boat saves the disk every minute and at stop; if a machine fails, you lose what was written after the last good snapshot.
Is boat SOC 2 compliant?
No SOC 2 report today; SOC 2 is in progress. Beam has SOC 2 Type II. Live status is at status.ascii.dev and our data retention policy is at docs.boat.dev/data-retention.
Try boat
Install the CLI, then run boat new.
7-day free trial