Azure Container Apps Sandboxes vs Upstash Box

Azure gives each sandbox a microVM with its own kernel that suspends with its memory, inside your Azure account in 40 regions. Upstash Box gives each agent a light Docker container in AWS us-east-1 that pauses when idle, bills only the CPU it uses, and comes with coding agents and a managed browser built in.

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.

Upstash Box

Upstash Box is a cloud computer for AI agents from Upstash, the company known for serverless Redis, Vector and QStash.

Each box is a Docker container with its own filesystem, shell, git and an optional coding agent such as Claude Code, Codex, OpenCode or Cursor, which you drive from TypeScript or Python SDKs. A box pauses when it sits idle, keeps its files, and you pay for the CPU it actually uses. Upstash built it to run its own Context7 service and opened it to everyone in March 2026.

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 workloadAzure Container Apps Sandboxes: price rankUpstash Box: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
A software factory needs Docker and long builds. Upstash does not document Docker inside a box, Azure needs the azure-dev image for it, and boat has Docker and /dev/kvm on every sandbox.
33rd cheapest of 365
$5,276 a month
98th of 365, with limits
$464 a month
5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
52nd cheapest of 361
$6,780 a month
170th of 361, with limits
$450 a month
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. Upstash's EphemeralBox is ready at once with no polling and an idle box costs no CPU. Azure can suspend a running interpreter with its memory. boat counts each create as a start against its plan's start limits.
39th cheapest of 336
$354 a month
13th cheapest of 336
$119 a month
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
All three fit sandboxes for your users. Upstash wakes a paused box on the next request at about a third of Azure's cost, and Azure suspends idle sandboxes with their memory. boat gives each user a full VM, within its plan's start limits.
32nd cheapest of 349
$2,260 a month
4th cheapest of 349
$222 a month
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
158th of 349, with limits
$10,740 a month
343rd of 349, with limits
$8,000 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
All three fit agent evals. Upstash allows 1,000 boxes at once on Pay as You Go, Azure starts at 300 active cores, and boat runs 100 to 2,000 sandboxes by plan.
85th cheapest of 359
$1,728 a month
67th cheapest of 359
$1,011 a month
10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
Neither Azure nor Upstash documents nested virtualization for Android or VM builds, and Upstash does not document Docker inside a box. boat has both, and each job start counts against its plan's start limits.
108th cheapest of 374
$1,046 a month
122nd cheapest of 374
$1,480 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
A flat-price keep-alive box makes Upstash a low-cost light dev box with SSH. Azure bills a running sandbox every second and does not document SSH.
327th of 371, with limits
$262 a month
8th cheapest of 371
$19 a month
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
Computer-use agents need a desktop. Upstash runs Chromium on a virtual display with a view-only live stream, and on Azure you build a desktop into your own image. boat streams a full Linux desktop at 60 fps with computer tools.
58th cheapest of 367
$1,573 a month
123rd of 367, with limits
$76 a month
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
Upstash ships a managed Chromium with AI page actions, CDP, screenshots, recordings and a view-only live view. On Azure you build a browser into your own image. boat gives the agent Chrome on a desktop it can see and click.
129th of 356, with limits
$795 a month
48th of 356, with limits
$38 a month
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
41st cheapest of 343
$400 a month
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
201st of 327, with limits
$8,000 a month
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
255th of 351, with limits
$259 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 requirementNot ranked: misses a requirementNot 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 requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureAzure Container Apps SandboxesUpstash Boxboat
IsolationMicroVM per sandbox with its own kernelDocker container per box on AWSFull VM with its own kernel, on hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Docker insideDepends on the image: azure-dev ships Docker on systemd; the default ubuntu image has only BuildahNot documented; the box is itself a Docker container, and custom images are listed as coming soonDocker, systemd and root on every sandbox
Nested virtualizationNot documentedNot documented; boxes are containers/dev/kvm for Android emulators and VMs
Getting a shellInteractive shell through the aca CLI, SDK or portal; SSH is not documentedSSH through a gateway, plus SDK execSSH, plus CLI and API exec
Biggest machine and diskUp to 16 cores / 32 GiB / 320 GiB diskLarge: 8 vCPU / 16 GB; disks of 10, 20 or 30 GB by sizeUp to 16 vCPU / 32 GB on the $100 plan and above; 51 GB at 4 vCPU, up to 251 GB
Suspend and resumeSuspend with memory and disk; resume in under a second with processes runningPauses itself when idle and keeps its files; storage keeps billing while pausedDisk saved every minute and at each stop; no compute charge while stopped; disk kept at least 14 days
Billing while idleFull tier rate until auto-suspend (default 5 minutes)No CPU charge while a box is idle; RAM is not billedFull rate while the sandbox runs, busy or idle; auto-stop defaults to 1 hour
Wake on requestYes; network traffic or a start command brings a suspended sandbox backYes; a request to a public URL resumes a paused box and waits for the appNo; a stopped sandbox is started by API
ForkSnapshot a running sandbox with its memory and create new sandboxes from itSnapshot a running box's files and start many new boxes from itFork a running sandbox from its last 1-minute disk snapshot
Desktop and browserNo desktop or browser in the public images; you can build one into your own OCI imageManaged Chromium with AI page actions, CDP, screenshots, recordings and a view-only live stream; no desktop or VNC1920x1080, 60 fps desktop with Chrome and computer tools
Inbound accessPublic HTTPS routes per published port; private endpoint from your VNet at extra cost; no public IPHTTPS URL per port, public unless you add a token or basic auth; no raw TCP documentedUp to 50 HTTPS URLs, token-gated by default; public IPv6 with raw ports
Outbound rulesAllow, deny, rewrite and header rules by host, path and method; VNet integrationAllow all, deny all, or allow and deny by domain and CIDR, changeable on a running boxOpen internet, no provider-side allowlist
Coding agentsCopilot CLI and Claude Code images, run through the exec APIClaude Code, Codex, OpenCode and Cursor built in, plus custom agents, with run and stream APIs, webhooks and scheduled promptsSeven harnesses installed, with a prompt, steer and events API
Keeping API keys out of the sandboxYou set it up: an egress Transform rule adds a group secret as a header from outside, one rule per API host; the built-in Copilot and Claude connections put tokens insideHost proxy injects headers into outbound HTTPS on port 443 for any host; set when the box is createdOptional AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests) for supported model providers; switch a credential to another account when credits run out
Regions40 Azure regions, 9 of them in the EUAWS us-east-1; custom regions on EnterpriseGermany, Finland and France; you cannot pick a region; no US or Asia region
Every feature Battleships tracks (43)
FeatureAzure Container Apps SandboxesUpstash Boxboat
Full VM (own kernel)YesNo documented wayYes
Docker insideYesNot publishedYes
Nested virtualizationNot publishedNo documented wayYes
RootYesNot publishedYes
SystemdYesNot publishedYes
Desktop GUIWith your own setupNo documented wayYes
BrowserWith your own setupYesYes
Computer-use APINo documented wayNo documented wayYes
SSHNo documented wayYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesNo documented wayYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo documented way
Wake on requestYesYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistYesYesNo documented way
Secret proxyYesYesYes
Secret proxy for any APIYesYesYes
Preinstalled agentsYesYesYes
Agent harness APINo documented wayYesYes
MCP serverNo documented wayYesNo documented way
GPUNo documented wayNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayYesNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayNo documented wayNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsYesNot publishedYes
Usage per sandbox (API)YesYesYes
Audit logsYesNot publishedNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesYesNo documented way
HIPAAYesNo documented wayNo documented way
EU data residencyYesNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

Azure Container Apps SandboxesNot measured
Upstash BoxNot measured
boat28.06 runs/s

Azure Container Apps Sandboxes and Upstash Box are not in StarSling's CPU benchmark, so we cannot say which is faster. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15. 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. ComputeSDK measured Upstash Box at its default size: a median of 2.34 s to the first command with 100 at once (2026-11-06). Azure and boat are not in ComputeSDK.

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. 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 and Upstash Box are 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.

ScenarioAzure Container Apps Sandboxes, a monthUpstash Box, a monthboat, 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$21 · Pay as You Go$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$21 · Pay as You Go$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$900 · Pay as You Go · 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
$989 · Pay-as-you-go$306 · 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
$2,148 · Pay-as-you-go$1,822 · Pay as You Go$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.

Upstash Box: A standard box is billed for the CPU it actually uses, at $0.10, $0.20 or $0.40 per active CPU hour for Small, Medium and Large, plus $0.10 per GB-month of storage, snapshots included. RAM is free, and Pay as You Go has no monthly fee. A keep-alive box costs a flat $8, $16 or $32 a month whether it is busy or not.

Upstash Box: 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, busy or idle. 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

Upstash does not document Docker inside a box (custom images are listed as coming soon), so the 50-agent scenario does not fit there. Its disks stop at 10, 20 or 30 GB by size (Medium is 20 GB in the docs, 30 GB in the pricing table), and its egress price is not published. Azure bills a running sandbox every second until it suspends, so one agent that never stops costs $262 a month and reaches that 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, so 300 user sandboxes and 1,000 short jobs need a support request 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.

ScenarioAzure Container Apps SandboxesUpstash Boxboat
One coding agent, workdaysNone for this scenario
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
One agent that never stops
  • 3-year commitment
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
50 agents in parallelNone for this scenario
  • not confirmed: Docker inside
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
Sandboxes for your usersNone for this scenario
  • egress price not published
None for this scenario
1,000 short jobs at onceNone for this scenario
  • egress price not published
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use Azure Container Apps Sandboxes when

your team already runs on Azure and wants sandboxes that suspend with their memory, sit behind strict egress rules and VNets, or run in many regions.

  • Memory suspend in under a second. Good for stateful jobs that sleep between requests: a sandbox suspends with its memory and resumes with its processes running.
  • Fine-grained outbound rules. Its egress policy can allow, deny or rewrite outbound requests by host, path and method, and reach your private Azure networks.
  • Inside Azure, in 40 regions. Teams already on Azure get Entra ID, Azure billing and VNets, with sandboxes in 40 regions including 9 in the EU.

Use Upstash Box when

your agents mostly wait, should wake on an incoming request, need coding agents and a managed browser ready to drive from an SDK, and can run in the US.

  • Idle costs no CPU. Good for agents that wait a lot: Upstash bills only the CPU a box uses, RAM is free, and a request wakes a paused box.
  • Coding agents and a browser ready to drive. Claude Code, Codex, OpenCode and Cursor come built in, with run and stream APIs, webhooks and scheduled prompts, next to a managed Chromium.
  • 1,000 boxes at once by default. Pay as You Go allows 1,000 boxes at once without a support request, in AWS us-east-1 close to US services.

Where boat fits

Azure and Upstash are both built for code that runs, sleeps and wakes up, and both cost nothing for CPU while asleep. If your agents do longer real work, like building containers, booting emulators or using a desktop, they need a whole machine. boat gives every agent a full VM with Docker, /dev/kvm, a desktop and coding agents built in, within its plan start limits.

Docker and /dev/kvm on every sandbox

Upstash does not document Docker inside a box, so the 50-agent scenario does not fit there. Azure has Docker only on images like azure-dev, and neither documents /dev/kvm for Android emulators or nested VMs.

A desktop the agent can see and click

Upstash runs Chromium on a virtual display with a view-only live stream, so desktop apps and native dialogs are out of reach. On Azure you build a desktop into your own image. boat streams a Linux desktop at 60 fps with computer tools.

Room for big builds

Upstash disks stop at 30 GB and machines at 8 vCPU / 16 GB. boat gives 51 GB at the default size and up to 251 GB and 16 vCPU / 32 GB on larger sizes.

Use boat when your agents need a whole computer: Docker, emulators, a desktop and a browser, SSH and room for big builds, with coding agents built in, within its plan start limits. Compare it one to one: boat vs Azure Container Apps Sandboxes and boat vs Upstash Box.

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 Upstash Box?

No. Upstash costs less in all five scenarios on this page: $21 against $68 for one coding agent on workdays, and $306 against $989 for sandboxes for your users. Upstash's 50-agent price does not fit, though, because it does not document Docker inside a box. boat is $20 and $200 for those two scenarios.

Which is faster, Azure Container Apps Sandboxes or Upstash Box?

Neither is in StarSling's CPU benchmark, so we cannot say. boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB in StarSling's run of 3 October 2026, on an AMD Ryzen 9 9950X host.

Can Azure Container Apps Sandboxes or Upstash Box run Docker?

On Azure, the azure-dev image ships Docker on systemd, while the default ubuntu image has only Buildah. Upstash does not document Docker inside a box, which is itself a Docker container. boat runs Docker on every sandbox.

Can I SSH into them?

Upstash gives SSH through a gateway. Azure gives an interactive shell through the aca CLI, the SDK or the portal, and does not document SSH. Every boat sandbox takes SSH.

Which one keeps memory when it sleeps?

Azure suspends a sandbox with its memory and disk and resumes it in under a second with processes running. Upstash pauses an idle box and keeps its files. boat saves the disk every minute and at each stop, keeps it for at least 14 days, and a resume is like a reboot.

Where do they run?

Azure Container Apps Sandboxes runs in 40 Azure regions, 9 of them in the EU. Upstash Box runs in AWS us-east-1, with custom regions on Enterprise. boat runs in Germany, Finland and France, and you cannot pick a region.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons