Together Code Sandbox vs Upstash Box

Together Code Sandbox starts VMs from Docker-image snapshots and can save their memory when they end. Together must enable it for your organization. Upstash Box is a self-serve container with a coding agent built in. It bills only busy CPU, pauses when idle and wakes on the next request.

The companies and products

Together Code Sandbox

Together AI is a cloud for running and training AI models, and Code Sandbox is its product for running code in isolated VMs.

You build a snapshot from a Docker image or Dockerfile on Together's builder, then start sandboxes from it and run commands and file operations through the together-sandbox SDK or CLI. When a sandbox ends you can save its disk, and its memory too, as a new snapshot to start more sandboxes from. It is aimed at model-generated code, agent tool calls and reinforcement learning rollouts, and Together must enable it for your organization. The pricing page also lists Code Interpreter at $0.03 per 60-minute session.

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. “67th cheapest of 365” means 66 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 workloadTogether Code Sandbox: 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. Together does not document Docker inside a sandbox. Each Upstash box is itself a Docker container, and Upstash does not document Docker inside it. boat runs Docker, root and /dev/kvm on every sandbox.
67th of 365, with limits
$528 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
Upstash can keep an agent on all month in a keep-alive box at a flat monthly price. A Together sandbox runs until you end it or its time to live ends, with no idle detection. boat gives the agent a full VM with systemd and a desktop, billed per second while it runs.
107th of 361, with limits
$1,095 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
Upstash fits short code runs well: an idle box costs no CPU, and its EphemeralBox deletes itself after at most 3 days. Together's pricing page lists Code Interpreter at $0.03 per 60-minute session. On boat, each create counts as a start against the plan's start limits.
318th of 336, with limits
$2,190 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 wakes a user's paused box on the next request. boat gives each user a full VM with token-protected HTTPS URLs, within its start limits. On Together every port URL is public unless you set an experimental access policy.
231st of 349, with limits
$900 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
Together can save a sandbox with its memory and start many copies with processes running, which suits rollouts from one warm state. Together must enable the VM product first. Upstash snapshots a running box and starts many new boxes from it.
309th of 349, with limits
$21,900 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
260th of 359, with limits
$450 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
CI jobs that build containers or Android apps need Docker and /dev/kvm. boat has both on every sandbox. Neither Together nor Upstash documents them inside a sandbox.
253rd of 374, with limits
$180 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
An Upstash keep-alive box is a light dev box at a flat $16 a month for 4 vCPU / 8 GB, with up to 30 GB of disk. boat's is a full VM with Docker, root and a 51 GB disk at the default size, billed per second while it runs. The tables price Together with Code Interpreter, which is not a dev box.
226th of 371, with limits
$22 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
Computer-use agents need a screen to look at and click. Together ships no browser or desktop. Upstash runs Chromium on a virtual display with a view-only live view, and has no desktop or VNC. boat streams a full Linux desktop at 60fps.
105th of 367, with limits
$600 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
195th of 356, with limits
$900 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
181st of 343, with limits
$180 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
126th of 327, with limits
$3,600 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
95th of 351, with limits
$150 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

FeatureTogether Code SandboxUpstash Boxboat
IsolationA VM per sandbox on Together's infrastructureA Docker container per box on AWSFull VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Getting startedThe SDK and CLI must be enabled for your organization by TogetherSelf-serve, with a Free plan and Pay as You GoSign up with a card (7-day trial), then start a sandbox from the API, CLI or dashboard
Machine size0.1 to 16 cores, 1 to 8 GB of memory per coreSmall 2 vCPU / 4 GB, Medium 4 vCPU / 8 GB, Large 8 vCPU / 16 GB on self-serve plans; custom sizes on Enterprise2, 4, 8 or 16 vCPU at 2 GB per vCPU; 16 vCPU needs the $100 plan or higher
DiskDisk size is not configurable10, 20 or 30 GB by size, billed per GB-month; Medium is 20 GB in the docs and 30 GB in the pricing table51 GB at the default 4 vCPU / 8 GB size, 51 to 251 GB by size; disk is fixed per size
Docker, root and systemdCommands run as user 1000 by default, root per exec on request; Docker inside a sandbox is not documentedNot documented; the box is itself a Docker container, and custom images are listed as coming soonDocker with Compose, systemd and root on every sandbox
Nested virtualizationNot documentedNot documented; boxes are containersYes, /dev/kvm for Android emulators and VMs
Saving stateEnd a sandbox with a snapshot of its disk, or disk and memory; a new sandbox from a memory snapshot resumes with its processes 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; memory is not saved, so a resume is like a reboot; disk kept at least 14 days
ForkThe parent stops first, then you start many sandboxes from its snapshot, with memory if you askSnapshot a running box and start many new boxes from itFork a running sandbox from its last 1-minute disk snapshot; the original keeps running
Idle and wakeTime to live counts from creation; no idle detection and no wake on requestNo CPU charge while idle; a request to a public URL resumes a paused boxFull rate while running, busy or idle; auto-stop defaults to 1 hour and does not watch for idle; started again by API
Inbound accessA URL per port, open to everyone by default; an experimental policy limits access by IP or requires a tokenHTTPS URL per port, public unless you add a token or basic auth; SSH through a gateway; no raw TCP documentedUp to 50 HTTPS URLs, token-protected by default; SSH; raw ports over public IPv6
Outbound rulesNo egress allowlist documentedAllow all, deny all, or allow and deny by domain and CIDR, changeable on a running boxOpen internet, no provider-side allowlist
Desktop and browserNo built-in desktop or stream; install a browser or virtual display in your own imageManaged Chromium on a virtual display with AI page actions, CDP, recordings and a view-only live stream; no desktop or VNCLinux desktop and Chrome streamed at 1920x1080, 60fps, with computer-use tools
Coding agentsYou install your agent in your image and run it through execs; a Harbor guide for agent evalsClaude 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 sandboxNo credentials proxy documentedHost proxy injects headers into outbound HTTPS on port 443 for any host; set when the box is createdOptional AI credentials proxy ($1 a day plus $1 per 1,000 requests) for supported model providers; other secrets still enter the sandbox
RegionsNot publishedAWS us-east-1; custom regions on EnterpriseGermany, Finland and France; you cannot pick a region; no US or Asia region
Every feature Battleships tracks (43)
FeatureTogether Code SandboxUpstash Boxboat
Full VM (own kernel)YesNo documented wayYes
Docker insideNot publishedNot publishedYes
Nested virtualizationNo documented wayNo documented wayYes
RootYesNot publishedYes
SystemdNot publishedNot publishedYes
Desktop GUINot publishedNo documented wayYes
BrowserNot publishedYesYes
Computer-use APINot publishedNo documented wayYes
SSHNo documented wayYesYes
Persistent diskWith your own setupYesYes
Pause/resumeYesYesYes
Automatic snapshotsNo documented wayNo documented wayYes
Fork/cloneYesYesYes
Live fork (no pause)No documented wayYesYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopNo documented wayYesNo documented way
Wake on requestNo documented wayYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress 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 serverYesYesNo 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 limitsYesNot publishedYes
Usage per sandbox (API)YesYesYes
Audit logsNot publishedNot publishedNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesYesNo documented way
HIPAANo documented wayNo documented wayNo documented way
EU data residencyNot publishedNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

Together Code SandboxNot measured
Upstash BoxNot measured
boat28.06 runs/s

Together Code Sandbox and Upstash Box are not in StarSling's CPU benchmark, 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. ComputeSDK measured Upstash Box at its default size: a median of 2.34 s to the first command with 100 at once (2026-11-06), and 445 ms one at a time (2026-08-07). boat and Together 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. Together Code Sandbox 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.

ScenarioTogether Code Sandbox, 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
$5 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits$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
$22 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits$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
$264 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits$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
$900 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · 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
$6,000 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits$1,822 · Pay as You Go$8,800 · $2000/mo · with limits

Together Code Sandbox: Together lists Code Sandbox at $0.0446 per vCPU-hour and $0.0149 per GiB-hour, about $0.30 an hour at 4 vCPU / 8 GB, from prepaid credits, once Together enables it for your organization. Billing granularity, snapshot storage and egress prices are not published. The pricing page also lists Code Interpreter at $0.03 per 60-minute session; the scenario tables use that line because Code Sandbox needs enablement.

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 for Small, Medium and Large, 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 it is busy or not. The Free plan stops at 5 CPU hours a month.

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. A running sandbox bills per second at full rate, busy or idle: $0.036 an hour for 4 vCPU / 8 GB. 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 AI credentials proxy still charge while sandboxes are stopped. The $20 plan includes 12 starts a minute and 200 a day; extra starts cost $0.03 to $0.07. A card is required, also for the 7-day trial.

Limits in those scenarios

The tables price Together with the Code Interpreter line ($0.03 per 60-minute session), because Code Sandbox needs Together to enable it. Those sessions last 60 minutes and their machine size is not published, so that line fits none of the five scenarios. Upstash fits four of them. It does not fit 50 agents in parallel, because Upstash does not document Docker inside a box. Its egress price is not published, and keep-alive boxes bill every month whether used or not. boat fits four too. For 1,000 short jobs at once, even the $2,000 plan includes 90 starts a minute and 2,400 a day; extra starts cost $0.03 to $0.07, and starts above 270 a minute fail with 429. boat never queues a start, so the burst does not fit boat.

ScenarioTogether Code SandboxUpstash Boxboat
One coding agent, workdays
  • Together pay-as-you-go (prepaid credits; Code Interpreter only): sessions capped at 1 h
  • not confirmed: persistent disk
  • machine size not published
  • different kind of product: code interpreter
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
One agent that never stops
  • Together pay-as-you-go (prepaid credits; Code Interpreter only): sessions capped at 1 h
  • not confirmed: persistent disk
  • machine size not published
  • different kind of product: code interpreter
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
50 agents in parallel
  • Together pay-as-you-go (prepaid credits; Code Interpreter only): sessions capped at 1 h
  • not confirmed: persistent disk
  • machine size not published
  • different kind of product: code interpreter
  • 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
  • machine size not published
  • different kind of product: code interpreter
  • machine size per session not published
  • egress price not published
  • egress price not published
None for this scenario
1,000 short jobs at once
  • machine size not published
  • different kind of product: code interpreter
  • machine size per session not published
  • 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 Together Code Sandbox when

you already run models on Together, can get the VMs enabled, and want light sandboxes, from a tenth of a core, that you save with their memory and branch from.

  • Memory snapshots to branch from. Useful for rollouts and test variants: save a sandbox with its memory and start many copies with processes still running.
  • Sandboxes next to your models. Handy if you already run inference or fine-tuning on Together: sandboxes and models share one account.
  • Sizes cut to the job. Good for many light jobs: sandboxes start at a tenth of a core, priced per vCPU-hour and GiB-hour.

Use Upstash Box when

your agents mostly wait, need to wake on an incoming request, must stay inside a strict outbound allowlist, start in big bursts, or must run in the US, and you want to sign up and start today.

  • Idle costs no CPU, and a request wakes the box. Good for agents that wait a lot: an idle box costs no CPU, and a request to its URL wakes it.
  • Self-serve, with agents built in. Sign up and run Claude Code, Codex, OpenCode or Cursor in up to 1,000 boxes at once on Pay as You Go.
  • Outbound network rules. Useful when an agent may only reach a short list of domains or IP ranges, changeable on a running box.

Where boat fits

Look at boat if your agents do real work for hours, with installs, builds, Docker, emulators, a desktop and servers other people reach. Each sandbox is a full VM with the agent already installed. boat needs a card, bills a running sandbox at full rate, busy or idle, has no region choice and caps starts per plan.

A whole machine with Docker and /dev/kvm

Together runs commands as a normal user by default and documents neither Docker inside nor nested virtualization. An Upstash box is itself a container, and Upstash does not document Docker inside it, so the 50-agent scenario does not fit there. boat runs Docker, systemd and /dev/kvm on every sandbox.

Hosting that is private by default

Together port URLs are public unless you set an experimental policy. Upstash URLs are public until you add a token or basic auth, and Upstash documents no raw TCP. boat token-protects HTTPS on up to 50 ports and serves raw ports over IPv6.

A desktop the agent can see

Together ships no browser or desktop. Upstash runs Chromium on a virtual display that a person can only watch, with no desktop or VNC. boat streams a full Linux desktop at 60fps with Chrome and computer-use tools.

Use boat when your agents need a full VM: Docker, emulators, a desktop, a disk above 30 GB, private hosting and services that keep running once auto-stop is off. Compare it one to one: boat vs Together Code Sandbox 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 Together Code Sandbox cheaper than Upstash Box?

The tables price Together with Code Interpreter, which fits none of these scenarios. On that line it costs more where both are priced: $900 against $306 a month for sandboxes for your users, and $6,000 against $1,822 for 1,000 short jobs at once. Code Sandbox itself lists about $0.30 an hour at 4 vCPU / 8 GB. Upstash also fits one agent always on for $21 a month. boat comes to $26 and $200 for the agent and the user sandboxes, and does not fit the burst.

Which is faster, Together Code Sandbox or Upstash Box?

Neither is in StarSling's CPU benchmark, so we cannot say. ComputeSDK measured Upstash Box at 445 ms to the first command one at a time (2026-08-07). 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, on an AMD Ryzen 9 9950X host.

Can Together Code Sandbox or Upstash Box run Docker?

Neither documents it. Together builds sandboxes from Docker images, but its SDK does not document Docker inside a sandbox. Each Upstash box is itself a Docker container, and Upstash does not document running Docker inside it. boat runs Docker, systemd and root on every sandbox.

Can I sign up for Together Code Sandbox today?

Not on your own. The SDK and CLI must be enabled for your organization, so you ask Together for access. Upstash Box is self-serve with a Free plan. boat is self-serve with a card, and the 7-day trial needs a card too.

Which one wakes up when a request comes in?

Upstash Box does: a paused box resumes when a request reaches its public URL. Together sandboxes have no idle detection or wake on request. boat sandboxes are started again by API, and a resume is like a reboot.

Is boat SOC 2 compliant?

SOC 2 is in progress at boat, so there is no SOC 2 report today. Upstash's trust center lists SOC 2 Type II for the company, and Together's trust center lists a SOC 2 Type 2 report. boat's live status is at status.ascii.dev and its data retention policy at docs.boat.dev/data-retention.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons