Azure Container Apps Sandboxes vs Modal VM Sandboxes
Both give each agent a machine with its own kernel. Azure's sandboxes run as long as you want and suspend with their memory inside your Azure account. Modal's VM Sandboxes are VMs with Docker that run up to 24 hours, carry work forward through filesystem snapshots, and scale to huge bursts.
The companies and products
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 and has its own kernel. A stop keeps the disk, or the disk and the memory, and a memory-mode sandbox resumes in under a second. It is built for teams already on Azure that want stateful code execution with Azure networking, identity and billing.
Modal VM Sandboxes
Modal is a serverless cloud for AI work, and VM Sandboxes are the version of its sandboxes that run in a virtual machine with their own Linux kernel.
You create a VM Sandbox from Python, TypeScript or Go code with runtime="vm", run commands in it, and terminate it when the job is done. Modal built the runtime on the Rust-based Cloud Hypervisor, so Docker, FUSE, systemd and nested cgroups work, with the same API, images and prices as its gVisor sandboxes. It became generally available on 1 October 2026. It suits teams that want many agent machines next to Modal's inference and training.
- Funding
- Over $1.2B raised
- Generally available
- 1 October 2026; early customers launched over 20 million VMs before that
- Compliance
- SOC 2 on every plan; HIPAA on Enterprise
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. “33rd cheapest of 365” means 32 of the other 364 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 | Azure Container Apps Sandboxes: price rank | Modal VM Sandboxes: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Modal ranks above Azure here because its VM runs Docker on every image. A Modal VM ends within 24 hours; to keep its files you snapshot the filesystem and boot a new sandbox from it, or use a Volume. A boat sandbox saves its disk at each stop with no code. | 33rd cheapest of 365 $5,276 a month | 27th cheapest of 365 $633 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An agent that lives on its machine all month runs on Azure with no session cap, billed every running second. On Modal you snapshot the filesystem before the 24-hour cap and boot a new sandbox each day; running programs start again. | 52nd cheapest of 361 $6,780 a month | Not ranked: misses a requirement | 6th cheapest of 361 $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. Azure sandboxes suspend with their memory and wake on traffic. Modal bills per second on the larger of request and use, with up to 5,000 containers at once on Team. | 39th cheapest of 336 $354 a month | Not ranked: misses a requirement | 189th of 336, 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 users who come back. Azure suspends idle sandboxes with their memory. On Modal you snapshot each user's filesystem and boot from it later (kept 30 days by default, or with no expiry). A stopped boat sandbox keeps its disk for at least 14 days, and each start counts against the plan's start limits. | 32nd cheapest of 349 $2,260 a month | Not ranked: misses a requirement | 3rd cheapest of 349 $209 a month |
| RL rollouts 1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month Huge bursts of short rollouts suit Modal's 5,000 containers at once on Team, with no per-start fee. Azure starts at 300 active cores by default. boat's $2,000 plan includes 90 starts a minute and refuses starts above 270. | 158th of 349, with limits $10,740 a month | 163rd of 349, with limits $11,982 a month | 39th of 349, with limits $2,000 a month |
| Agent evals 250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month | 85th cheapest of 359 $1,728 a month | Not ranked: misses a requirement | 10th cheapest of 359 $200 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Both run Docker builds, but Android or VM builds need /dev/kvm. boat has it on every plan, Modal on the Enterprise plan as an experimental option, and Azure does not document it. | 108th cheapest of 374 $1,046 a month | 170th of 374, with limits $655 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A dev box wants SSH and a disk that stays. Azure gives a shell through its own CLI and keeps state, Modal VMs end within a day, and boat has SSH and keeps a stopped disk for at least 14 days. | 327th of 371, with limits $262 a month | Not ranked: misses a requirement | 19th cheapest of 371 $26 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month Neither Azure nor Modal ships a desktop. You build one into your Azure image, or run Modal's example that installs Xvfb, VNC and Chromium. boat streams a 60 fps desktop with computer tools. | 58th cheapest of 367 $1,573 a month | Not ranked: misses a requirement | 7th cheapest of 367 $200 a month |
| Browser-use agents 50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month | 129th of 356, with limits $795 a month | Not ranked: misses a requirement | 7th cheapest of 356 $200 a month |
| Scraping & bots (startup scale) 50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month | 112th cheapest of 343 $561 a month | Not ranked: misses a requirement | 6th cheapest of 343 $90 a month |
| Mass scraping & bots (undetectable) 1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month | 240th of 327, with limits $10,956 a month | Not ranked: misses a requirement | 73rd of 327, with limits $1,800 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month | 30th cheapest of 351 $517 a month | 27th cheapest of 351 $464 a month | 3rd cheapest of 351 $200 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month | Not ranked: misses a requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
| macOS agents 5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month | Not ranked: misses a requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | Azure Container Apps Sandboxes | Modal VM Sandboxes | boat |
|---|---|---|---|
| Isolation | MicroVM per sandbox with its own kernel | VM with its own Linux kernel on Cloud Hypervisor | Full VM with its own kernel, on hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared |
| Docker and systemd | Depends on the image: azure-dev ships Docker on systemd; the default ubuntu image has only Buildah | Yes; you start dockerd yourself | Docker, systemd and root on every sandbox |
| Nested virtualization | Not documented | Enterprise plan only, as an experimental option | /dev/kvm on every plan |
| CPU benchmark (V8 Web Tooling, 4 vCPU / 8 GB, StarSling run of 3 October 2026) | Not in the public benchmarks we use | VM runtime 15.48 runs/s (gVisor 12.60), rank 7 of 15 (shared); measured with cpu=4 | 28.06 runs/s, rank 2 of 15 (shared), on a Ryzen 9 9950X host |
| Longest session | No cap; runs until stopped or auto-suspended when idle | 24 hours (default 5 minutes); continue in a new sandbox from a filesystem snapshot | No cap once auto-stop is off on a paid plan; auto-stop defaults to 1 hour, up to 30 days |
| Stop and resume | Suspend with memory and disk; resume in under a second with processes running | No paused state; you snapshot the filesystem and boot a new sandbox from it (kept 30 days by default, or with no expiry), or keep files in a Volume | Stop saves the disk with no code; kept at least 14 days, longer as a saved snapshot; a resume is like a reboot |
| Wake on traffic | Network traffic or a start command brings a suspended sandbox back | Not documented; your code creates a new sandbox | Auto-stop timer you set; a stopped sandbox is started by API |
| Fork and snapshots | Snapshot a running sandbox with its memory and create new sandboxes from it | Filesystem snapshots of a running sandbox boot any number of new ones; memory snapshots in alpha end the sandbox and expire after 7 days | Fork a running sandbox from its last 1-minute disk snapshot |
| Getting a shell and inbound access | Shell through the aca CLI, SDK or portal; public HTTPS routes per port; SSH and raw TCP not documented | Encrypted and raw TCP tunnels, connect tokens, inbound IP allowlist | SSH, up to 50 HTTPS URLs (token-gated by default), public IPv6 with raw ports |
| Desktop, browser and computer use | No desktop or browser in the public images; you can build one into your own OCI image | Not built in; Modal's runnable example installs Xvfb, x11vnc, noVNC, Chromium and a Browser Use agent | 1920x1080, 60 fps desktop with Chrome and computer tools |
| Coding agents and API keys | Copilot CLI and Claude Code images run through exec; built-in connections put tokens inside, while egress Transform rules you write add secrets from outside | You install the harness; official examples cover the Claude Agent SDK and OpenCode; a credential-injecting proxy runs in an experimental Sidecar | Seven harnesses installed with a prompt, steer and events API; optional paid AI credentials proxy for supported providers |
| Outbound network rules | Allow, deny, rewrite and header rules by host, path and method; VNet integration | Block all, IP-range allowlist, domain allowlist (beta) | Open internet, no provider-side allowlist |
| Disk | Up to 320 GiB on the largest tier | Fixed 512 GiB root filesystem on VMs | 51 GB on the default size, up to 251 GB on xlarge |
| Scaling a fleet | 300 concurrent active cores per region and subscription by default; more by Azure support request | 100 containers on Starter, 5,000 on Team, more on Enterprise; no per-start fee | 100 to 2,000 sandboxes by plan; starts per minute, hour and day capped by plan, extra starts paid |
| Regions | 40 Azure regions, 9 of them in the EU | US, EU and Asia-Pacific; pinning a region costs 1.15x to 1.75x | Germany, Finland and France; you cannot pick a region; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Azure Container Apps Sandboxes | Modal VM Sandboxes | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Not published | Yes | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Yes | Yes | Yes |
| Desktop GUI | With your own setup | With your own setup | Yes |
| Browser | With your own setup | With your own setup | Yes |
| Computer-use API | No documented way | With your own setup | Yes |
| SSH | No documented way | With your own setup | Yes |
| Persistent disk | Yes | With your own setup | Yes |
| Pause/resume | Yes | No documented way | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Not published | Yes |
| Memory fork | Yes | Yes | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | Yes | Yes | No documented way |
| Wake on request | Yes | No documented way | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No documented way | Yes | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | Yes | With your own setup | Yes |
| Secret proxy for any API | Yes | No documented way | Yes |
| Preinstalled agents | Yes | With your own setup | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | No documented way | No documented way | No documented way |
| GPU | No documented way | No documented way | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | No documented way | No documented way | No documented way |
| Self-hosting | No documented way | No documented way | No documented way |
| BYOC | No documented way | No documented way | No documented way |
| Open source | No documented way | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | Yes | Not published | Yes |
| Usage per sandbox (API) | Yes | Not published | Yes |
| Audit logs | Yes | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | Yes | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
In StarSling's run of 3 October 2026 (run 37073680030), on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, boat did 28.06 runs/s, second of 15. Modal's VM runtime did 15.48 and its gVisor runtime 12.60, both rank 7 (shared). StarSling ran Modal with cpu=4 and the sandbox saw 4 CPUs (PR #121); sized that way, Modal bills 4 cores, $0.76/h, not the 2-core $0.476/h list price. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. Providers ran on different hardware in different regions. Azure Container Apps Sandboxes is not in the public benchmarks we use, so we cannot say how it compares.
V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Modal VM Sandboxes measured on: VM Sandbox, request = size. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. Azure Container Apps Sandboxes is not in the public benchmarks we use, so we cannot say which is faster.
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. Start limits, per-start fees and plan minimums are in the price, boat's included.
| Scenario | Azure Container Apps Sandboxes, a month | Modal VM Sandboxes, 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 | $68 · Pay-as-you-go | $0 · Starter | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $262 · Pay-as-you-go · with limits | $109 · Starter · 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 | $3,421 · Pay-as-you-go | $1,480 · Starter | $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 | $989 · Pay-as-you-go | $579 · Team | $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 | $2,148 · Pay-as-you-go | $1,911 · Team · with limits | $8,800 · $2000/mo · with limits |
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. The XL tier (4 cores / 8 GiB) is $0.432 an hour at the East US rates. Stopped sandboxes pay no CPU or memory, and there is no plan fee.
Modal VM Sandboxes: Modal bills by the second for the larger of the CPU and memory you request or use, until the sandbox ends. It prices CPU per physical core, and one core equals two vCPUs, so 4 vCPU / 8 GiB is $0.476 an hour when the request equals the size. The scenario bills here use a minimal request that bursts above it; that extra CPU is shared and not guaranteed. Starter is $0 with $30 of credit a month, Team is $250 a month with $100 of credit, and pinning a region multiplies the price.
Modal VM Sandboxes: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month; unused time does not carry over. A default sandbox (4 vCPU / 8 GB) costs $0.036 an hour, billed per second while it runs. The $20 plan includes 12 starts a minute, 60 an hour and 200 a day; extra starts cost $0.03 to $0.07 each. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots above the included count and the optional AI credentials proxy still charge while stopped.
Limits in those scenarios
A Modal VM Sandbox runs 24 hours at most, so the always-on scenario needs a snapshot and a new sandbox each day and is marked as not fitting as-is. Files carry over only through a filesystem snapshot or a Volume that your code sets up. In the 1,000-job burst, Modal's priced setup uses shared CPU, which the table marks as a compromise. Azure has no session cap, but it bills every running second, so the always-on scenario reaches its lowest price only with a 3-year savings plan, and Azure does not state that the plan covers Sandboxes. Azure's default quota is 300 active cores per region and subscription: 50 XL sandboxes use 200, but 300 user sandboxes and 1,000 short jobs need a raise first. boat does not fit the 1,000-job burst: the $2,000 plan includes 90 starts a minute, starts above 270 a minute fail with 429, and boat never queues a start.
| Scenario | Azure Container Apps Sandboxes | Modal VM Sandboxes | boat |
|---|---|---|---|
| One coding agent, workdays | None for this scenario | None for this scenario | None for this scenario |
| One agent that never stops |
|
| None for this scenario |
| 50 agents in parallel | None for this scenario | None for this scenario | None for this scenario |
| Sandboxes for your users | None for this scenario | None for this scenario | None for this scenario |
| 1,000 short jobs at once | None for this scenario |
|
|
Which one should you use?
Use Azure Container Apps Sandboxes when
your team is on Azure and wants stateful sandboxes that suspend with their memory, wake on traffic, sit behind strict egress rules and have no session cap.
- Suspend with memory, wake on traffic. For stateful jobs that sleep between requests: a sandbox suspends with its memory and resumes in under a second.
- No session cap. A sandbox keeps running until you stop it or it goes idle, so long jobs are not cut off at a day.
- Fine-grained egress inside Azure. Teams on Azure get per-request outbound rules, VNets and Entra ID, in 40 regions.
Use Modal VM Sandboxes when
you run huge bursts of short jobs that need Docker in a real VM, finish within a day, or sit next to models you already run on Modal.
- Docker on every VM. Every VM Sandbox has a real Linux kernel where Docker, FUSE and systemd work, whatever image you pick, with a 512 GiB root filesystem.
- Huge bursts of short jobs. Good for evals and rollouts: Team runs 5,000 containers at once, with more on Enterprise and no per-start fee.
- One platform with your models. Teams that already serve or train models on Modal can keep sandboxes on the same account and bill. Starter is $0 with $30 of credit a month.
Where boat fits
Azure is strongest at short stateful jobs inside an Azure account, and Modal at huge bursts of VMs that run up to a day. If your agents do long real work on one machine, with builds, emulators, a browser and you stepping in over SSH, boat gives them a whole computer that keeps its disk across stops. boat caps starts per plan and runs only in Germany, Finland and France.
A whole computer you can SSH into
Azure does not document SSH or /dev/kvm, and Modal offers nested virtualization on the Enterprise plan only, as an experimental option. boat has SSH, Docker, systemd and /dev/kvm on every sandbox.
A disk that stays with no code, and no 24-hour cutoff
A Modal VM ends within 24 hours, and you write snapshot or Volume code to carry its files forward. Azure keeps state and bills every running second. boat saves the disk every minute and at each stop, and keeps a stopped disk for at least 14 days.
Desktop and agents built in
Neither ships a desktop: you build one into your Azure image or run Modal's Xvfb and VNC example. boat has a 60 fps desktop, Chrome and seven agents you drive from outside by API.
Use boat when your agents work for hours or days on a machine they come back to: SSH, Docker, /dev/kvm, a desktop and a browser, with the disk saved at each stop, within its plan start limits. Compare it one to one: boat vs Azure Container Apps Sandboxes and boat vs Modal VM Sandboxes.
boat's own limits
- Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
- Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
- A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
- Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
- boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
- Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
- Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
- Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source
Questions people ask
Is Azure Container Apps Sandboxes cheaper than Modal VM Sandboxes?
Modal costs less in all five of our scenarios, for example $1,480 against $3,421 a month for 50 parallel agents, and $0 against $68 for one agent on workdays within Starter's monthly credit. Modal's bills use a minimal CPU request that bursts above it, and to keep files between days you snapshot the filesystem or use a Volume. boat costs $317 and $20 for the same two scenarios.
Which is faster, Azure or Modal?
Modal's VM runtime did 15.48 runs/s and its gVisor runtime 12.60 on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB in StarSling's run of 3 October 2026. Azure is not in that run, so we cannot compare it. boat did 28.06 runs/s in the same run, on an AMD Ryzen 9 9950X host.
Can I run Docker in Azure Container Apps Sandboxes and Modal VM Sandboxes?
Modal runs Docker in every VM Sandbox once you start dockerd. On Azure it depends on the image: azure-dev ships Docker on systemd, while the default ubuntu image has only Buildah. boat runs Docker on every sandbox and also exposes /dev/kvm.
How long can a sandbox run on each?
A Modal VM Sandbox runs 5 minutes by default and 24 hours at most; a filesystem snapshot carries its files to a new sandbox. Azure documents no cap: a sandbox runs until you stop it or it auto-suspends when idle. boat has no session cap once auto-stop is off on a paid plan; auto-stop defaults to 1 hour.
Can I SSH into them?
Azure gives an interactive shell through the aca CLI, the SDK or the portal, and does not document SSH. Modal offers encrypted and raw TCP tunnels into a sandbox. Every boat sandbox takes SSH.
Is boat SOC 2 compliant?
SOC 2 is in progress, and boat has no SOC 2 report today. Modal has SOC 2 on every plan. Live status is at status.ascii.dev and boat's data retention policy is at docs.boat.dev/data-retention.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Azure Container Apps Sandboxes
- boat vs Modal VM Sandboxes
- E2B vs Azure Container Apps Sandboxes
- Daytona vs Azure Container Apps Sandboxes
- Modal vs Azure Container Apps Sandboxes
- Vercel Sandbox vs Azure Container Apps Sandboxes
- Cloudflare Sandbox vs Azure Container Apps Sandboxes
- Blaxel vs Azure Container Apps Sandboxes
- Runloop vs Azure Container Apps Sandboxes
- Tensorlake vs Azure Container Apps Sandboxes
- Morph Cloud vs Azure Container Apps Sandboxes
- CodeSandbox SDK vs Azure Container Apps Sandboxes