Namespace vs Docker Cloud Sandboxes
Namespace is a build and dev platform: CI runners, caches and Devboxes on Linux, macOS and Windows. Docker Cloud Sandboxes runs the same sbx microVMs you use on your laptop in Docker's cloud, one per coding agent, for up to 24 hours per run.
The companies and products
Namespace
Namespace is a dev platform for fast builds, tests and coding environments: CI runners, build caches and Devboxes, on its own hardware.
Most of Namespace is CI: a faster drop-in for GitHub Actions runners, with Docker, Bazel, Turborepo and Nix caching. Its Devboxes are remote Linux and macOS machines with persistent storage, made for people and AI coding agents. You run Claude Code, Codex, OpenCode, Amp, Copilot or Cursor in persistent Devbox sessions, and Namespace also hosts sessions for Claude Managed Agents, Cursor Cloud Agents, Devin and Amp. It is a different kind of product from boat, so this page compares the part where they overlap: a machine an agent works on.
- Products
- GitHub Actions runners, Docker, Bazel, Turborepo and Nix caching, Devboxes, and a compute API
- Hardware
- Its own hardware in its own racks: AMD EPYC for Linux and Windows, Apple M4 Pro or M5 Max for macOS
- Linux Devboxes
- Run a container image you choose and include Docker; the docs do not say if each one has its own kernel
- Devbox time limit
- 3 hours on Developer and Devbox Plus, 5 on Team, 24 on Business, even while you work; support can raise it to 24 hours at most
- Devbox count limit
- Per user / per workspace: 1/3 on Developer, 3/30 on Team, 5/50 on Business and Devbox Plus; stopped Devboxes count
- Free trial
- 30-day Developer trial with no card
- Compliance
- Trust center lists SOC 2 Type II
Docker Cloud Sandboxes
Docker Cloud Sandboxes runs Docker's sbx coding-agent microVMs on Docker-managed compute instead of your laptop.
Each sandbox is a microVM with its own Linux kernel and its own Docker Engine. You start it from the same sbx CLI you use locally, or from the Sandboxes API, with Claude Code, Codex and other agents ready to run. You can move a sandbox from your laptop to the cloud and back, publish HTTPS ports and SSH in. It launched on September 24, 2026, and it bills pay-as-you-go on a personal Docker account.
- Launched
- September 24, 2026
- Session length
- 1 hour by default, up to 24 hours from creation; with the always-on entitlement, a restart at expiry keeps memory
- Regions
- Not published
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. “87th cheapest of 374” means 86 of the other 373 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 | Namespace: price rank | Docker Cloud Sandboxes: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Both are a compromise for a software factory. Namespace caps Devboxes at 50 per workspace on Business and Devbox Plus, and Docker allows 10 sandboxes at once by default, with higher quotas through Docker. boat is a full match here. | 74th of 365, with limits $3,745 a month | 295th of 365, with limits $4,928 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB Both are a compromise for an assistant that never stops. A Namespace Devbox stops at its plan's limit (24 hours at most), and a Docker run ends 24 hours after creation unless the always-on entitlement restarts it. On a boat paid plan you turn auto-stop off. | 316th of 361, with limits $6,645 a month | 139th of 361, with limits $5,110 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 All three are a compromise for big bursts. Namespace caps Devboxes at 50 per workspace, Docker allows 10 at once by default, and boat refuses starts above 3 times its per-minute limit. | 244th of 336, with limits $250 a month | 239th of 336, with limits $233 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 are a compromise for sandboxes for your users: Namespace caps Devboxes at 50 per workspace, and Docker allows 10 at once by default on one personal account. boat fits, with 300 at once on the $100 plan. | 279th of 349, with limits $2,068 a month | 266th of 349, with limits $1,628 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 | 345th of 349, with limits $9,012 a month | 122nd of 349, with limits $7,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 | 282nd of 359, with limits $1,093 a month | 291st of 359, with limits $1,400 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 Namespace fits CI: its main product is GitHub Actions runners with build caches. Docker sells agent sandboxes, not runners. boat also fits, with Docker and /dev/kvm on every sandbox, but it sells no managed runner or build cache. | 87th cheapest of 374 $765 a month | 300th of 374, with limits $672 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB | 201st of 371, with limits $250 a month | 140th of 371, with limits $204 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 For a Linux computer-use agent both are a compromise. Namespace's click API and VNC desktop work on macOS Devboxes; on a Linux Devbox you install a desktop and VNC in your image. Docker has no display server. boat streams a built-in Linux desktop at 60 fps. | 108th of 367, with limits $1,032 a month | 298th of 367, with limits $1,400 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 On Namespace you install Chrome or Playwright in your Devbox image. Docker's official Playwright kit adds headless Chromium. boat ships Chrome with browser control on its built-in desktop. | 191st of 356, with limits $789 a month | 189th of 356, with limits $700 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 | 191st of 343, with limits $332 a month | 192nd of 343, with limits $350 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 | 225th of 327, with limits $9,012 a month | 190th of 327, with limits $7,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 | 112th of 351, with limits $339 a month | 114th of 351, with limits $350 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 Only Namespace fits: it runs macOS Devboxes and instances on Apple Silicon. Docker Cloud Sandboxes and boat have no macOS. | 6th cheapest of 35 $1,255 a month | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | Namespace | Docker Cloud Sandboxes | boat |
|---|---|---|---|
| Isolation | Linux Devboxes run a container image; the docs do not say if each has its own kernel (a third-party benchmark reports Firecracker) | MicroVM per sandbox with its own Linux kernel and Docker Engine; hypervisor not named | Full VM with its own kernel on a host dedicated to boat; vCPUs are shared |
| CPU benchmark (Node.js V8 Web Tooling, 4 vCPU / 8 GB, StarSling run of 3 October 2026) | 24.90 runs/s, rank 2 of 15 (shared) | Not in the public benchmarks we use | 28.06 runs/s, rank 2 of 15 (shared), on a Ryzen 9 9950X host |
| How long a session can run | Devboxes stop at 3 hours on Developer and Devbox Plus, 5 on Team, 24 on Business, even while you work; support can raise it to 24 at most | 1 hour by default, at most 24 hours from creation; with the always-on entitlement, a restart at expiry keeps memory | No cap once auto-stop is off on a paid plan; auto-stop defaults to 1 hour |
| Machines at once | Devboxes per workspace: 3 on Developer, 30 on Team, 50 on Business and Devbox Plus, stopped ones included | 10 concurrent and 50 stored by default; higher quotas through Docker, not self-serve | 100, 300, 1,000 or 2,000 by plan; the $20 plan includes 12 starts a minute and 200 a day |
| Docker and nested virtualization | Docker in Linux Devboxes; /dev/kvm on Linux compute instances | Its own Docker Engine in each sandbox; nested virtualization not documented | Docker, root, systemd and /dev/kvm on every sandbox |
| Stop, resume and fork | A stopped Devbox keeps its storage until you delete it ($0.20 per GB-month); no fork documented; compute instances suspend and resume with RAM kept | Stop keeps memory and files; snapshot a running sandbox with disk or disk and memory and restore it as a new one | Disk saved every minute and on stop, kept at least 14 days; fork a running sandbox from its last 1-minute snapshot; resume is a reboot |
| Idle stop and wake | Devboxes stop after an idle timeout (15 minutes to 8 hours) and start again when you connect | A timer from creation (1 hour default, 24 hours at most); no idle stop documented | Auto-stop is a timer from start or resume, not an idle check; a running sandbox bills busy or idle |
| Desktop and computer use | macOS Devboxes: screenshot and click API and a VNC desktop. Linux Devboxes: install a desktop and VNC in your image. Compute instances: VNC and RDP | No display server; headless Chromium through Docker's official Playwright kit | Built-in Linux desktop and Chrome at 1920x1080, 60 fps, with computer tools for agents |
| Reaching the sandbox | HTTPS URLs that need a Namespace login; TCP through a running CLI port-forward; no public IP | Public HTTPS URL per published port, not a TCP tunnel; SSH with Docker-issued certificates | Up to 50 HTTPS URLs, token-gated by default; SSH over IPv4 through a shared host and port; raw ports over IPv6 on some sandboxes; no dedicated IPv4 |
| Outbound rules | Egress policies per Devbox blueprint, runner or instance: block, advisory or allow by domain | Allow and deny rules by host at a proxy, with allow-all, balanced and deny-all presets | Open internet on every plan; no provider-side allowlist; egress not billed |
| Keeping keys out of the sandbox | Egress rules inject a header from Namespace Vault, resolved outside the workload | Cloud proxy sets the auth header for AI services and custom hosts; the sandbox sees a placeholder | Optional AI credentials proxy ($1 a day it is on, plus $1 per 1,000 requests) for model providers and HTTPS APIs you register |
| Coding agents | You run Claude Code, Codex, OpenCode, Amp, Copilot or Cursor in persistent Devbox sessions; hosts Claude Managed Agents, Cursor, Devin and Amp sessions; no API to prompt or steer an agent from outside | Claude Code, Codex, Copilot, OpenCode and more, run from the sbx CLI; a Sandboxes API runs processes and moves files, with no agent prompt or events API | Seven harnesses installed, including Claude Code, Codex and OpenCode, with an API to prompt, steer and stream events |
| Operating systems | Linux, macOS on Apple Silicon, and Windows on Team plans and up | Linux only, amd64 or arm64 by account | Linux only; Windows programs run through Wine |
| Laptop and cloud | Cloud only | Same microVM and CLI locally or in the cloud; move a sandbox either way | Cloud only |
Every feature Battleships tracks (43)
| Feature | Namespace | Docker Cloud Sandboxes | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Yes | No documented way | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Not published | Yes |
| Desktop GUI | Yes | No documented way | Yes |
| Browser | With your own setup | With your own setup | Yes |
| Computer-use API | Yes | No documented way | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | Yes | Yes |
| Fork/clone | No documented way | Yes | Yes |
| Live fork (no pause) | No documented way | Yes | Yes |
| Memory fork | No documented way | Yes | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | Yes | No documented way | No documented way |
| Wake on request | Yes | Not published | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | Yes | Not published | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | Yes | Yes | Yes |
| Preinstalled agents | Yes | Yes | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | Yes | Yes | No documented way |
| GPU | No documented way | No documented way | No documented way |
| Windows | Yes | No documented way | No documented way |
| Arm64 | Yes | Yes | 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) | No documented way | No documented way | Yes |
| Audit logs | Yes | Not published | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | No documented way | No documented way |
| HIPAA | No documented way | No documented way | No documented way |
| EU data residency | Yes | Not published | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
In StarSling's run of 3 October 2026 (run 37073680030), the Node.js V8 Web Tooling benchmark at 4 vCPU / 8 GB did 28.06 runs/s on boat and 24.90 on Namespace. Both share rank 2 of 15, so the run cannot separate them. Docker Cloud Sandboxes is not in the public benchmarks we use, so we cannot say which is faster. StarSling does not name the Namespace product it tested. 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.
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. Namespace measured on: Linux compute instance (unit-minutes, PAYG/overage $0.0015). 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. Docker Cloud 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 | Namespace, a month | Docker Cloud 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 | $300 · Devbox on Business | $49 · Docker Agentic Platform (pay-as-you-go) | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $426 · Devbox on Business · with limits | $204 · Docker Agentic Platform (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 | $2,448 · Devbox on Business | $2,464 · Docker Agentic Platform (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 | $1,264 · Devbox Plus · with limits | $700 · Docker Agentic Platform (pay-as-you-go) · with limits | $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 | $3,287 · Devbox Plus · with limits | $1,400 · Docker Agentic Platform (pay-as-you-go) · with limits | $8,800 · $2000/mo · with limits |
Namespace: Devboxes are billed in Devbox Minutes at $0.004 each: a 4 vCPU / 8 GB (size S) Devbox uses one a minute. Pay as you go, or Devbox Plus at $250 a month for 50,000 minutes and 400 GB-month of storage. Team ($100) and Business ($250) plan minutes do not cover Devboxes, but you need those plans for longer sessions and more Devboxes. Storage costs $0.20 per GB-month used.
Docker Cloud Sandboxes: Docker bills per second for the size you pick, from $0.07 an hour for 1 vCPU / 2 GiB to $1.12 an hour for 16 vCPU / 32 GiB, with no monthly fee. A 4 vCPU / 8 GiB sandbox costs $0.28 an hour. A stopped sandbox costs nothing, and volumes and egress are free. New accounts get a one-time credit.
Docker Cloud Sandboxes: Plans cost $20, $100, $500 or $2,000 a month. The whole plan price comes back as VM time for that month; unused time does not carry over. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs. 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. The $20 plan includes 200 starts a day; extra starts cost $0.03 to $0.07 each. A card is required, also for the 7-day free trial.
Limits in those scenarios
Namespace stops a Devbox at 3 hours on Developer and Devbox Plus, 5 on Team and 24 on Business, and caps Devboxes at 50 per workspace, stopped ones included. Docker ends a run 24 hours after creation unless the always-on entitlement restarts it, and allows 10 sandboxes at once by default. So the agent that never stops, sandboxes for your users and 1,000 short jobs at once fit neither by default. 50 agents in parallel fit Namespace Business but not Docker's default quota. boat has its own limits: auto-stop is on by default (1 hour), a stopped disk is kept for at least 14 days unless you save a snapshot, resume is a reboot, and starts above 3 times the per-minute limit fail, so 1,000 jobs at once do not fit even on the $2,000 plan.
| Scenario | Namespace | Docker Cloud 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 |
| Sandboxes for your users |
|
| None for this scenario |
| 1,000 short jobs at once |
|
|
|
Which one should you use?
Use Namespace when
you need macOS or Windows machines, faster GitHub Actions runners with build caches, egress allowlists, or Devboxes for people that stop when idle.
- macOS and Windows. Useful if your agents build iOS or Mac apps or test on Windows: Namespace runs macOS on Apple Silicon and Windows machines.
- CI runners and build caches. Useful if you want faster GitHub Actions: Namespace is a drop-in runner with Docker, Bazel, Turborepo and Nix caching.
- Boxes that stop when idle. Useful for dev boxes people use on and off: a Devbox stops after an idle timeout, keeps its storage and starts again when you connect.
Use Docker Cloud Sandboxes when
you already run agents in sbx on your laptop and want a few to keep going in the cloud, with memory kept across stops and no monthly fee.
- Stop and fork with memory. Useful for agents that pause between steps: a stopped sandbox comes back with its memory, and a running one can be copied with it.
- The same sandbox on your laptop. If you already run sbx locally, the cloud is the same microVM and CLI, and you can move a sandbox between them.
- No monthly fee. Useful for light use: Docker bills per second with no plan fee, and new accounts get a one-time credit.
Where boat fits
If you run Linux coding agents that work for hours or days, Namespace and Docker each end a run within 24 hours by default. boat gives each agent a full VM with no session cap once auto-stop is off, /dev/kvm, a built-in desktop and an API to drive the agent inside. Namespace stays the pick for macOS, Windows and CI runners, and Docker for memory kept across stops.
No clock on the session
A Namespace Devbox stops at 3, 5 or 24 hours by plan. A Docker run ends 24 hours after creation unless its always-on entitlement restarts it. On a boat paid plan you turn auto-stop off (default 1 hour). A boat resume is also a reboot, so this matters only for runs longer than those caps.
A whole machine, screen included
Docker's sandboxes have no display server and do not document /dev/kvm. Namespace's click API and VNC desktop work on macOS Devboxes; on Linux you install a desktop yourself. boat ships a 60 fps Linux desktop with Chrome and /dev/kvm on every sandbox.
Agents you drive from outside
On Docker you start agents from the sbx CLI, and on Namespace you start each agent in a Devbox session. Neither documents an API to prompt an agent and stream its events. boat installs seven harnesses with that API.
Use boat when your Linux agents run for days or by the dozen, need Docker with /dev/kvm, a desktop or a browser, or have to be driven from your own app through an API, at $0.036 an hour for 4 vCPU / 8 GB. Compare it one to one: boat vs Namespace and boat vs Docker Cloud 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 Namespace cheaper than Docker Cloud Sandboxes?
For one coding agent on workdays, Docker costs about $49 a month and Namespace $300, because an 8-hour session needs Namespace Business. 50 agents in parallel cost $2,448 on Namespace Business and do not fit Docker's default 10-sandbox quota. boat costs $20 and $317 for those two.
Which is faster, Namespace or Docker Cloud Sandboxes?
Docker Cloud Sandboxes is not in the public benchmarks we use, so we cannot say. In StarSling's run of 3 October 2026, Namespace did 24.90 V8 Web Tooling runs/s at 4 vCPU / 8 GB and boat did 28.06. Both share rank 2 of 15, so the run cannot separate them.
Can either run longer than 24 hours?
Not in one run by default. A Namespace Devbox stops at 3, 5 or 24 hours by plan. A Docker run ends 24 hours after creation; with the always-on entitlement, a restart at expiry keeps its memory. boat has no session cap once you turn auto-stop off on a paid plan.
Can Namespace and Docker Cloud Sandboxes run Docker inside?
Yes. Docker gives each microVM its own Docker Engine, and Namespace Linux Devboxes include Docker, with /dev/kvm on Linux compute instances. boat has Docker, root, systemd and /dev/kvm on every sandbox.
Does either run macOS or Windows?
Only Namespace: it runs macOS on Apple Silicon and Windows on Team plans and up. Docker Cloud Sandboxes and boat are Linux only; boat runs Windows programs through Wine.
Where does my data run?
boat sandboxes run on machines in Germany, Finland and France, and you cannot pick a region. Snapshot copies can be stored outside the EU. Namespace runs in several regions; keeping every workload inside one region needs its Enterprise plan. Docker does not publish its regions.
Try boat
Install the CLI, then run boat new.
7-day free trial