Morph Cloud vs Namespace
Morph Cloud sells full VMs for agents that can be snapshotted and branched with their memory, and wake on the next request. Namespace is mainly a CI and build platform whose Devboxes run Linux, macOS and Windows but shut down after 4 to 24 hours.
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
Namespace
Namespace is a dev platform for fast builds, tests and coding environments: CI runners, build caches and Devboxes, on its own hardware.
Most of Namespace is CI: a faster drop-in for GitHub Actions runners, with Docker, Bazel, Turborepo and Nix caching. Its Devboxes are remote Linux and macOS machines with persistent storage, made for people and AI coding agents, and they also host sessions for Claude Managed Agents, Cursor Cloud Agents and Devin. It is a different kind of product from bochka, so this page compares the part where they overlap: a machine an agent works on.
- Products
- GitHub Actions runners, Docker, Bazel, Turborepo and Nix caching, Devboxes, and a compute API
- Hardware
- Its own hardware in its own racks: AMD EPYC for Linux and Windows, Apple M4 Pro or M5 Max for macOS
- Linux Devboxes
- Run from a container image you choose and include Docker; the docs do not say whether each one has its own kernel
- Funding
- Announced a $42M Series B
- Compliance
- Trust center lists SOC 2 Type II
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 | Namespace: price rank | bochka: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Namespace ranks 39th and Morph Cloud 198th, both as a compromise; bochka ranks 3rd with Docker, /dev/kvm and coding agents preinstalled. | 198th of 367, with limits $2,288 a month | 39th of 367, with limits $3,495 a month | 3rd cheapest of 367 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB Both are a compromise for an assistant that never stops: Morph leaves you to install the agent and desktop, and a Namespace Devbox is shut down after at most 24 hours. | 235th of 366, with limits $3,014 a month | 303rd of 366, with limits $6,645 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 because a paused machine keeps its memory and bills only its snapshot, while Namespace is a compromise for short code runs. | 16th cheapest of 345 $154 a month | 247th of 345, with limits $250 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 Cloud ranks 12th and fits, since each user's machine can pause and wake on the next request, while Namespace ranks 284th; bochka ranks 1st with token-protected HTTPS on up to 50 ports. | 12th cheapest of 361 $905 a month | 284th of 361, with limits $2,068 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 Morph's memory branching suits rollouts that all start from one running state; Namespace has no fork at all. | 86th of 360, with limits $4,847 a month | 356th of 360, with limits $9,012 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 | 282nd of 364, with limits $1,043 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 Both fit: CI runners with build caches are Namespace's main product, and Morph also sells managed GitHub Actions runners from its MCU balance. | 39th cheapest of 377 $355 a month | 80th cheapest of 377 $765 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 | 126th of 368, with limits $168 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 Namespace's screenshot and click API works on macOS Devboxes only, and on Morph you install the desktop agent yourself; bochka ships a 60fps Linux desktop with Chromium. | 182nd of 369, with limits $595 a month | 67th of 369, with limits $982 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 | 214th of 367, with limits $250 a month | 285th of 367, with limits $789 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 | 259th of 346, with limits $332 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 | 226th of 338, with limits $9,012 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 | 242nd of 360, with limits $339 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 Only Namespace fits: it runs macOS on Apple Silicon, while Morph lists macOS (x86) as experimental and bochka has no macOS. | Can't run it | 6th cheapest of 36 $1,205 a month | Can't run it |
Key features
| Feature | Morph Cloud | Namespace | bochka |
|---|---|---|---|
| Isolation | Full VM with its own kernel | Linux Devboxes run from a container image on Namespace's own hardware; the docs do not say if each has its own kernel | Full VM with its own kernel on dedicated AMD Ryzen 9 9950X hosts |
| CPU speed (Node.js build-and-test, 4 vCPU / 8 GB) | Not measured | 21.79 runs/s | 26.69 runs/s |
| Docker and nested virtualization | Root and Docker, including Docker in Docker and local Kubernetes; nested virtualization is experimental | Docker in Linux Devboxes; /dev/kvm on Linux compute instances, not on macOS or Windows | Docker, root, systemd and /dev/kvm on every machine |
| How long a session can run | No provider limit; a machine runs until you stop it or its own TTL ends | Devboxes stop after 4, 5 or 24 hours by plan, raisable to 24 at most | No session cap on paid plans |
| Memory snapshots, fork and wake | Snapshot and branch a running VM with its memory in under 250 ms; a paused VM wakes on the next HTTP request, SSH or exec call | No fork; compute instances can suspend with RAM kept, and Devboxes start again when you connect | Fork a running sandbox with its disk; resume boots again from disk |
| Files after a stop | Saved when you pause or snapshot; a plain stop deletes the instance | A stopped Devbox keeps its storage, billed at $0.20 per GB-month used | Disk saved every minute and on every stop; a stopped sandbox costs nothing |
| Desktop and computer use | Browser-based remote desktop; you install the browser and any computer use agent yourself | Screenshot and click API on macOS Devboxes only; VNC and RDP for compute instances | 60fps Linux desktop with Chromium, computer use and browser control, embeddable stream |
| Coding agents | You install the agent, then drive it through a tmux API that sends keys and reads the screen | Hosts Claude Managed Agents, Cursor and Devin sessions run by those partners; an MCP server lets your agent create Devboxes | Seven agents preinstalled, including Claude Code and Codex, with a prompt, steer and events API |
| Keeping keys out of the sandbox | Responses Proxy for model APIs; other secrets are handed to the machine | Egress rules inject a header from Namespace Vault, resolved outside the workload | Credentials proxy for model providers and any HTTPS API; switch a credential to another account when credits run out |
| Reaching the sandbox | Named HTTP services with optional API key auth; SSH through Morph's gateway; no raw TCP | HTTPS URLs that need a Namespace login; TCP through a running CLI port-forward; no public IP | HTTPS URLs for up to 50 ports, token-protected by default; raw TCP; dedicated IPv6 or IPv4 |
| Outbound internet rules | Open internet; no provider-side domain allowlist documented | Egress policies per Devbox blueprint, runner or instance: block, advisory or allow by domain | Open internet on every plan; no provider-side allowlist |
| Operating systems | Linux, with experimental Windows and macOS (x86) | Linux, macOS on Apple Silicon, and Windows on Team plans and up | Linux only; Wine for Windows apps |
| Managed CI | GitHub Actions runners in three sizes, billed from the same MCU balance | Main product: drop-in GitHub Actions runners with Docker, Bazel, Turborepo and Nix caching | No managed runner; run your own runner inside a sandbox |
| Where data lives | Regions not published | Several regions; keeping every workload in one region needs the enterprise plan | EU only (Germany, Finland, France), with zero data retention |
Every feature Battleships tracks (43)
| Feature | Morph Cloud | Namespace | bochka |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Yes | Yes | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Yes | Not published | Yes |
| Desktop GUI | Yes | Yes | Yes |
| Browser | No | No | Yes |
| Computer-use API | No | Yes | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | Yes | Yes |
| Fork/clone | Yes | No | Yes |
| Live fork (no pause) | Yes | No | Yes |
| Memory fork | Yes | No | 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 | Yes | Yes |
| Public IPv4 | No | No | No |
| Egress allowlist | No | Yes | No |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | No | Yes | Yes |
| Preinstalled agents | No | Yes | Yes |
| Agent harness API | Yes | No | Yes |
| MCP server | No | Yes | No |
| GPU | No | No | No |
| Windows | Yes | Yes | No |
| Arm64 | No | Yes | 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 | No | Yes |
| Audit logs | Yes | Yes | No |
| SSO | Not published | Yes | No |
| SOC 2 | Not published | Yes | No |
| HIPAA | Not published | No | No |
| EU data residency | Not published | Yes | Yes |
| Zero data retention | Not published | Not published | Yes |
Performance
In StarSling's public run of 2026-09-29 at 4 vCPU / 8 GB, bochka did 26.69 Node.js build-and-test runs per second and Namespace did 21.79, so the same build takes about a fifth longer on Namespace. Morph Cloud is not in that run, so there is no comparable CPU measurement for it. Morph's under 250 ms figure is for restoring a snapshot, which measures start 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. Namespace measured on: Linux compute instance (unit-minutes, PAYG/overage $0.0015). 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 | Morph Cloud, a month | Namespace, 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 | $50 · Devbox (pay as you go) | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $121 · Team | $176 · Devbox (pay as you go) · 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 | $2,198 · Devbox (pay as you go) | $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 | $1,214 · Devbox (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 | $869 · Scale | $3,237 · Devbox (pay as you go) | $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 storage.
Namespace: Devboxes are billed in Devbox Minutes at $0.004 each, pay as you go on every plan; a 4 vCPU / 8 GB Devbox uses one a minute. The minutes in the Team ($100) and Business ($250) plans cover runners and instances, not Devboxes, and stored files cost $0.20 per GB-month.
Namespace: Plans start at $20 a month, and the whole fee is usage credit spent per second while a sandbox runs. A stopped sandbox costs nothing and keeps its disk.
Limits in those scenarios
On Namespace the limit that bites is time: a Devbox is shut down after 4, 5 or 24 hours by plan, so the agent that never stops restarts at least once a day. On Morph it is disk and pool size: more than 16 GiB of disk per vCPU raises the MCU count, and the Developer pool of 64 vCPU holds only 16 machines at 4 vCPU. Neither publishes an egress price. Both fit 1,000 short jobs at once, while bochka's $2,000 plan queues those starts.
| Scenario | Morph Cloud | Namespace | 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
your agents branch from one running state with its memory, sleep between requests and wake on demand, or need to run for days on Linux.
- Branch a running machine with its memory. For agents that fan out from one running state: Morph copies a live VM with its memory into many branches in under 250 ms.
- Sleep cheaply, wake on request. For machines that sit idle between calls: a paused VM bills only its snapshot and wakes on the next HTTP request, SSH or exec call.
- No clock on a session. For agents that run for days: a Morph machine keeps running until you stop it, with no provider time limit.
Use Namespace when
you need macOS or Windows machines, faster GitHub Actions runners with build caches, or outbound traffic limited to chosen domains.
- macOS and Windows machines. For agents that build iOS or Mac apps or test on Windows: Namespace runs macOS on Apple Silicon and Windows on Team plans.
- Fast CI with build caches. For teams that want quicker GitHub Actions: Namespace is a drop-in runner with Docker, Bazel, Turborepo and Nix caching.
- Egress rules by domain. For agents that must reach only chosen domains: Namespace can block all other outbound traffic per Devbox blueprint, runner or instance.
Where bochka fits
If what you are really running is coding or computer use agents on Linux, look at bochka. Morph gives you a strong VM but leaves the agent, the desktop and the browser to you, and Namespace is a CI platform whose Devboxes stop within a day. bochka is a full VM on dedicated AMD Ryzen 9 9950X hosts with the agents, a 60fps desktop and hosting already inside.
Coding agents you drive from outside
On Morph you install the agent and drive it by sending keystrokes to tmux and reading the screen. On Namespace a partner service runs the agent, or you write that harness yourself. bochka ships seven agents with a prompt, steer and events API.
A Linux desktop ready for computer use
Morph has remote desktop access, but you build the browser and the click loop yourself. Namespace's screenshot and click API rejects Linux Devboxes, so you pay for macOS minutes or set up VNC. bochka streams a 60fps desktop with Chromium.
Work saved every minute, no session clock
A plain stop deletes a Morph instance unless you paused or snapshotted it first, and a Namespace Devbox is shut down after at most 24 hours mid-task. bochka saves the disk every minute, a stopped sandbox is free, and paid plans have no session cap.
Use bochka when your agents work on Linux for hours or days and should arrive ready: coding agents you drive from outside, a 60fps desktop with Chromium, a faster full VM with /dev/kvm, and hosting on 50 ports in the EU. Compare it one to one: bochka vs Morph Cloud and bochka vs Namespace.
Questions people ask
Is Morph Cloud cheaper than Namespace?
In all five scenarios we priced, yes. One agent running all month comes to $121 on Morph Cloud against $176 on Namespace, and 50 agents in parallel come to $1,459 against $2,198. bochka comes to $26 and $317 a month for the same two.
Which is faster, Morph Cloud or Namespace?
There is no comparable CPU measurement for Morph Cloud. Namespace did 21.79 Node.js build-and-test runs per second at 4 vCPU / 8 GB in StarSling's run, and bochka did 26.69 on the same test.
Can an agent run 24/7 on Morph Cloud or Namespace?
On Morph, yes: a machine keeps running until you stop it or a TTL you set ends. A Namespace Devbox is shut down after 4, 5 or 24 hours by plan, even while you work in it, so it needs a restart at least once a day.
Can Morph Cloud and Namespace run Docker?
Both can. Morph is a full VM with root, Docker in Docker and local Kubernetes, with nested virtualization marked experimental. Namespace Linux Devboxes include Docker, and /dev/kvm is on Linux compute instances. bochka has Docker, systemd and /dev/kvm on every machine.
Do they run macOS or Windows?
Namespace runs macOS on Apple M4 Pro and M5 Max chips and Windows on Team plans and up. Morph lists Windows and macOS (x86) guests as experimental. bochka runs Linux only, with Wine for Windows apps.
Which is better for Claude Code or Codex?
On Morph you install the agent in a Devbox and drive it through a tmux API. Namespace hosts sessions run by partners such as Anthropic, Cursor and Devin, plus an MCP server for your own agent. bochka ships both preinstalled with a prompt, steer and events API.
Try bochka
Install the CLI, then run bochka new.
Product preview