CodeSandbox SDK vs Deno Sandbox

Both run each sandbox in a Firecracker microVM. CodeSandbox SDK keeps a VM around, hibernated with its memory, wakes it on an HTTP request and forks it from a warm state. Deno Sandbox starts a 2 vCPU machine that Deno says boots in under 200 ms and lives up to 30 minutes; since November 2026 it is closed to new customers.

The companies and products

CodeSandbox SDK

CodeSandbox SDK is an API from CodeSandbox, now a Together AI company, that starts sandboxed development VMs on the same infrastructure as the CodeSandbox editor.

Each sandbox is a Firecracker microVM built from a template or any Dockerfile. When it goes idle, it hibernates with a memory snapshot, and it resumes or forks from that snapshot in seconds. You drive it from a TypeScript SDK through terminals, commands, files and HTTPS hosts. Together's docs call it the deprecated offering and point new users to its successor, the together-sandbox SDK.

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.

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. “32nd cheapest of 365” means 31 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 workloadCodeSandbox SDK: price rankDeno Sandbox: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
CodeSandbox SDK fits a software factory with Docker on every VM and a 20 GB disk. A Deno sandbox lives up to 30 minutes on 2 vCPU, and Deno does not document Docker. boat adds SSH, /dev/kvm and a 51 GB disk.
32nd cheapest of 365
$3,731 a month
No published price5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
CodeSandbox SDK's hibernation and wake on request suit mostly idle assistants. A Deno sandbox ends after 30 minutes; a bootable volume in Chicago can keep its files for the next sandbox.
50th cheapest of 361
$4,811 a month
No published price6th 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 suit short code runs: CodeSandbox SDK resumes a hibernated VM with its memory, and Deno says a new sandbox starts in under 200 ms. Deno is closed to new customers.
54th cheapest of 336
$642 a month
No published price189th 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
CodeSandbox SDK's Scale plan stops at 250 VMs at once. Deno Sandbox is closed to new customers, and existing organizations get 5 at once by default. boat allows 100 to 2,000 at once by plan, within per-plan start limits.
140th of 349, with limits
$1,707 a month
No published price3rd 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
341st of 349, with limits
$3,861 a month
No published price39th 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
77th cheapest of 359
$1,335 a month
No published price10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
CI jobs that run Docker fit CodeSandbox SDK. Deno does not document Docker. boat also exposes /dev/kvm for Android emulators.
96th cheapest of 374
$860 a month
No published price2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
Deno has SSH and a browser editor but ends a sandbox after 30 minutes. CodeSandbox SDK connects through its SDK, with no SSH documented. boat is a VM with built-in SSH that you can keep on.
316th of 371, with limits
$240 a month
No published price19th cheapest of 371
$26 a month
Computer-use agents
50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month
Neither documents a desktop. On CodeSandbox SDK you add a VNC desktop to your own template; on Deno you install one yourself within 2 vCPU and 4 GB. boat streams a built-in 60 fps desktop with Chrome.
54th cheapest of 367
$1,236 a month
No published price7th cheapest of 367
$200 a month
Browser-use agents
50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month
125th of 356, with limits
$741 a month
No published price7th 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
119th cheapest of 343
$871 a month
No published price6th 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
194th of 327, with limits
$7,390 a month
No published price73rd 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
Deno limits outbound traffic to allowed hosts outside the VM. CodeSandbox SDK documents no egress rules but can fork a running sandbox with its memory. boat gives root and you filter with nftables.
29th cheapest of 351
$505 a month
No published price3rd 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 requirementNo published priceNot 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 requirementNo published priceNot ranked: misses a requirement

Key features

FeatureCodeSandbox SDKDeno Sandboxboat
IsolationFirecracker microVM with its own kernelFirecracker microVM with its own kernelFull VM with its own kernel, on hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Machine sizeFixed sizes up to 16 cores / 32 GB on Scale, 64 cores / 128 GB on Enterprise; 20 GB disk2 vCPU, 768 MB to 4 GB memory, 10 GB disk2 to 16 vCPU and 4 to 32 GB, 51 to 251 GB disk; 16 vCPU needs the $100 plan or higher
Session lengthNo hard cap; hibernates after an idle timeout of up to one dayUp to 30 minutes; longer work can be promoted to a Deno Deploy appAuto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no cap
Sleep and wakeHibernates with a memory snapshot; resumes in about 0.5 to 2 s; an HTTP request can wake itNo pause or resume; Deno says a new sandbox starts in under 200 msAuto-stop timer, not idle detection; resume boots the VM again
Disk20 GB disk per VM, kept through hibernation; more on request, price not publishedDefault root disk is wiped at the end; a volume (300 MB to 20 GB, Chicago only) keeps files and can be the bootable root disk51 GB disk on the default size, saved every minute and at each stop; kept at least 14 days while stopped
Fork and snapshotsFork a hibernated sandbox from its snapshot, or a running one sharing its memoryRead-only volume snapshots that many new sandboxes can boot from (Chicago only)Fork a running sandbox from its last 1-minute snapshot (disk only)
Docker and nested virtualizationDocker and root on every VM, built from any Dockerfile; /dev/kvm not documentedRoot access; Docker and nested virtualization not documentedDocker, systemd and /dev/kvm for Android emulators and VMs
SSHTerminals, commands and files through the SDK; SSH is not documentedSSH and a VS Code editor in the browserBuilt-in SSH, root and systemd
Desktop and browserHeadless Chromium template; you can install a VNC desktop in your own DockerfileNo desktop documented; you install a browser yourself with apt-getLinux desktop and Chrome streamed at 1920x1080, 60 fps, with computer-use tools
Inbound accessHTTPS host per port, public by default, signed tokens for private sandboxesHTTPS URL per exposed port, public without authentication; SSHSSH, up to 50 HTTPS URLs per sandbox (token-gated by default), raw ports over public IPv6
Outbound rulesNo egress allowlist or static egress IP documentedHost allowlist per sandbox, enforced outside the VMOpen internet; filter inside the VM with nftables
Keeping API keys out of the sandboxSecrets go in as environment variables; no credentials proxy documentedPlaceholder secrets swapped for real ones on requests to approved hostsOptional AI credentials proxy ($1 a day plus $1 per 1,000 requests); keys of supported model providers stay outside, other secrets still enter the sandbox
Coding agentsYou install your own agent in the template and run it through the commands APIA root image with Claude Code, run through the shell command APISeven harnesses installed, with a prompt, steer and events API
Regions and availabilityA country hint steers scheduling, but placement is not guaranteed; self-serve sign-up; Together calls this SDK deprecatedAmsterdam and Chicago; closed to new customers since November 2026Germany, Finland and France, no region choice; self-serve plans from $20 a month
Every feature Battleships tracks (43)
FeatureCodeSandbox SDKDeno Sandboxboat
Full VM (own kernel)YesYesYes
Docker insideYesNot publishedYes
Nested virtualizationNo documented wayNo documented wayYes
RootYesYesYes
SystemdNot publishedNot publishedYes
Desktop GUIWith your own setupNo documented wayYes
BrowserWith your own setupNo documented wayYes
Computer-use APINo documented wayNo documented wayYes
SSHNo documented wayYesYes
Persistent diskYesYesYes
Pause/resumeYesNo documented wayYes
Automatic snapshotsYesNo documented wayYes
Fork/cloneYesNo documented wayYes
Live fork (no pause)YesNo documented wayYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesNo documented wayYes
Idle auto-stopYesNo documented wayNo documented way
Wake on requestYesNo documented wayNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistNo documented wayYesNo documented way
Secret proxyNo documented wayYesYes
Secret proxy for any APINo documented wayYesYes
Preinstalled agentsNo documented wayYesYes
Agent harness APINo documented wayNo documented wayYes
MCP serverNo documented wayNo documented wayNo 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 wayNo documented wayNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNot publishedYesYes
Usage per sandbox (API)No documented wayNo documented wayYes
Audit logsNot publishedNot publishedNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesNot publishedNo documented way
HIPAANo documented wayNot publishedNo documented way
EU data residencyNo documented wayYesNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

CodeSandbox SDKNot measured
Deno SandboxNot measured
boat28.06 runs/s

CodeSandbox SDK and Deno Sandbox are not in StarSling's run of 3 October 2026 (run 37073680030), so we cannot say which is faster at CPU work; Deno is fixed at 2 vCPU. In that run boat did 28.06 V8 Web Tooling Benchmark runs per second at 4 vCPU / 8 GB, second of 15. Every boat sandbox in that run ran on an AMD Ryzen 9 9950X host; boat also places sandboxes on Ryzen 7 9700X hosts and does not promise a CPU model. For start time, ComputeSDK measured CodeSandbox SDK at 11.76 s median with 100 at once (6 November 2026); Deno says a new sandbox starts in under 200 ms, a claim not in ComputeSDK. 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. 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. CodeSandbox SDK 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.

ScenarioCodeSandbox SDK, a monthDeno Sandbox, 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
$193 · ScaleNo published price$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$341 · ScaleNo 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
$2,500 · ScaleNo 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
$815 · Scale · with limitsNo 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
$1,632 · Scale · with limitsNo published price$8,800 · $2000/mo · with limits

CodeSandbox SDK: CodeSandbox SDK sells VM credits at $0.01486 each, and a 4 vCPU / 8 GB VM burns 20 an hour, about $0.30. Billing is per started minute while the VM runs, including idle time before it hibernates. A hibernated VM costs nothing. The Scale plan adds a $170 monthly platform fee that is not usage credit.

Deno Sandbox: Deno Sandbox is no longer included in Deno Deploy plans and is not available to new customers (November 2026). Deno publishes no current sandbox rates, so we do not price it in our scenarios.

Deno Sandbox: Plans cost $20, $100, $500 or $2,000 a month. The whole plan price comes back as VM time for that month, and it does not carry over. A default sandbox costs $0.036 an hour, billed per second while it runs, busy or idle. A stopped sandbox has no compute charge, but saved snapshots above the included count and the AI credentials proxy still charge. The $20 plan includes 200 starts 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 run at once by default. CodeSandbox SDK fits the workday agent, the always-on agent and 50 agents in parallel, but its Scale plan stops at 250 VMs at once, so 300 users and 1,000 jobs need an Enterprise plan; it publishes no price for disk beyond 20 GB or for egress. boat's plans allow 100 to 2,000 at once; at 1,000 jobs at once its $2,000 plan charges for starts above 90 a minute, refuses them above 270, and never queues a start.

ScenarioCodeSandbox SDKDeno Sandboxboat
One coding agent, workdays
  • disk beyond 20 GiB: price unknown
  • egress price not published
  • discontinued / closed to new customers
None for this scenario
One agent that never stops
  • disk beyond 20 GiB: price unknown
  • egress price not published
  • discontinued / closed to new customers
None for this scenario
50 agents in parallel
  • egress price not published
  • discontinued / closed to new customers
None for this scenario
Sandboxes for your users
  • Scale: max 250 concurrent
  • egress price not published
  • discontinued / closed to new customers
None for this scenario
1,000 short jobs at once
  • Scale: max 250 concurrent
  • egress price not published
  • discontinued / closed to new customers
  • 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 CodeSandbox SDK when

your sandboxes sleep between visits and should wake on the next HTTP request with their memory, or when you fork many runs from one warm state, and you accept that Together calls this SDK deprecated.

  • Hibernates and wakes with its memory. Useful for sandboxes that sit idle: one hibernates with its processes and wakes on the next HTTP request where it was.
  • Forks that share memory. For branching many runs from one warm state: fork a running sandbox while it shares memory with its parent.
  • Bigger VMs with Docker and a disk. For agents that work for hours: up to 16 cores on Scale, Docker on every VM, a 20 GB disk and no 30-minute limit.

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, reach only the hosts you allow, and live on Deno Deploy.

  • Fast starts for short bursts. Deno says a sandbox starts in under 200 ms, fast enough to create one per request, for teams that already have it.
  • Outbound rules and secret swapping. Each sandbox reaches only the hosts you allow, and real secrets replace placeholders only on requests to approved hosts.
  • SSH and an editor in the browser. Handy for looking inside a run: each sandbox offers SSH and a VS Code editor in the browser.

Where boat fits

CodeSandbox SDK and Deno Sandbox are both Firecracker microVMs tuned for quick starts and short runs. If your agents do real work for hours, with builds, Docker, emulators and a browser, boat gives each one a whole Linux machine with a disk and coding agents you drive from outside through one API. boat does not keep memory across a stop, and it runs only in Germany, Finland and France.

A whole Linux machine

boat has systemd, built-in SSH, Docker and /dev/kvm. Neither CodeSandbox SDK nor Deno documents /dev/kvm, so an Android emulator or a VM is not a supported path on either, and Deno does not document Docker.

A bigger disk on every sandbox

CodeSandbox SDK gives 20 GB, with no published price for more. Deno wipes the default root disk when a sandbox ends after at most 30 minutes; its volumes keep files, in Chicago only. boat saves a 51 GB disk every minute and at each stop.

Open to new customers, with agents installed

Deno Sandbox is closed to new customers, and Together calls the CodeSandbox SDK deprecated. boat has self-serve plans from $20 a month and seven coding agents you drive by API. A running boat sandbox bills busy or idle, because auto-stop is a timer.

Use boat when your agents do real work for hours: builds, tests, Docker, emulators and a browser on a whole Linux machine with SSH and a disk saved every minute. Compare it one to one: boat vs CodeSandbox SDK 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 CodeSandbox SDK cheaper than Deno Sandbox?

We cannot compare today. Deno Sandbox is closed to new customers since November 2026 and publishes no current rates. On CodeSandbox SDK, one agent that never stops costs $341 a month and 50 agents in parallel $2,500 in our scenarios; boat costs $26 and $317.

Which is faster, CodeSandbox SDK or Deno Sandbox?

We cannot say for CPU work: neither is in StarSling's run of 3 October 2026, where boat did 28.06 runs per second. For start time, ComputeSDK measured CodeSandbox SDK at 11.76 s median with 100 at once, and Deno says a new sandbox starts in under 200 ms.

Can CodeSandbox SDK or Deno Sandbox run Docker?

CodeSandbox SDK runs Docker on every VM and builds from any Dockerfile. Deno's docs do not say Docker works inside a sandbox. Neither documents /dev/kvm for emulators. boat runs Docker and systemd and exposes /dev/kvm.

How long can a sandbox run?

A Deno sandbox lives up to 30 minutes, and longer work can be promoted to a Deno Deploy app. A CodeSandbox SDK VM has no hard cap and hibernates after its idle timeout. boat's auto-stop defaults to 1 hour; on a paid plan you can turn it off, and then there is no cap.

Are both still available?

Deno Sandbox is closed to new customers since November 2026. CodeSandbox SDK still has self-serve sign-up, but Together's docs call it deprecated and name together-sandbox, which your organization must ask Together to enable, as its successor; the last SDK release was 2.4.2 in December 2025.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons