Koyeb vs Azure Container Apps Sandboxes
Both start each sandbox in its own microVM and put it to sleep when idle. Koyeb adds GPUs, bigger machines and regions in the EU, US and Asia. Azure suspends a sandbox with its memory, wakes it in under a second and runs inside your Azure subscription.
The companies and products
Koyeb
Koyeb is a serverless cloud for apps, inference and sandboxes. In February 2026 it agreed to join Mistral AI.
A Koyeb sandbox is a Koyeb service: a microVM that starts from any Docker image. You drive it from Python or JavaScript SDKs or the Koyeb CLI: run commands, read files, expose a port and take snapshots. The default image comes with four coding agents. A sandbox can scale to zero when idle and wake on the next request, on CPU or GPU instance types. It suits teams that run AI agents or untrusted code next to apps they already host on Koyeb.
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.
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. “6th cheapest of 336” means 5 of the other 335 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 | Koyeb: price rank | Azure Container Apps Sandboxes: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Azure fits a software factory (25th), with Docker and systemd in images such as azure-dev. Koyeb documents neither Docker inside a sandbox nor nested virtualization (65th, compromise). boat ranks 8th, with /dev/kvm for emulators too. | 92nd of 365, with limits $366 a month | 33rd cheapest of 365 $5,276 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 194th of 361, with limits $923 a month | 52nd cheapest of 361 $6,780 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: Koyeb ranks 5th at $66 a month and sleeps after 5 idle minutes, and Azure 32nd at $354, suspending with memory and resuming in under a second. boat's start limits make big bursts a compromise (130th). | 6th cheapest of 336 $66 a month | 39th cheapest of 336 $354 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 Both fit sandboxes for your users: Koyeb ranks 6th at $495 a month and Azure 27th at $2,260, and Azure keeps each user's memory across a suspend. boat ranks 2nd at $209, with HTTPS on up to 50 ports per sandbox. | 8th cheapest of 349 $495 a month | 32nd cheapest of 349 $2,260 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 | 233rd of 349, with limits $1,631 a month | 158th of 349, with limits $10,740 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 Both fit agent evals: Koyeb ranks 16th at $429 a month and can give an eval a GPU, and Azure 55th at $1,728 can seed many sandboxes from one memory snapshot. boat ranks 8th at $200. | 27th cheapest of 359 $429 a month | 85th cheapest of 359 $1,728 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 Azure fits CI runners (80th), and Koyeb is a compromise (104th) because its fitting price is a negotiated reservation. Neither documents /dev/kvm for Android or VM builds. boat ranks 2nd at $86. | 143rd of 374, with limits $88 a month | 108th cheapest of 374 $1,046 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. Neither Koyeb nor Azure documents SSH, and Koyeb's local disk is lost on redeploy unless you attach a volume; both are compromises. boat ranks 13th at $26. | 232nd of 371, with limits $37 a month | 327th of 371, with limits $262 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 Azure fits computer use (40th) with a desktop you build into your own image and publish on an HTTPS port. On Koyeb you add a desktop and VNC to your own image too (80th, compromise). boat ranks 8th with a built-in 60 fps desktop. | 128th of 367, with limits $123 a month | 58th cheapest of 367 $1,573 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 | 237th of 356, with limits $123 a month | 129th of 356, with limits $795 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 | 242nd of 343, with limits $89 a month | 112th cheapest of 343 $561 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 | 67th of 327, with limits $1,683 a month | 240th of 327, with limits $10,956 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 | 261st of 351, with limits $299 a month | 30th cheapest of 351 $517 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 Koyeb ranks 3rd, with GPU instances from an RTX 4000 SFF Ada up to H100, H200 and B200. Azure Container Apps Sandboxes and boat have no GPU. | 3rd cheapest of 102 $628 a month | 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 | Koyeb | Azure Container Apps Sandboxes | boat |
|---|---|---|---|
| Isolation | Cloud Hypervisor microVM per instance | MicroVM per sandbox with its own kernel | Full VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared |
| Biggest machine | Instance types up to 40 vCPU / 128 GB, and larger GPU types | Tiers XS to 3XL, up to 16 vCPU / 32 GiB | Up to 16 vCPU / 32 GB with a 251 GB disk, on the $100 plan and above |
| GPUs | RTX 4000 SFF Ada up to H100, H200 and B200, and multi-GPU | None | None on any size |
| Disk that survives | Local disk is lost on redeploy and in Deep Sleep; SDK snapshots save the filesystem for new sandboxes; volumes (preview, 1 to 10 GB, not on eco instances) persist | A suspended or stopped sandbox keeps its disk | Disk saved every minute and at each stop; no compute charge while stopped; kept at least 14 days, longer as a saved snapshot |
| Sleep and wake | Scales to zero after 5 idle minutes or more and wakes on the next request; Light Sleep wakes in about 200 ms (preview); not on eco instances | Auto-suspend with memory after an idle timeout (5 minutes by default); traffic or a start command resumes it in under a second with processes running | No wake on request; auto-stop is a timer (default 1 hour), not an idle check; a resume is like a reboot |
| Snapshots and fork | SDK snapshots of the filesystem, or with running processes, then new sandboxes from them | Snapshot a running sandbox with its memory and create new sandboxes from it | Fork a running sandbox from its last 1-minute disk snapshot (no memory) |
| Docker and nested virtualization | Starts from any Docker image; Docker inside a sandbox and nested virtualization not documented | Depends on the image: azure-dev ships Docker on systemd; the default ubuntu image has only Buildah; nested virtualization not documented | Docker, systemd and /dev/kvm for Android emulators and VMs on every sandbox; you cannot boot your own Docker image |
| Getting a shell | Commands through the Python and JavaScript SDKs and the CLI; SSH not documented | Interactive shell through the aca CLI, SDK or portal; SSH not documented | SSH, plus CLI and API exec |
| Inbound access | One exposed HTTPS port at a time, plus an optional TCP proxy to one port (preview); no dedicated IP | Public HTTPS routes per published port; private endpoint from your VNet at extra cost; no public IP | Up to 50 HTTPS URLs, token-gated by default; SSH; public IPv6; the IP changes at each resume |
| Outbound rules | Block all outbound traffic, or allow only listed IPs and CIDRs | Egress policy with allow, deny, rewrite and header rules by host, path and method; VNet integration | Open internet, no provider-side allowlist |
| Desktop and browser | No desktop or browser preinstalled; you add them to your own Docker image | No desktop or browser in the public images; you can build one into your own OCI image and publish it on an HTTPS port | 1920x1080 Linux desktop and Chrome at 60 fps, with computer-use tools |
| Coding agents | Default image preinstalls Mistral Vibe, Codex, Gemini and OpenCode, run through the command API | Copilot CLI and Claude Code images, run through the exec API | Seven agents installed, with a prompt, steer and events API |
| Keeping API keys out of the sandbox | Secrets are set as environment variables inside the service | An egress Transform rule adds a group secret or managed-identity token as a header, outside the sandbox; the built-in Copilot and Claude connections put tokens inside | Optional AI credentials proxy ($1 a day on, plus $1 per 1,000 requests): real keys of supported providers stay out; other secrets still enter |
| Regions | EU, US and Asia; you pick the region | 40 Azure regions, 9 of them in the EU | Germany, Finland and France; you cannot pick a region; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Koyeb | Azure Container Apps Sandboxes | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Not published | Yes | Yes |
| Nested virtualization | No documented way | Not published | Yes |
| Root | Not published | Yes | Yes |
| Systemd | Not published | Yes | Yes |
| Desktop GUI | No documented way | With your own setup | Yes |
| Browser | No documented way | With your own setup | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | No documented way | No documented way | Yes |
| Persistent disk | With your own setup | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | Yes | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Not published | Yes | 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 | Yes | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | Yes | No documented way | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | No documented way | Yes | Yes |
| Secret proxy for any API | No documented way | Yes | Yes |
| Preinstalled agents | Yes | Yes | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | Yes | No documented way | No documented way |
| GPU | Yes | 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 | Yes | No documented way | No documented way |
| BYOC | Yes | 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 | No documented way | Yes | Yes |
| Usage per sandbox (API) | No documented way | Yes | Yes |
| Audit logs | Yes | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | No documented way | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Koyeb and Azure Container Apps Sandboxes are not in the public benchmarks we use, 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 that 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. Koyeb publishes a CPU share of at least 0.25 dedicated vCPU per GB of memory, bursting to all cores, and Azure says it resumes a suspended sandbox in under a second.
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. Koyeb and Azure Container Apps Sandboxes 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.
| Scenario | Koyeb, a month | Azure Container Apps 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 | $29 · Pro | $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 | $57 · Pro | $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 | $475 · Pro · with limits | $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 | $329 · 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 | $485 · Scale · with limits | $2,148 · Pay-as-you-go | $8,800 · $2000/mo · with limits |
Koyeb: Koyeb bills each instance per second at a fixed price per instance type: eco-xlarge (4 vCPU / 8 GB, 20 GB disk) costs $0.0576 an hour. The idle period before sleep bills at the full rate, and Deep Sleep has no charge. Pro costs $29 a month with $10 of usage included, and Scale $299 with $100 included; the rest of the fee is not credit.
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 (5 minutes by default). The XL tier (4 cores / 8 GiB) is $0.432 an hour at the East US rates. There is no plan fee, and stopped sandboxes pay no CPU or memory. Storage for images, snapshots and volumes will be billed per GiB (announced as coming soon).
Azure Container Apps Sandboxes: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A 4 vCPU / 8 GB sandbox 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. A stopped sandbox has no compute charge and keeps its disk for at least 14 days; saved snapshots above the included count and the AI credentials proxy still charge. A card is required, also for the 7-day trial.
Limits in those scenarios
Koyeb's priced shape is eco-xlarge, which has a 20 GB disk and takes no volume, and Koyeb does not document Docker inside a sandbox, so the 50-agent fleet is not confirmed there. Azure bills a running sandbox every second until it suspends, so the always-on agent needs a 3-year savings plan to reach $262 a month, and Azure does not state that the plan covers Sandboxes. Azure's default quota is 300 active cores per region and subscription, raised by support request. For 1,000 short jobs at once, Azure fits at $2,148 after a quota raise. boat does not fit that burst: its $2,000 plan includes 90 starts a minute, charges for extra starts and refuses starts above 270 a minute.
| Scenario | Koyeb | Azure Container Apps Sandboxes | boat |
|---|---|---|---|
| One coding agent, workdays |
| 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 |
| 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 Koyeb when
your sandboxes need GPUs or big CPU machines, start from your own Docker image, sleep most of the time and wake on a request, or sit next to apps you already run on Koyeb.
- GPUs in the same platform. Useful when an agent or eval needs a GPU: Koyeb runs instances from RTX 4000 cards up to H100, H200 and B200.
- Bigger CPU machines, lower bills. For heavy jobs, Koyeb instance types go up to 40 vCPU / 128 GB, and it costs less than Azure in every scenario both fit here.
- Next to apps you already host. A Koyeb sandbox is a Koyeb service, so teams already serving apps or inference there keep one platform and one bill.
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, or handle large bursts of short jobs.
- Suspend with memory, wake on traffic. Good for stateful jobs that sleep between requests: a sandbox keeps its memory and resumes in under a second.
- Fine-grained outbound rules. Its egress policy can allow, deny or rewrite each outbound request by host, path and method, and add secrets from outside the sandbox.
- Inside Azure, in 40 regions. Teams already on Azure get Entra ID, Azure billing, VNets and their own OCI images, in 40 regions on six continents.
Where boat fits
Koyeb and Azure are both built for sandboxes that sleep between requests. If your agents instead work for hours on one machine, building, running Docker, starting emulators and using a browser, look at boat: each agent gets a full VM that saves its disk, with a desktop, SSH and coding agents installed. boat keeps the disk only, not memory, has no GPU and runs only in Germany, Finland and France.
A whole computer with /dev/kvm and SSH
boat gives root, systemd, Docker, SSH and /dev/kvm on every sandbox. Neither Koyeb nor Azure documents nested virtualization or SSH, so Android emulators and VMs need another place.
A screen and a browser for every agent
Every boat sandbox streams a 60 fps Linux desktop with Chrome and computer-use tools. On Koyeb and Azure you build a browser, a virtual display and a stream into your own image.
boat's own limits
boat has no GPU, no wake on request, no memory suspend, no outbound allowlist and no US or Asia region. A sandbox stops after 1 hour by default unless you change auto-stop. Starts are capped per plan, so 1,000 short jobs at once fit Azure but not any boat plan.
Use boat when your agents need a whole computer for hours: a disk saved every minute, Docker, /dev/kvm, SSH, a desktop and a browser, with coding agents installed. Compare it one to one: boat vs Koyeb and boat vs Azure Container Apps 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 Koyeb cheaper than Azure Container Apps Sandboxes?
Yes, where both fit. Sandboxes for your users cost $329 a month on Koyeb and $989 on Azure. One agent that never stops costs $57 on Koyeb, on a 20 GB disk, and $262 on Azure with a 3-year savings plan. boat comes to $200 and $26 for those two. For 50 agents in parallel, Azure fits at $3,421, and Koyeb is not confirmed because it does not document Docker inside a sandbox. For 1,000 short jobs at once, only Azure fits, after a quota raise.
Which is faster, Koyeb or Azure Container Apps Sandboxes?
Neither is in the public benchmarks we use, so we cannot say. In StarSling's run of 3 October 2026, boat did 28.06 runs/s at 4 vCPU / 8 GB, on a Ryzen 9 9950X host. boat does not promise a CPU model.
Which one keeps my files and memory when it sleeps?
Azure suspends a sandbox with its memory and disk and resumes running processes in under a second. On Koyeb the local disk is lost on redeploy and in Deep Sleep, so you take an SDK snapshot of the filesystem, optionally with running processes, or attach a volume. boat saves the disk every minute and at each stop, but a resume boots the machine again.
Can I run Docker or Android emulators in Koyeb or Azure?
Koyeb starts each sandbox from any Docker image, but does not document Docker inside a sandbox. On Azure the azure-dev image ships Docker, while the default ubuntu image has only Buildah. Neither documents /dev/kvm, which Android emulators and VMs need. boat runs Docker on every sandbox and exposes /dev/kvm.
Which one has GPUs?
Koyeb runs instances from an RTX 4000 SFF Ada up to H100, H200 and B200, billed per second. Azure Container Apps Sandboxes and boat have no GPU.
Is boat SOC 2 compliant?
SOC 2 is in progress; boat has no SOC 2 report today. boat shows live status at status.ascii.dev and its data retention policy at docs.boat.dev/data-retention.
Try boat
Install the CLI, then run boat new.
7-day free trial