Morph Cloud vs Replit
Morph Cloud sells full Linux VMs that your code creates by API, then snapshots, branches and wakes with their memory. Replit is an AI app builder: you describe an app, Replit Agent writes it, and Replit hosts it.
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
Replit
Replit is an AI app builder and hosting platform: you describe an app in chat, Replit Agent writes it, and Replit publishes it.
You work in a browser workspace where Replit Agent sets up the project, writes the code, tests it and fixes problems, with system packages managed by Nix. When the app is ready you publish it as an Autoscale, Static, Scheduled or Reserved VM deployment, with Postgres and object storage next to it. It is built for people and teams who want a working app, not for programs that need to create many machines by API, so this page compares the parts where the two overlap.
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 | Replit: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Morph runs Docker and full builds but you install the agent and drive it through tmux; Replit's MCP server drives Replit Agent one app at a time; boat has coding agents you prompt and steer by API. | 198th of 367, with limits $2,288 a month | 181st of 367, with limits $2,000 a month | 3rd cheapest of 367 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 235th of 366, with limits $3,014 a month | 202nd of 366, with limits $2,033 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 fits short code runs well: a machine can pause with its memory, cost almost nothing while paused and wake on the next request, while Replit's Autoscale is a web host, not a code runner. | 16th cheapest of 345 $154 a month | 228th of 345, with limits $146 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 give each user a VM that pauses and wakes on request; Replit does not publish how many deployments can run at once, and each one is a published app. | 12th cheapest of 361 $905 a month | 233rd of 361, with limits $825 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 the same running state, which Replit has no way to do. | 86th of 360, with limits $4,847 a month | 258th of 360, with limits $4,226 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 Evals need many fresh machines started by code, which Morph and boat both offer by API and Replit does not. | 38th cheapest of 364 $675 a month | 265th of 364, with limits $685 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 runs Docker and also sells managed GitHub Actions runners; Replit's Nix-based environments do not document Docker, which most CI jobs need. | 39th cheapest of 377 $355 a month | 275th of 377, with limits $425 a month | 4th cheapest of 377 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A Replit workspace is a good place to code by hand, but it has no Docker or systemd; Morph and boat give you a full VM with root. | 85th cheapest of 368 $116 a month | 165th of 368, with limits $109 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 Neither ships a computer use API: Morph has a browser-based remote desktop you set up yourself, and Replit's VNC pane shows a desktop to a person; boat ships a 60fps desktop with Chromium and a computer use API. | 182nd of 369, with limits $595 a month | 190th of 369, with limits $619 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 | 229th of 367, with limits $317 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 | 234th of 346, with limits $217 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 | 150th of 338, with limits $4,378 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 | 208th of 360, with limits $215 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 | Replit | boat |
|---|---|---|---|
| Kind of product | Full VMs for AI agents, created, snapshotted and branched by API | AI app builder with browser workspaces and app hosting | Sandboxes you create, stop and fork by API, SDK or CLI |
| Isolation | Full VM with its own kernel | Not documented; the security page says strong logical separation between users | Full VM with its own kernel on dedicated AMD Ryzen 9 9950X hosts |
| Creating machines from code | Python and TypeScript SDKs to start, pause, snapshot and branch instances | MCP server tools to create, update and publish apps; no API to start many machines | API, SDK and CLI to create, stop, resume and fork many sandboxes |
| Root, Docker and nested virtualization | Root and Docker, including Docker in Docker and local Kubernetes; nested virtualization is experimental | System packages come from Nix; the docs do not describe Docker, systemd or /dev/kvm | Root, Docker, systemd and /dev/kvm on every machine |
| Pause with memory and wake on request | A paused VM keeps its processes and memory, bills only its snapshot, and wakes on the next HTTP request, SSH or exec call | Autoscale apps start on the first request and go idle after 15 minutes; no pause with memory | No; disk is saved and resume boots the machine again |
| Fork a running machine | Yes, with its memory, as many copies as you ask for, in under 250 ms | Not documented; Agent checkpoints let you roll a project back | Yes, with its disk |
| Saving work automatically | Saved when you pause or snapshot; a plain stop deletes the instance | Workspace files and Agent checkpoints; published apps should not rely on their filesystem | Disk saved every minute and on every stop; a stopped sandbox is free |
| Coding agents | You install the agent, then drive it through a tmux API that sends keys and reads the screen | Replit Agent, which you can also drive from an MCP client (create, update, ask, publish) | Seven agents preinstalled, including Claude Code and Codex, with a prompt, steer and events API |
| Keeping API keys out of the machine | Responses Proxy for model APIs; other secrets are handed to the machine | Replit manages keys for OpenAI, Anthropic, Google and OpenRouter models; other keys are secrets in the app | Credentials proxy for model providers and any HTTPS API; switch a credential to another account when credits run out |
| Desktop and computer use | Browser-based remote desktop; you install the browser and any computer use agent yourself | VNC pane that streams a native desktop to your browser; no computer use API | 60fps Linux desktop with Chromium and a computer use API, embeddable in your app |
| Inbound access | Named HTTP services with optional API key auth; SSH through Morph's gateway; no raw TCP | Published apps on HTTPS domains and custom domains; SSH into the workspace on paid plans | HTTPS URLs for up to 50 ports, token-protected by default; raw TCP; SSH |
| Built-in storage | Morph EFS, a named filesystem several machines can mount at once | Postgres and App Storage built into each app | No hosted databases; run your own inside a sandbox |
| Guest systems | Linux, with experimental Windows and macOS (x86) | Linux | Linux |
| Where it runs | Regions not published | Data mainly in Google Cloud in the United States; published apps in North America, Europe, Asia, South America or Australia on Core and up | EU only (Germany, Finland, France), with zero data retention |
Every feature Battleships tracks (43)
| Feature | Morph Cloud | Replit | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | No | Yes |
| Nested virtualization | Yes | No | Yes |
| Root | Yes | Not published | Yes |
| Systemd | Yes | No | Yes |
| Desktop GUI | Yes | Yes | Yes |
| Browser | No | No | Yes |
| Computer-use API | No | No | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | No | Yes |
| Automatic snapshots | Yes | Yes | Yes |
| Fork/clone | Yes | Yes | 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 | Not published | Yes |
| Public IPv4 | No | No | No |
| Egress allowlist | No | No | No |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | No | No | Yes |
| Preinstalled agents | No | Yes | Yes |
| Agent harness API | Yes | Yes | Yes |
| MCP server | No | Yes | No |
| GPU | No | No | No |
| Windows | Yes | No | No |
| Arm64 | No | Not published | 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 | 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
There is no comparable measurement for either Morph Cloud or Replit: neither is in the hpc-sandbox-benchmarks run, so we cannot say which of the two is faster. boat did 26.69 runs per second on that Node.js build-and-test loop at 4 vCPU / 8 GB, on dedicated AMD Ryzen 9 9950X hosts. Morph says it restores a snapshot in under 250 ms, 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. Morph Cloud and Replit 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 | Replit, a month | boat, 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 | $122 · Pro $100 (annual) · with limits | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $121 · Team | $122 · Pro $100 (annual) · 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 | $1,330 · Pro $1,000 (annual) · 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 | $403 · Pro $250 (annual) · 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 | $825 · Pro $1,000 (annual) · 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 storage.
Replit: Replit plans (Core $20, Pro from $100) turn into monthly credits for Agent work and hosting, then usage goes on to pay-as-you-go. A Reserved VM has a fixed monthly price per size, such as $130 for 4 vCPU / 16 GB, and bills whether busy or idle; our bills price agents as Reserved VMs and leave out Agent usage.
Replit: 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
Replit is marked as not a fit in every scenario because it is an app platform: one Reserved VM is one published app that runs all month, it does not document Docker, and it does not publish how many deployments can run at once, so 300 or 1,000 machines at once are not confirmed. Morph fits all five scenarios, but more than 16 GiB of disk per vCPU raises its price, egress prices are not published, and its Developer pool of 64 vCPU holds only 16 machines at 4 vCPU. On boat, the 1,000-job burst is queued above 90 starts a minute and needs more starts per day than the $2,000 plan allows.
| Scenario | Morph Cloud | Replit | boat |
|---|---|---|---|
| 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 code needs full VMs for agents, especially ones that branch from one running state with its memory or sleep and wake on request.
- Machines your code creates. Useful if your program needs many full VMs with root and Docker, started and stopped by API rather than through a chat.
- Memory snapshots, branching and wake on request. Useful for agents that fan out from one running state or sleep between requests: a paused VM keeps its memory and wakes on demand.
- Windows and macOS guests. Morph lists experimental Windows and macOS (x86) guests for agents that must work in those systems.
Use Replit when
you want Replit Agent to build a web app from a description and host it for you, with a database, hosting that sleeps when idle and regions outside Europe.
- An app built and hosted for you. Useful if you want a working app from a description: Replit Agent builds, tests and publishes it with Postgres and storage.
- Hosting that costs nothing when idle. Useful for web apps with uneven traffic: Autoscale wakes on the first request and costs nothing while idle.
- Regions on five continents. Useful if your users are spread out: Replit publishes apps in North America, Europe, Asia, South America and Australia.
Where boat fits
If you are comparing Morph Cloud and Replit because you want machines for AI agents, boat sits closer to Morph: full VMs your code creates by API, with root, Docker, systemd and /dev/kvm. The difference is that boat's machines arrive ready for agents, with coding agents you drive from outside, a desktop for computer use and real keys kept outside the machine, and the disk is saved every minute.
Coding agents you drive from outside
On Morph you install the agent and drive it by sending keystrokes to tmux and reading the screen. Replit's MCP server drives only Replit Agent, with no event stream. boat ships seven agents with a prompt, steer and events API.
A desktop agents can actually use
Morph's remote desktop needs you to install the browser and wire up the screenshot and click loop. Replit's VNC pane shows a desktop to a person, with no API. boat has a 60fps desktop with Chromium and a computer use API.
Real keys never enter the machine
Morph's Responses Proxy and Replit's managed keys cover model APIs only, so keys for GitHub, Stripe or anything else sit where the agent can read them. boat's credentials proxy covers any HTTPS API.
Use boat when your agents need full VMs that arrive ready: coding agents you prompt and steer by API, a desktop with Chromium for computer use, real keys kept outside the machine, and disk saved every minute in the EU. Compare it one to one: boat vs Morph Cloud and boat vs Replit.
Questions people ask
Is Morph Cloud cheaper than Replit?
In most scenarios we priced, yes, and Replit does not fit any of them as a sandbox. One coding agent on workdays comes to $32 on Morph against $122 on Replit, and sandboxes for your users come to $325 against $403. For 50 agents in parallel Replit is lower at $1,330 against $1,459, and for 1,000 short jobs at once at $825 against $869.
Which is faster, Morph Cloud or Replit?
We cannot say: neither is in the public benchmark we use. boat did 26.69 Node.js build-and-test runs per second at 4 vCPU / 8 GB in that benchmark.
Can Morph Cloud or Replit run Docker?
Morph Cloud runs Docker inside each VM, including Docker in Docker and local Kubernetes. Replit's docs set up environments with Nix packages and do not describe running Docker. Every boat sandbox has root, systemd, Docker and /dev/kvm.
Can I branch a running machine with its memory?
On Morph Cloud, yes: Infinibranch copies a running VM with its memory in under 250 ms, and every copy continues from the same point. Replit does not document this. boat can fork a running sandbox with its disk, but the copy boots fresh.
Can I drive a coding agent from my own code?
On Morph you install the agent in a Devbox and drive it through a tmux API that sends keystrokes and captures the screen. Replit's MCP server lets an MCP client create and update apps through Replit Agent only. On boat you prompt, steer and stream events from Claude Code, Codex and other agents inside each sandbox.
Where does my data run?
Morph Cloud does not publish its regions. Replit hosts data mainly on Google Cloud in the United States, and on Core and up you can publish apps in North America, Europe, Asia, South America or Australia. boat runs only in the EU, in Germany, Finland and France.
Try boat
Install the CLI, then run boat new.
7-day free trial