Morph Cloud
VM-based cloud computers for AI agents built on “Infinibranch” snapshot, branch and restore, plus persistent Devboxes. Purpose-built for branching workloads; a specialist pick for search, RL and evals.
Overview
Morph Cloud’s core idea is branching: snapshot a running VM — memory, processes and disk — and start many copies from that exact state in a fraction of a second. That suits tree search, best-of-N agent attempts and RL rollouts, where you want to explore many paths from one prepared environment.
Devboxes extend the same infrastructure to persistent development workspaces.
Notable
- Also sells GitHub Actions runners billed in compute units.
Morph Cloud specifications
| Attribute | Details |
|---|---|
| Isolation | Full VMs; hypervisor not named |
| Deployment | Hosted platform |
| Open source | No (SDKs Apache-2.0) |
| SDKs and interfaces | Python, TypeScript |
| Cold start (vendor claim) | Snapshot, branch and restore entire environments in under 250 ms (vendor claim) |
| Max session length | Configurable TTL per instance; Devboxes can disable auto-sleep to run like a persistent VPS |
| Persistence | Snapshots, branching many instances from one state, pause/resume preserving memory and processes, volumes, wake-on-request |
| GPU | Not documented |
| Networking | Public HTTP URLs with optional API-key auth; SSH and reverse tunnels; egress controls not documented |
| Pricing | Morph Compute Units at $0.05 each (1 MCU = 1 vCPU-hour + 4 GB RAM-hours + 16 GB disk-hours); Team $40/month incl. 1,000 MCUs |
| Free tier | Developer plan $0/month (pricing page and docs disagree on included hours) |
| Compliance | Not documented |
| Regions | Not documented |
Facts from Morph Cloud’s public documentation, verified November 8, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You run many parallel attempts from one environment state
- You want pause/resume that keeps running processes
- You like a single blended compute unit for billing
Trade-offs
- Hypervisor and egress controls not documented
- No GPU support documented
- No published compliance attestations
Best for: Workloads that branch a running environment many times — parallel search, RL and evaluation rollouts.
Where Morph Cloud ranks
How Morph Cloud compares
| Sandbox | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|
| Morph Cloud | VM | No | No / Not documented | <250 ms (restore) | Configurable | Yes / Yes | Not documented | Python, TypeScript |
| Modal Sandboxes | gVisor or VM | No | No / Not documented | <1 s | Up to 24 h | Yes / Yes | Yes | Python, JavaScript/TypeScript, Go |
| E2B | Firecracker microVM | Yes | Yes / Yes | Not documented | 1 h / 24 h (Pro) | Yes / Yes | No | Python, JavaScript/TypeScript |
| Freestyle | VM | No | No / Not documented | 65 ms | Unlimited (paid) | Yes / Yes | Not documented | TypeScript |
| Daytona | Containers or VMs | No | Not documented / Yes | <90 ms | Unlimited | Yes / Yes | Yes | Python, TypeScript, Ruby, Go, Java |
Head-to-head: Morph Cloud vs E2B
Frequently asked questions
What is Morph Cloud?
How does Morph Cloud isolate code?
Is Morph Cloud open source?
How much does Morph Cloud cost?
What are the best Morph Cloud alternatives?
Sources
Cite this page
Agent Sandboxes. (2026). Morph Cloud. agentsandboxes.org. Last reviewed November 8, 2026. https://agentsandboxes.org/sandboxes/morph/
Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.