CodeSandbox SDK vs Upstash Box

CodeSandbox SDK gives each sandbox a Firecracker microVM that runs Docker and hibernates with its memory, so it wakes with its processes still running. Upstash Box gives each agent a light container with coding agents built in, billed only for the CPU it uses. Its docs do not describe Docker inside a box.

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.

Upstash Box

Upstash Box is a cloud computer for AI agents from Upstash, the company known for serverless Redis, Vector and QStash.

Each box is a Docker container with its own filesystem, shell, git and an optional coding agent such as Claude Code, Codex, OpenCode or Cursor, which you drive from TypeScript or Python SDKs. A box pauses when it sits idle, keeps its files, and you pay for the CPU it actually uses. Upstash built it to run its own Context7 service and opened it to everyone in March 2026.

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 rankUpstash Box: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
A software factory needs Docker for databases and test services. CodeSandbox SDK runs it. Upstash does not document Docker inside a box, which is itself a container. boat adds SSH, /dev/kvm and installed agents.
32nd cheapest of 365
$3,731 a month
98th of 365, with limits
$464 a month
5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
50th cheapest of 361
$4,811 a month
170th of 361, with limits
$450 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 suit short code runs. Upstash bills only the CPU a box uses, and its EphemeralBox deletes itself after at most 3 days. CodeSandbox SDK hibernates with its memory and wakes on the next request.
54th cheapest of 336
$642 a month
13th cheapest of 336
$119 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
Upstash fits 300 users at once. CodeSandbox SDK's Scale plan allows 250 VMs at once. boat fits too, with SSH and a desktop, and each create, fork or resume counts against the plan's start limits.
140th of 349, with limits
$1,707 a month
4th cheapest of 349
$222 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
CodeSandbox SDK's memory forks let many rollouts branch from the same running state. Upstash snapshots copy files, not memory, and so do boat forks.
341st of 349, with limits
$3,861 a month
343rd of 349, with limits
$8,000 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
Both fit eval runs. CodeSandbox SDK can fork many runs from one warm memory state, and Upstash can start many boxes from one snapshot.
77th cheapest of 359
$1,335 a month
67th cheapest of 359
$1,011 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
CodeSandbox SDK runs Docker builds inside its VMs. Upstash documents neither Docker nor /dev/kvm inside a box. boat has both, for container and Android builds.
96th cheapest of 374
$860 a month
122nd cheapest of 374
$1,480 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
A flat-price keep-alive Upstash box is a light dev box that stays on, with up to 30 GB of disk. CodeSandbox SDK bills every running minute. boat's is a full VM with a 51 GB disk at the default size, billed per second while it runs.
316th of 371, with limits
$240 a month
8th cheapest of 371
$19 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
Neither ships a desktop. CodeSandbox SDK has a headless Chromium template, and you can add a VNC desktop to your own Dockerfile. Upstash runs Chromium on a virtual display with a view-only live view. boat streams a full Linux desktop at 60 fps with computer-use tools.
54th cheapest of 367
$1,236 a month
123rd of 367, with limits
$76 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
125th of 356, with limits
$741 a month
48th of 356, with limits
$38 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
119th cheapest of 343
$871 a month
41st cheapest of 343
$400 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
194th of 327, with limits
$7,390 a month
201st of 327, with limits
$8,000 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
29th cheapest of 351
$505 a month
255th of 351, with limits
$259 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

FeatureCodeSandbox SDKUpstash Boxboat
IsolationFirecracker microVM with its own kernelDocker container per box on AWSFull VM with its own kernel, on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat; vCPUs are shared
Docker insideYes, with root; built from any DockerfileNot documented; the box is itself a container, and custom images are listed as coming soonYes, Docker and systemd run as on any Linux server; no custom Docker image
Nested virtualizationNot documentedNot documented; boxes are containersYes, /dev/kvm for Android emulators and VMs
Biggest machine16 cores / 32 GB on Scale, up to 64 cores / 128 GB on EnterpriseLarge: 8 vCPU / 16 GB on self-serve plans; custom sizes on EnterpriseUp to 16 vCPU / 32 GB on the $100 plan and above
Disk20 GB per VM; more on request, price not published10, 20 or 30 GB by size, billed per GB-month51 GB at the default 4 vCPU / 8 GB size, 51 to 251 GB by size; fixed per size
Pause and resumeHibernates with a memory snapshot; resumes with processes still runningPauses itself after 6 hours idle on paid plans and keeps its files; storage keeps billing while pausedDisk saved every minute and at each stop, kept at least 14 days; no compute charge while stopped; memory is not saved, so a resume is like a reboot
Billing while idleBills per started minute until it hibernates, then nothingNo CPU charge while a box is idle; RAM is not billedFull rate while the sandbox runs, busy or idle; auto-stop defaults to 1 hour
Wake on requestYes; an HTTP request to a host wakes itYes; a request to a public URL resumes a paused boxNo; a stopped sandbox is started by API
ForkFork a hibernated sandbox from its memory snapshot, or a running one that shares memory with its parentSnapshot a running box and start many new boxes from itFork a running sandbox from its last 1-minute disk snapshot; memory is not copied
Shell accessTerminals, commands and files through the SDK; SSH is not documentedSDK commands, plus SSH through a gatewaySSH, plus exec and files over the API
Inbound accessHTTPS host per port, public by default, signed tokens for private sandboxes; raw TCP is not documentedHTTPS URL per port, public unless you add a token or basic auth; raw TCP is not documentedHTTPS URLs for up to 50 ports, token-gated by default; raw ports on a public IPv6 address; no dedicated IPv4
Desktop and browserNo built-in desktop; a headless Chromium template, and you can install a VNC desktop in your own DockerfileManaged Chromium with AI page actions, CDP, screenshots, recordings and a view-only live view; no desktop or VNCBuilt-in Linux desktop and Chrome streamed at 1920x1080, 60 fps, with computer-use tools
Coding agentsYou install your own agent in the template and run it through the commands APIClaude Code, Codex, OpenCode and Cursor built in, plus custom agents, with run and stream APIs, webhooks and scheduled promptsSeven harnesses preinstalled, including Claude Code, Codex and OpenCode, with a prompt, steer and events API
Keeping API keys out of the sandboxSecrets passed in as environment variables; no credentials proxy documentedHost proxy injects headers into outbound HTTPS on port 443 for any host; set when the box is createdOptional paid credentials proxy ($1 a day plus $1 per 1,000 requests) for supported model providers; other secrets enter the sandbox
Outbound rulesNo outbound allowlist documentedAllow all, deny all, or allow and deny by domain and CIDR, changeable on a running boxOpen internet, no provider-side allowlist
RegionsA country hint steers scheduling, but placement is not guaranteedAWS us-east-1; custom regions on EnterpriseGermany, Finland and France; you cannot pick a region, and snapshot copies can be stored outside the EU
Every feature Battleships tracks (43)
FeatureCodeSandbox SDKUpstash Boxboat
Full VM (own kernel)YesNo documented wayYes
Docker insideYesNot publishedYes
Nested virtualizationNo documented wayNo documented wayYes
RootYesNot publishedYes
SystemdNot publishedNot publishedYes
Desktop GUIWith your own setupNo documented wayYes
BrowserWith your own setupYesYes
Computer-use APINo documented wayNo documented wayYes
SSHNo documented wayYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesNo documented wayYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo documented way
Wake on requestYesYesNo 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 wayYesYes
MCP serverNo documented wayYesNo documented way
GPUNo documented wayNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayYesNo 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 publishedNot publishedYes
Usage per sandbox (API)No documented wayYesYes
Audit logsNot publishedNot publishedNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesYesNo documented way
HIPAANo documented wayNo documented wayNo documented way
EU data residencyNo documented wayNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

CodeSandbox SDKNot measured
Upstash BoxNot measured
boat28.06 runs/s

Neither CodeSandbox SDK nor Upstash Box is in the CPU benchmark we use, so we cannot say which is faster. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15. 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 both at their default size with 100 starts at once (6 November 2026): a median of 2.34 s for Upstash Box and 11.76 s for CodeSandbox SDK. 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 Upstash Box 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 monthUpstash Box, 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 · Scale$21 · Pay as You Go$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$341 · Scale$21 · Pay as You Go$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 · Scale$900 · Pay as You Go · with limits$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 limits$306 · Pay as You Go$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 limits$1,822 · Pay as You Go$8,800 · $2000/mo · with limits

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

Upstash Box: A standard box is billed for the CPU it actually uses, at $0.10, $0.20 or $0.40 per active CPU hour by size, plus $0.10 per GB-month of storage, snapshots included. RAM is free, and Pay as You Go has no monthly fee. A keep-alive box costs a flat $8, $16 or $32 a month whether busy or not.

Upstash Box: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. Unused VM time expires at the end of the period. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs, busy or idle. The $20 plan includes 12 starts a minute and 200 a day; extra starts cost $0.03 to $0.07. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots above the included count and the optional credentials proxy still charge while it is stopped.

Limits in those scenarios

CodeSandbox SDK's Scale plan allows 250 VMs at once, so the user-sandboxes and 1,000-job scenarios need Enterprise, and each VM has a 20 GB disk. Upstash Box allows 1,000 boxes at once, but it does not document Docker inside a box, so the 50-agent scenario does not fit there. Neither publishes an egress price. boat's limit is starts: boat never queues a start, and on the $2,000 plan starts above 90 a minute are paid extras and starts above 270 a minute fail with 429. So 1,000 short jobs at once do not fit on boat. If a boat machine fails, you lose what was written after the last 1-minute snapshot.

ScenarioCodeSandbox SDKUpstash Boxboat
One coding agent, workdays
  • disk beyond 20 GiB: price unknown
  • egress price not published
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
One agent that never stops
  • disk beyond 20 GiB: price unknown
  • egress price not published
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
50 agents in parallel
  • egress price not published
  • not confirmed: Docker inside
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
Sandboxes for your users
  • Scale: max 250 concurrent
  • egress price not published
  • egress price not published
None for this scenario
1,000 short jobs at once
  • Scale: max 250 concurrent
  • egress price not published
  • egress price not published
  • 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

you need Docker inside each sandbox and want it to hibernate with its memory and wake on the next request, and you accept that Together calls this SDK deprecated.

  • Docker inside a VM. For agents that run databases or build images: each Firecracker VM has its own kernel, root and Docker, built from your Dockerfile.
  • Memory hibernation and forks. For work used in bursts: a sandbox sleeps with its memory and wakes or forks with processes still running.
  • Bigger machines on Enterprise. For very large single jobs: Enterprise offers sizes up to 64 cores and 128 GB.

Use Upstash Box when

your agents mostly wait, you want coding agents ready in each box, you need strict outbound rules, or you run big bursts in the US.

  • Coding agents built in. For teams that want Claude Code, Codex, OpenCode or Cursor ready in each box, with streaming, webhooks and scheduled prompts.
  • Idle costs no CPU. For agents that mostly wait: only used CPU is billed, RAM is free, and a request wakes a paused box.
  • Outbound rules and big bursts. For locked-down or bursty work: allow lists by domain or CIDR, and 1,000 boxes at once with no published start limit.

Where boat fits

boat fits agents that do long work on a whole machine. Each sandbox is a full VM with SSH, Docker, systemd and /dev/kvm, a 60 fps desktop and seven coding agents installed.

Docker and /dev/kvm in one machine

Upstash does not document Docker inside a box, so agents that start a database or build an image need another place to run them. CodeSandbox SDK runs Docker but does not document SSH or /dev/kvm. boat has Docker, SSH and /dev/kvm in every sandbox.

A desktop the agent can see

Upstash gives a managed Chromium with a view-only live view. On CodeSandbox SDK you install a desktop yourself. boat streams a full Linux desktop at 60 fps with computer-use tools, so an agent can click desktop apps and a human can watch.

boat's own limits

boat bills its full size while it runs, busy or idle, so a mostly idle Upstash box can cost less. boat has no wake on request, no memory snapshot, no outbound allowlist and no US region. Starts are capped per plan.

Use boat when your agents need a whole machine for hours: Docker, /dev/kvm, a built-in desktop, SSH, a 51 GB or bigger disk and up to 50 HTTPS URLs, with coding agents installed. Compare it one to one: boat vs CodeSandbox SDK and boat vs Upstash Box.

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 Upstash Box?

Usually not. For one coding agent on workdays, CodeSandbox SDK comes to $193 a month against $21 on Upstash, and for one agent that never stops, $341 against $21. For 1,000 short jobs at once, Upstash comes to $1,822 a month and fits, while CodeSandbox SDK's Scale plan allows 250 VMs at once. boat is $20 and $26 for the first two, and does not fit the 1,000-job burst because of its start limits.

Which is faster, CodeSandbox SDK or Upstash Box?

Neither is in the CPU benchmark we use, so we cannot say. For start time, ComputeSDK measured a median of 2.34 s for Upstash Box and 11.76 s for CodeSandbox SDK with 100 starts at once (6 November 2026). In StarSling's run of 3 October 2026, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB.

Can CodeSandbox SDK and Upstash Box run Docker?

CodeSandbox SDK runs Docker with root inside each Firecracker VM. Upstash Box does not document it: each box is itself a Docker container, and custom images are listed as coming soon. boat runs Docker and systemd in every sandbox.

Which has coding agents built in?

Upstash Box ships Claude Code, Codex, OpenCode and Cursor with run and stream APIs. On CodeSandbox SDK you install your own agent and run it through the commands API. boat preinstalls seven harnesses, driven from outside with a prompt, steer and events API.

Is CodeSandbox SDK still maintained?

CodeSandbox is now part of Together AI. Together's docs call this SDK 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. Self-serve sign-up still runs through CodeSandbox.

Can either one run a desktop for computer use?

Neither ships one. On CodeSandbox SDK you can add a VNC desktop to your own Dockerfile. Upstash gives a managed Chromium with CDP and a view-only live view, and its docs say there is no desktop or VNC. boat streams a full Linux desktop at 60 fps with computer-use tools.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons