Morph Cloud vs Together Code Sandbox
Both run agent code in VMs that can be saved with their memory. Morph Cloud is self-serve and branches a running machine in under 250 ms, while Together Code Sandbox must be enabled for your organization and snapshots a sandbox only when it ends.
The companies and products
Morph Cloud
Morph Cloud sells full virtual machines for AI agents that can be snapshotted, branched and restored with their memory, which it calls Infinibranch.
You get MorphVM instances as low-level building blocks and Devboxes as ready workspaces on top of them, with SSH, preview URLs and a tmux API for running coding agents you install yourself. Everything is billed in MCUs, where one MCU is 1 vCPU, 4 GB of RAM or 16 GB of disk for an hour. It is built for teams that fan agents out from one saved state, and it also sells managed GitHub Actions runners and a shared filesystem.
- Regions
- Not published
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 it must be enabled for your organization by Together. Together also sells Code Interpreter, a separate API that runs Python code in short sessions.
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. “16th cheapest of 345” means 15 of the other 344 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 | Morph Cloud: price rank | Together Code Sandbox: price rank | bochka: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Morph runs Docker in Docker and local Kubernetes as root; Together's new SDK runs commands as a normal user and does not document Docker inside, while bochka has Docker, systemd and /dev/kvm on every machine. | 198th of 367, with limits $2,288 a month | 65th of 367, with limits $528 a month | 3rd cheapest of 367 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An assistant that lives on its machine all month needs a machine that stays put; Morph keeps running until you stop it, Together has no idle detection or wake on request, and bochka adds agents, a desktop and a credentials proxy. | 235th of 366, with limits $3,014 a month | 152nd of 366, with limits $1,095 a month | 5th cheapest of 366 $657 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month Morph can pause a machine with its memory and wake it on the next request; Together's Code Interpreter runs Python in 60-minute sessions and keeps nothing after them. | 16th cheapest of 345 $154 a month | 326th of 345, with limits $2,190 a month | 186th of 345, 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 Morph can pause each user's machine and wake it on the next request; on Together every port is public and preview URLs are coming soon, while bochka gives each user token-protected HTTPS on up to 50 ports. | 12th cheapest of 361 $905 a month | 234th of 361, with limits $900 a month | Cheapest of 361 $209 a month |
| RL rollouts 1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month Both can start many copies from a saved memory state; Morph branches a running VM in under 250 ms, while Together saves the snapshot only when the parent sandbox ends. | 86th of 360, with limits $4,847 a month | 315th of 360, with limits $21,900 a month | 34th of 360, with limits $2,000 a month |
| Agent evals 250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month | 38th cheapest of 364 $675 a month | 258th of 364, with limits $450 a month | 10th cheapest of 364 $200 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Morph also sells managed GitHub Actions runners; Together has none, and on bochka you run your own runner inside a sandbox. | 39th cheapest of 377 $355 a month | 251st of 377, with limits $180 a month | 4th cheapest of 377 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB | 85th cheapest of 368 $116 a month | 210th of 368, with limits $22 a month | 18th cheapest of 368 $26 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month Morph has a browser-based remote desktop you set up yourself, Together has no desktop at all, and bochka streams a 60fps desktop with Chromium and a computer use API. | 182nd of 369, with limits $595 a month | 184th of 369, with limits $600 a month | 6th cheapest of 369 $200 a month |
| Browser-use agents 50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month On Morph and Together you install a headless browser in your own image; bochka has Chromium ready on its desktop. | 214th of 367, with limits $250 a month | 301st of 367, with limits $900 a month | 7th cheapest of 367 $200 a month |
| Scraping & bots (startup scale) 50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month | 239th of 346, with limits $234 a month | 219th of 346, with limits $180 a month | 6th cheapest of 346 $90 a month |
| Mass scraping & bots (undetectable) 1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month | 154th of 338, with limits $4,750 a month | 124th of 338, with limits $3,600 a month | 71st of 338, with limits $1,800 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month | 214th of 360, with limits $228 a month | 167th of 360, with limits $150 a month | 2nd cheapest of 360 $200 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month | Can't run it | Can't run it | Can't run it |
| macOS agents 5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month | Can't run it | Can't run it | Can't run it |
Key features
| Feature | Morph Cloud | Together Code Sandbox | bochka |
|---|---|---|---|
| Isolation | Full VM with its own kernel | A VM per sandbox on Together's infrastructure | Full VM with its own kernel on dedicated AMD Ryzen 9 9950X hosts |
| Getting started | Self-serve; the free Developer plan starts at 0 MCUs, so you buy pay-as-you-go credits | The SDK and CLI must be enabled for your organization by Together; only Code Interpreter is self-serve | Sign up and start a sandbox from the API, CLI or dashboard |
| Root, Docker and systemd | Yes, including Docker in Docker and local Kubernetes | Commands run as user 1000 by default, root on request; Docker inside not documented | Docker, systemd and root on every machine |
| Nested virtualization | Experimental | Not documented | Yes, /dev/kvm for Android emulators and VMs |
| Memory snapshots | Snapshot a running VM with its memory and branch it into many copies in under 250 ms | End a sandbox with a snapshot of its disk, or disk and memory; new sandboxes resume with processes running | No; disk is saved and resume boots the machine again |
| Fork a running machine | Yes, with its memory | No live fork: the parent stops, then you start copies from its snapshot | Yes, with its disk; the original keeps running |
| Idle and wake | A paused VM bills only its snapshot and resumes on the next HTTP request, SSH or exec call | Time to live counts from creation; no idle detection and no wake on request | Runs until you stop it or its time to live ends; started again by API |
| Saving work automatically | Saved when you pause or snapshot; a plain stop deletes the instance | Saved only when you end a sandbox with a snapshot | Disk saved every minute and on every stop; a stopped sandbox is free |
| Reaching the sandbox | Named HTTP services with optional API key auth; SSH through Morph's gateway; no raw TCP | All ports public; preview URLs coming soon; experimental inbound allowlist; no SSH | SSH, HTTPS URLs for up to 50 ports, token-protected by default, and raw TCP |
| Desktop and browser | Browser-based remote desktop; you install the browser and any computer use agent | None; headless command and file access only | 60fps Linux desktop with Chromium and a computer use API |
| Coding agents | You install the agent and drive it through a tmux API that sends keys and reads the screen | Run your own agent through execs; a Harbor guide for agent evals | Seven agents preinstalled, with a prompt, steer and events API |
| Keeping API keys out of the sandbox | Responses Proxy for model APIs; other secrets are handed to the machine | No credentials proxy documented | Credentials proxy for model providers and any HTTPS API; switch a credential to another account when credits run out |
| Guest systems | Linux, with experimental Windows and macOS (x86) | Linux | Linux |
| Hosted Python runner | None | Code Interpreter API runs Python in sessions billed per 60 minutes | No separate product; run code through exec in a sandbox |
Every feature Battleships tracks (43)
| Feature | Morph Cloud | Together Code Sandbox | bochka |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Not published | Yes |
| Nested virtualization | Yes | No | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Yes | Not published | Yes |
| Desktop GUI | Yes | No | Yes |
| Browser | No | No | Yes |
| Computer-use API | No | No | Yes |
| SSH | Yes | No | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | No | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | No | Yes |
| Memory fork | Yes | Yes | No |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | Yes | No | No |
| Wake on request | Yes | No | No |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No | No | Yes |
| Public IPv4 | No | No | No |
| Egress allowlist | No | No | No |
| Secret proxy | Yes | No | Yes |
| Secret proxy for any API | No | No | Yes |
| Preinstalled agents | No | No | Yes |
| Agent harness API | Yes | No | Yes |
| MCP server | No | Yes | No |
| GPU | No | No | No |
| Windows | Yes | No | No |
| Arm64 | No | No | No |
| Self-hosting | No | No | No |
| BYOC | No | No | No |
| Open source | No | No | No |
| Scoped API keys | Yes | Not published | Yes |
| Spend limits | Not published | Yes | Yes |
| Usage per sandbox (API) | Yes | Yes | Yes |
| Audit logs | Yes | Not published | No |
| SSO | Not published | Yes | No |
| SOC 2 | Not published | Yes | No |
| HIPAA | Not published | No | No |
| EU data residency | Not published | Not published | Yes |
| Zero data retention | Not published | Not published | Yes |
Performance
Neither Morph Cloud nor Together Code Sandbox has a comparable CPU measurement: neither was in the StarSling hpc-sandbox-benchmarks run. bochka did 26.69 runs per second on that Node.js test at 4 vCPU / 8 GB, on dedicated AMD Ryzen 9 9950X hosts. Morph's under 250 ms figure is snapshot restore time, not CPU speed.
Node.js build-and-test loop at 4 vCPU / 8 GB, higher is better. Measured with the open hpc-sandbox-benchmarks suite. Morph Cloud and Together Code Sandbox have no published run in this suite yet, so there is no like-for-like number to compare.
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.
| Scenario | Morph Cloud, a month | Together Code Sandbox, a month | bochka, 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 | $32 · Developer | $5 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $121 · Team | $22 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits | $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 | $1,459 · Scale | $264 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · 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 | $325 · Scale | $900 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits | $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 | $869 · Scale | $6,000 · Together pay-as-you-go (prepaid credits; Code Interpreter only) · with limits | $2,000 · $2000/mo · with limits |
Morph Cloud: Morph bills MCUs at $0.05 each: per hour, a machine uses the largest of its vCPUs, its RAM in 4 GiB steps or its disk in 16 GiB steps. Team ($40 a month) and Scale ($250 a month) are prepaid MCU bundles at a discount, and a paused VM bills only its snapshot.
Together Code Sandbox: Together lists Code Sandbox at $0.0446 per vCPU-hour and $0.0149 per GiB-hour, but the VMs must be enabled for your organization, so the table prices Code Interpreter: $0.03 per 60-minute session from prepaid credits. Code Interpreter runs only Python and keeps no disk, so it does not fit these scenarios.
Together Code Sandbox: Plans start at $20 a month, and the whole fee is usage credit. You pay per second while a sandbox runs, and a stopped sandbox costs nothing and keeps its disk.
Limits in those scenarios
The Together column is Code Interpreter, so its limits decide every row: sessions last 60 minutes, nothing is kept, and the machine size is not published. Morph fits every scenario, but disk beyond 16 GiB per MCU raises its price and egress is not published; its Developer pool of 64 vCPU holds only 16 machines at 4 vCPU. On bochka the limit that bites is starts: 1,000 short jobs at once need more starts than even the $2,000 plan allows, so they queue, while Morph Scale fits.
| Scenario | Morph Cloud | Together Code Sandbox | bochka |
|---|---|---|---|
| One coding agent, workdays |
|
| None that bite |
| One agent that never stops |
|
| None that bite |
| 50 agents in parallel |
|
| None that bite |
| Sandboxes for your users |
|
| None that bite |
| 1,000 short jobs at once |
|
|
|
Which one should you use?
Use Morph Cloud when
you want to start today on full VMs that branch live with their memory, sleep between requests and wake on demand, or need experimental Windows and macOS guests.
- Live branching with memory. For agents that fan out from one running state: Morph copies a live VM with its memory in under 250 ms.
- Sleep and wake on request. For machines that sit idle between calls: a paused VM bills only its snapshot and wakes on the next request.
- Self-serve, with extras. You can start today, and Morph also sells managed GitHub Actions runners and a filesystem many machines share.
Use Together Code Sandbox when
you already run models on Together and want very light sandboxes you save with their memory when they end, or a simple Python runner billed per session.
- Sandboxes next to your models. If you already run inference or fine-tuning on Together, code execution and model calls share one account and API key.
- Very small machines and a Python runner. For many light jobs: sandboxes start at a tenth of a core, and Code Interpreter runs Python billed per session.
Where bochka fits
Morph and Together both hand you a VM and leave the agent, the browser and the key handling to you. If your agents need to arrive ready, with a coding agent you steer by API, a desktop, real keys kept outside and private hosting, look at bochka. It is self-serve like Morph, keeps your disk every minute, and lives in the EU.
Coding agents you drive from outside
On Morph you install the agent and drive it through tmux keystrokes; on Together you wire it through execs. Either way you build a harness that parses terminal output, while bochka ships seven agents with a prompt, steer and events API.
Real keys never enter the machine
Morph's Responses Proxy covers model APIs only, and Together documents no proxy, so keys for GitHub or Stripe sit inside a machine the agent controls. bochka's credentials proxy covers any HTTPS API.
A desktop and private hosting, ready
Morph has no built-in browser and no raw TCP; Together has no desktop and every port is public. bochka streams a 60fps desktop with Chromium and serves up to 50 ports over token-protected HTTPS, plus raw TCP.
Use bochka when your agents need to arrive ready: coding agents you prompt and steer by API, a 60fps desktop with Chromium, real keys kept outside the machine, disk saved every minute, and private hosting in the EU. Compare it one to one: bochka vs Morph Cloud and bochka vs Together Code Sandbox.
Questions people ask
Is Morph Cloud cheaper than Together Code Sandbox?
Together's only self-serve price is Code Interpreter, which does not fit these scenarios because sessions end after 60 minutes and keep no disk. Where both have a price, Together looks cheaper for long runs, $264 against $1,459 a month for 50 agents, but costs more at scale: $900 against $325 for sandboxes for your users, and $6,000 against $869 for 1,000 short jobs at once.
Which is faster, Morph Cloud or Together Code Sandbox?
There is no comparable CPU measurement for either one. bochka did 26.69 runs per second on the StarSling Node.js test at 4 vCPU / 8 GB. Morph restores a snapshot in under 250 ms, which is start time, not CPU speed.
Can Morph Cloud and Together Code Sandbox run Docker?
Morph runs Docker in Docker and local Kubernetes as root. Together builds sandboxes from Docker images, but its new SDK runs commands as user 1000 by default and does not document Docker inside a sandbox. bochka runs Docker, systemd and root on every machine, with /dev/kvm for emulators.
Can I use Together Code Sandbox without contacting Together?
Not the VM product: the together-sandbox SDK and CLI must be enabled for your organization. Code Interpreter is self-serve from prepaid credits. Morph and bochka both let you sign up and start a machine yourself.
Which one can branch a running VM with its memory?
Morph can, in under 250 ms, and the original keeps running. Together saves memory only when a sandbox ends, then starts copies from that snapshot. bochka forks a running sandbox with its disk, not its memory, so the copy boots fresh.
Is bochka SOC 2 compliant?
SOC 2 is in progress. We're open about where we stand: live status at status.bochka.xyz and our data retention policy at docs.bochka.xyz/data-retention.
Try bochka
Install the CLI, then run bochka new.
Product preview