Runloop vs Morph Cloud
Runloop runs devboxes in micro-VMs with hostname allowlists, Dockerfile builds, arm64 and deploys into your own cloud. Morph Cloud gives each agent a full VM that can pause, wake on a request and branch into many copies with its memory.
The companies and products
Runloop
Runloop is a US platform of sandboxes, called devboxes, for building, running and testing AI coding agents.
You get Linux devboxes built from Dockerfile-style blueprints, disk snapshots, HTTPS tunnels, agent gateways that hide API keys, and Axons, event streams that drive agents such as Claude Code. Each devbox runs in a micro-VM on Runloop's own bare-metal hypervisor, with a container layer inside. It is built for teams shipping coding agents, plus evaluation and RL fine-tuning work on the Enterprise plan.
- Compliance
- SOC 2 Type 2
- Architectures
- x86_64 and arm64 base blueprints
- Own-cloud deploy
- Deploy to VPC on AWS, GCP and Azure (Enterprise)
- Regions
- Not documented or selectable
- Company
- Runloop AI, Inc.
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
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. “20th cheapest of 367” means 19 of the other 366 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 | Runloop: price rank | Morph Cloud: price rank | bochka: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Runloop is a full match for a software factory and Morph Cloud a compromise; bochka adds /dev/kvm for Android emulators and keeps the disk on every plan. | 20th cheapest of 367 $8,152 a month | 198th of 367, with limits $2,288 a month | 3rd cheapest of 367 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 32nd cheapest of 366 $10,194 a month | 235th of 366, with limits $3,014 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 Cloud ranks 16th for short code runs, ahead of Runloop, because a paused VM keeps its memory, bills only its snapshot and wakes on the next request. | 44th cheapest of 345 $525 a month | 16th cheapest of 345 $154 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 Both fit sandboxes for your users; Morph can pause each user's machine and wake it on demand, and bochka ranks 1st with token-protected HTTPS on up to 50 ports. | 26th cheapest of 361 $3,301 a month | 12th cheapest of 361 $905 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 Runloop ranks 4th for RL rollouts and is a full match, while Morph Cloud is a compromise here even though its memory branching suits rollouts that start from one running state. | 4th cheapest of 360 $15,922 a month | 86th of 360, with limits $4,847 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 | 81st cheapest of 364 $2,562 a month | 38th cheapest of 364 $675 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; bochka's faster CPUs finish builds sooner, and Docker works inside all three. | 121st cheapest of 377 $1,554 a month | 39th cheapest of 377 $355 a month | 4th cheapest of 377 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Both can run a box all month: Runloop with an idle policy in place of its 48-hour lifetime, Morph because an instance never expires unless you set a TTL. | 113th cheapest of 368 $410 a month | 85th cheapest of 368 $116 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 Runloop ships a desktop and a browser an agent can control, while on Morph you install those yourself; bochka streams its desktop at 60fps with Chromium. | 39th cheapest of 369 $2,306 a month | 182nd of 369, with limits $595 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 | 40th cheapest of 367 $1,153 a month | 214th of 367, with limits $250 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 | 68th cheapest of 346 $781 a month | 239th of 346, with limits $234 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 | 266th of 338, with limits $15,611 a month | 154th of 338, with limits $4,750 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 Runloop can lock each devbox to a hostname allowlist, which Morph does not document; bochka gives each sandbox a full kernel with nested virtualization. | 10th cheapest of 360 $770 a month | 214th of 360, with limits $228 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 | Runloop | Morph Cloud | bochka |
|---|---|---|---|
| Isolation | Micro-VM on a custom bare-metal hypervisor, plus a container layer | Full VM with its own kernel | Full VM with its own kernel on dedicated AMD Ryzen 9 9950X hosts |
| Nested virtualization | Not documented; Docker-in-Docker blueprints only | Experimental | Yes: /dev/kvm, Android emulators and VMs inside |
| Docker inside | Yes, on the dnd blueprints, as root | Yes, including Docker in Docker and local Kubernetes | Yes, with root and systemd |
| Images and guest systems | Blueprints built from Dockerfiles; Linux on x86_64 and arm64 | Linux, with experimental Windows and macOS (x86) guests | Templates from named snapshots; Linux on x86_64 |
| Fork a running machine | Disk snapshots you can start new devboxes from | Branch a running VM with its memory into many copies in under 250 ms | Fork a running sandbox with its disk |
| Sleep when idle and wake | Suspend after idle, wake on an HTTP request to the tunnel (Pro plan) | Pause with memory, wake on the next HTTP request, SSH or exec call; a paused VM bills only its snapshot | No idle timer; a stopped sandbox is started by API |
| Keeping files | Kept through suspend (Pro) or manual disk snapshots; shutdown ends the devbox | Saved when you pause or snapshot; a plain stop deletes the instance | Disk saved every minute and on every stop, on every plan; a stopped sandbox is free |
| Long runs | Lifetime 1 hour by default, 48 hours max; an idle policy replaces it | No expiry unless you set a TTL | No session cap on paid plans; default TTL 1 hour, changeable |
| Egress rules | Hostname allowlist with wildcards, or block all | No provider-side allowlist documented | Open internet, no provider-side allowlist |
| Inbound access | One HTTPS tunnel per devbox, open or bearer token; SSH through a TLS proxy; no public IP | Named HTTP services with optional API key auth; SSH through Morph's gateway; no raw TCP | HTTPS URLs for up to 50 ports, token-protected by default; raw TCP; dedicated IPv6 or IPv4 |
| Keeping API keys out of the sandbox | Agent gateways for any API endpoint with bearer, header or basic auth | Responses Proxy for model APIs only; other secrets are handed to the machine | Credentials proxy for model providers and any HTTPS API; switch a credential to another account when credits run out |
| Coding agents | Claude Code, Codex, OpenCode, Gemini CLI, DeepAgents, driven through Axons and Broker | You install the agent, then drive it through a tmux API that sends keys and reads the screen | Seven agents preinstalled, with a prompt, steer and events API |
| Desktop and browser | Desktop and browser an agent can control | Browser-based remote desktop; you install the browser and any computer use agent yourself | 60fps Linux desktop with Chromium and a computer use API, embeddable in your app |
| Where it runs | Regions not documented; Deploy to VPC on AWS, GCP or Azure (Enterprise) | Regions not published; hosted only | EU only (Germany, Finland, France), EU data residency |
Every feature Battleships tracks (43)
| Feature | Runloop | Morph Cloud | bochka |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | No | Yes | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Yes | Yes |
| Desktop GUI | Yes | Yes | Yes |
| Browser | Yes | No | Yes |
| Computer-use API | Yes | No | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | Yes | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Yes | Yes |
| Memory fork | No | Yes | No |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | Yes | Yes | No |
| Wake on request | Yes | Yes | No |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No | No | Yes |
| Public IPv4 | No | No | No |
| Egress allowlist | Yes | No | No |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | Yes | No | Yes |
| Preinstalled agents | Yes | No | Yes |
| Agent harness API | Yes | Yes | Yes |
| MCP server | Yes | No | No |
| GPU | No | No | No |
| Windows | No | Yes | No |
| Arm64 | Yes | No | No |
| Self-hosting | No | No | No |
| BYOC | Yes | No | No |
| Open source | No | No | No |
| Scoped API keys | Yes | Yes | Yes |
| Spend limits | Not published | Not published | Yes |
| Usage per sandbox (API) | No | Yes | Yes |
| Audit logs | Not published | Yes | No |
| SSO | Yes | Not published | No |
| SOC 2 | Yes | Not published | No |
| HIPAA | Not published | Not published | No |
| EU data residency | No | Not published | Yes |
| Zero data retention | Not published | Not published | Yes |
Performance
On the hpc-sandbox-benchmarks Node.js build-and-test loop at 4 vCPU / 8 GB (run 36498291449, 2026-09-29), bochka scored 26.69 runs a second and Runloop 8.29, about 3.2 times apart. Morph Cloud is not in that run, so there is no comparable CPU measurement for it. 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 has 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 | Runloop, a month | Morph Cloud, 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 | $113 · Basic | $32 · Developer | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $429 · Basic | $121 · Team | $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 | $5,268 · Basic | $1,459 · Scale | $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 | $1,441 · Basic | $325 · Scale | $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 | $3,184 · Basic | $869 · Scale | $2,000 · $2000/mo · with limits |
Runloop: Runloop bills per second for the CPU and memory you allocate, while a devbox is starting, running, suspending or resuming, and bills its disk for the devbox's whole life. Basic has no plan fee; Pro adds $250 a month that is not usage credit and unlocks suspend and resume.
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.
Morph Cloud: Plans start at $20 a month and the whole fee is usage credit, billed per second while a sandbox runs. A stopped sandbox costs nothing and keeps its disk.
Limits in those scenarios
Runloop publishes no concurrency cap for paid plans and no egress price, its disk tops out at 64 GiB, and its fixed lifetime ends at 48 hours unless an idle policy replaces it. Morph prices each machine by its largest resource, so disk beyond 16 GiB per vCPU raises the bill, and its account pools are small on Developer: 64 vCPU holds only 16 machines at 4 vCPU. Neither publishes egress prices. bochka's limit that bites is start rate: for 1,000 short jobs at once, both Runloop and Morph fit while bochka's $2,000 plan queues the starts.
| Scenario | Runloop | Morph Cloud | 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 Runloop when
sandboxes must reach only listed hosts, you build images from Dockerfiles or for arm64, or you want devboxes inside your own AWS, GCP or Azure account.
- Lock down the network. Useful if a sandbox must only reach a fixed list of hosts: Runloop allows listed hostnames, with wildcards, or blocks everything.
- Run it in your own cloud. On the Enterprise plan, Runloop can run devboxes inside your own AWS, GCP or Azure account.
- Dockerfile builds and arm64. Useful if your images live in Dockerfiles or you build for arm64: Runloop blueprints build from Dockerfiles on x86_64 or arm64.
Use Morph Cloud when
your agents branch from one running state with its memory, sleep between requests and wake on demand, or need experimental Windows and macOS guests.
- Branch a running VM with its memory. Useful when many agents fan out from one running state: Morph copies a VM with its memory in under 250 ms.
- Pause cheaply and wake on demand. A paused Morph VM keeps every process, bills only its snapshot, and wakes on the next HTTP request, SSH or exec call.
- Windows and macOS guests. Morph lists experimental Windows and macOS (x86) guests for agents that must work in those systems.
Where bochka fits
If your agents spend hours installing, building, testing and running Docker or emulators, look at bochka. Each sandbox is a full VM with /dev/kvm on fast CPUs, saves its disk every minute on every plan, and comes with coding agents, a 60fps desktop and hosting on many ports. Pick Runloop or Morph Cloud instead when you need egress allowlists, your own cloud or memory branching.
A full machine, open to the outside
Runloop does not document nested virtualization and Morph lists it as experimental, so an Android emulator or a VM may not start. Neither offers raw TCP, so a database or game server that is not HTTP has no way in.
Work saved without asking
On Runloop a devbox is gone after shutdown unless you pay for Pro's suspend or write snapshot code. On Morph a plain stop deletes the instance. bochka saves the disk every minute and on every stop.
Faster CPUs for builds and tests
On the same Node.js build-and-test benchmark, bochka ran 26.69 loops a second and Runloop 8.29, so each install and test run waits about three times longer there. Morph has no comparable measurement.
Use bochka when your agents do real work for hours: builds, tests, Docker and emulators on fast CPUs, files saved every minute, coding agents and a desktop ready inside, and hosting on many ports in the EU. Compare it one to one: bochka vs Runloop and bochka vs Morph Cloud.
Questions people ask
Is Runloop cheaper than Morph Cloud?
No, Morph costs less in every scenario on this page. One agent that never stops costs $429 a month on Runloop and $121 on Morph, and 50 agents in parallel cost $5,268 versus $1,459. bochka comes in at $26 and $317 for the same two.
Which is faster, Runloop or Morph Cloud?
We can only compare CPU speed where both were measured. Runloop scored 8.29 runs a second on the Node.js build-and-test benchmark and bochka 26.69; Morph Cloud is not in that run. Morph restores a snapshot in under 250 ms, which is start time, not CPU speed.
Can Runloop and Morph Cloud run Docker?
Yes. Runloop runs Docker as root on its Docker-in-Docker blueprints, and Morph runs Docker, Docker in Docker and local Kubernetes inside a full VM. bochka runs Docker with root and systemd too.
Can I run Android emulators or VMs inside them?
Runloop does not document nested virtualization or /dev/kvm, and Morph lists nested virtualization as experimental. bochka exposes /dev/kvm, so Android emulators and VMs run inside a sandbox.
Can I branch a running machine with its memory?
On Morph, yes: Infinibranch copies a running VM with its memory, so every copy continues with its processes running. Runloop works from disk snapshots, and bochka forks a running sandbox with its disk, so those copies boot fresh.
Can I limit which websites a sandbox can reach?
On Runloop, yes: network policies allow only the hostnames you list, with wildcards, or block all traffic. Morph does not document an egress allowlist, and bochka has none, so on those you filter inside the VM.
Try bochka
Install the CLI, then run bochka new.
Product preview