Morph Cloud vs Azure Container Apps Sandboxes

Both keep a machine's memory when it sleeps and wake it on the next request. Morph Cloud gives you a full VM with SSH and fast memory branching, while Azure Container Apps Sandboxes gives you headless microVMs inside your Azure account, with strict outbound rules and 40 regions.

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.

Azure Container Apps Sandboxes

Azure Container Apps Sandboxes is a service inside Microsoft Azure that gives each agent or user an isolated microVM you create, suspend and resume through an SDK.

It is part of Azure Container Apps, the hyperscaler's serverless container platform, and lives in your Azure subscription as a sandbox group resource. Each sandbox boots from an OCI image or a snapshot, has its own kernel, and can be suspended with its memory and resumed in under a second. It is built for teams already on Azure that want stateful code execution with Azure networking, identity and billing.

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 workloadMorph Cloud: price rankAzure Container Apps Sandboxes: price rankbochka: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
A software factory needs Docker, emulators and long builds; Morph has Docker everywhere, Azure only on some images, and bochka adds /dev/kvm and preinstalled coding agents.
198th of 367, with limits
$2,288 a month
288th of 367, with limits
$5,276 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
302nd of 366, with limits
$6,544 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
Both fit short code runs that sleep with their memory and wake on the next request; Morph costs less in this use case.
16th cheapest of 345
$154 a month
34th cheapest of 345
$354 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 pause idle user machines with their memory and wake them on traffic; bochka gives each user hosting on up to 50 ports and costs the least here.
12th cheapest of 361
$905 a month
22nd cheapest of 361
$2,260 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
Rollouts that all start from one running state suit both, since each can copy a machine with its memory into many new ones.
86th of 360, with limits
$4,847 a month
153rd of 360, with limits
$10,740 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
75th cheapest of 364
$1,728 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; Azure has none listed, and builds that need nested virtualization fit bochka's /dev/kvm best.
39th cheapest of 377
$355 a month
103rd cheapest of 377
$1,046 a month
4th cheapest of 377
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
A dev box wants SSH; Morph has it through its gateway, Azure gives a shell only through its CLI, SDK or portal, and bochka adds raw TCP.
85th cheapest of 368
$116 a month
322nd of 368, with limits
$262 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
Azure's sandboxes are headless and Morph's desktop needs you to install the browser and agent; bochka ships a 60fps desktop with Chromium and a computer use API.
182nd of 369, with limits
$595 a month
279th of 369, with limits
$1,573 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 both Morph and Azure you install and run the browser yourself; bochka has Chromium ready on its desktop.
214th of 367, with limits
$250 a month
288th of 367, with limits
$795 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
284th of 346, with limits
$561 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
239th of 338, with limits
$10,956 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
278th of 360, with limits
$517 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 itCan't run itCan't run it
macOS agents
5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month
Can't run itCan't run itCan't run it

Key features

FeatureMorph CloudAzure Container Apps Sandboxesbochka
IsolationFull VM with its own kernelMicroVM per sandbox with its own kernelFull VM with its own kernel on dedicated AMD Ryzen 9 9950X hosts
Docker and systemdYes, including Docker in Docker and local KubernetesDepends on the image: azure-dev ships Docker on systemd; the default ubuntu image has only BuildahDocker, systemd and root on every sandbox
Nested virtualizationExperimentalNot documentedYes, /dev/kvm for Android emulators and VMs
Getting a shellSSH through Morph's gatewayInteractive shell through the aca CLI, SDK or portal; no SSHSSH, plus CLI and API exec
Sleep with memory and wake on requestPause with memory; resumes on the next HTTP request, SSH or exec callAuto-suspend with memory after an idle timeout; traffic or a start command brings it back in under a secondNo; disk is saved every minute and on stop, and resume boots the machine again
Copy a running machineBranch with its memory into many copies in under 250 msSnapshot with its memory and create new sandboxes from itFork a running sandbox with its disk
Desktop and browserBrowser-based remote desktop; you install the browser and any computer use agentHeadless; no desktop or managed browser60fps Linux desktop with Chromium and a computer use API
Coding agentsYou install the agent and drive it through a tmux APICopilot CLI and Claude Code images, run through the exec APISeven agents preinstalled, with a prompt, steer and events API
Keeping API keys out of the sandboxResponses Proxy for model APIs; other secrets are handed to the machineGroup secrets usable in egress header rules; Copilot and Anthropic tokens are injected at startupCredentials proxy for model providers and any HTTPS API; switch a credential to another account when credits run out
Inbound accessNamed HTTP services with optional API key auth; no raw TCPPublic HTTPS routes per published port; private endpoint from your VNet; no public IPHTTPS URLs for up to 50 ports, token-protected by default; raw TCP; dedicated IPv4 or IPv6
Outbound rulesOpen internet, no egress rulesAllow, deny, rewrite and header rules by host, path and method; VNet integrationOpen internet, no provider-side allowlist
Guest systemsLinux, with experimental Windows and macOS (x86)LinuxLinux
RegionsNot published40 Azure regions, 9 of them in the EUEU only (Germany, Finland, France), with zero data retention
Scaling up a fleetAccount pools of 64, 256 or 1,024 vCPU by plan500 concurrent active cores by default; more by Azure support requestConcurrency set by plan, up to 2,000 sandboxes, self-serve
Every feature Battleships tracks (43)
FeatureMorph CloudAzure Container Apps Sandboxesbochka
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationYesNoYes
RootYesYesYes
SystemdYesYesYes
Desktop GUIYesNoYes
BrowserNoNoYes
Computer-use APINoNoYes
SSHYesNoYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesYesYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkYesYesNo
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo
Wake on requestYesYesNo
HTTPS preview URLsYesYesYes
Raw TCP inboundNoNoYes
Public IPv4NoNoNo
Egress allowlistNoYesNo
Secret proxyYesYesYes
Secret proxy for any APINoYesYes
Preinstalled agentsNoYesYes
Agent harness APIYesNoYes
MCP serverNoNoNo
GPUNoNoNo
WindowsYesNoNo
Arm64NoNoNo
Self-hostingNoNoNo
BYOCNoNoNo
Open sourceNoNoNo
Scoped API keysYesNot publishedYes
Spend limitsNot publishedYesYes
Usage per sandbox (API)YesYesYes
Audit logsYesYesNo
SSONot publishedYesNo
SOC 2Not publishedYesNo
HIPAANot publishedYesNo
EU data residencyNot publishedYesYes
Zero data retentionNot publishedNot publishedYes

Performance

Morph CloudNot measured
Azure Container Apps SandboxesNot measured
bochka26.69 runs/s

Neither Morph Cloud nor Azure Container Apps Sandboxes has a comparable CPU measurement: they are not in the hpc-sandbox-benchmarks run. bochka 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. This page makes no speed claim between them.

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 Azure Container Apps Sandboxes 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.

ScenarioMorph Cloud, a monthAzure Container Apps Sandboxes, a monthbochka, 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$68 · 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$262 · 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$3,421 · 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$989 · 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$2,148 · 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.

Azure Container Apps Sandboxes: Azure bills per second on the Container Apps Consumption meters for the vCPU and memory of the sandbox's tier while it runs, idle time before auto-suspend included. There is no plan fee, and some regions such as West Europe charge more.

Azure Container Apps Sandboxes: 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

Morph costs less than Azure in all five scenarios, but its disk beyond 16 GiB per MCU raises the bill and its egress price is not published. Azure's always-on agent only gets close to its listed price with a 3-year commitment, and a default quota of 500 active cores caps a fleet until support raises it. For the 50-agent fleet, Azure needs an image that ships Docker, like azure-dev. bochka is the cheapest wherever it fits, but at 1,000 short jobs at once its $2,000 plan queues starts, while both Morph and Azure fit.

ScenarioMorph CloudAzure Container Apps Sandboxesbochka
One coding agent, workdays
  • disk beyond 16 GiB: price unknown
  • egress price not published
None that biteNone that bite
One agent that never stops
  • disk beyond 16 GiB: price unknown
  • egress price not published
  • 3-year commitment
None that bite
50 agents in parallel
  • disk beyond 16 GiB: price unknown
  • egress price not published
None that biteNone that bite
Sandboxes for your users
  • egress price not published
None that biteNone that bite
1,000 short jobs at once
  • egress price not published
None that bite
  • max 2,400 starts/day (needs ~6,667)
  • max 600 starts/hour (needs ~1,000)
  • bursts above 90 starts/min are queued (a burst of 333 takes ~4 min to start)

Which one should you use?

Use Morph Cloud when

your agents branch from one running state with its memory, need a full VM with SSH, or need experimental Windows and macOS guests or managed CI runners.

  • Fast branching with memory. For agents that fan out from one running state, Morph copies a VM with its memory into many branches in under 250 ms.
  • A full VM you can SSH into. Every machine has Docker and SSH through Morph's gateway, so tools that expect a normal server work without picking a special image.
  • Windows, macOS and managed CI. Morph lists experimental Windows and macOS (x86) guests and sells managed GitHub Actions runners from the same balance.

Use Azure Container Apps Sandboxes when

your team already runs on Azure and wants short stateful sandboxes behind strict outbound rules, in regions outside the EU.

  • Fine-grained outbound rules. For agents you must hold to chosen hosts, Azure can allow, deny or rewrite each outbound request by host, path and method.
  • Inside your Azure account. Teams already on Azure get Entra ID sign-in, Azure billing and their existing VNets with no new vendor.
  • 40 regions. Sandboxes run in 40 Azure regions on six continents, for teams that need machines near users outside the EU.

Where bochka fits

Morph and Azure are both built around machines that sleep with their memory and wake fast. If your agents instead do long, real work on a computer, with emulators, a screen, a browser and keys they must not see, bochka gives them that ready, and in every scenario it fits it costs less than both.

Nested virtualization that works

An agent that builds Android apps or starts a VM needs /dev/kvm. Morph lists nested virtualization as experimental and Azure does not document it, so those jobs may not run at all. bochka exposes /dev/kvm on every sandbox.

A screen and a browser ready to use

Azure's sandboxes are headless, and Morph's remote desktop leaves you to install the browser and wire up computer use. On either, you build and maintain that image yourself. bochka ships a 60fps desktop with Chromium and a computer use API.

Agents driven from outside, keys kept outside

Morph drives agents by tmux keystrokes and Azure by raw exec, and both put non-model or agent tokens inside the machine. bochka preinstalls seven agents with a prompt, steer and events API, and its credentials proxy covers any HTTPS API.

Use bochka when your agents need a whole computer for long, real work: /dev/kvm for emulators, a desktop with Chromium, coding agents you drive from outside, and real keys kept outside the machine. Compare it one to one: bochka vs Morph Cloud and bochka vs Azure Container Apps Sandboxes.

Questions people ask

Is Morph Cloud cheaper than Azure Container Apps Sandboxes?

In all five scenarios on this page, yes, at roughly half or less of Azure's price: one workday coding agent is $32 a month on Morph against $68 on Azure. bochka costs less than both in the four scenarios it fits.

Which is faster, Morph Cloud or Azure Container Apps Sandboxes?

Neither has been measured on the same CPU test, so there is no fair speed answer. Both wake a sleeping machine fast: Morph restores a snapshot in under 250 ms and Azure resumes in under a second.

Can both run Docker?

Morph runs Docker in every VM, including Docker in Docker and local Kubernetes. On Azure it depends on the image: azure-dev ships Docker on systemd, while the default ubuntu image has only Buildah. bochka runs Docker on every sandbox.

Can I SSH into Morph Cloud or Azure sandboxes?

Morph has SSH through its gateway. Azure gives an interactive shell through the aca CLI, the SDK or the portal, with no SSH. bochka has SSH plus raw TCP on its own IP.

Do I need an Azure account for Azure Container Apps Sandboxes?

Yes. It needs an Azure subscription, a Microsoft Entra ID account and the Container Apps SandboxGroup Data Owner role. Morph and bochka have their own sign-up.

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

More comparisons

Bochka product preview · Pricing, benchmarks and commands are illustrative. Sandbox provisioning is not connected.