GitHub Codespaces vs Ona
GitHub Codespaces opens a ready Linux dev container from any GitHub repository, self-serve, and stops it after 12 hours at most. Ona, formerly Gitpod and now part of OpenAI, runs governed dev environments with its Codex Agent in your own AWS or GCP account. Since Ona Cloud and Core shut down on October 31, 2026, Ona sells only Enterprise, through sales.
The companies and products
GitHub Codespaces
GitHub Codespaces is GitHub's cloud development environment: a ready-to-code Linux machine for a repository, opened in the browser, VS Code or the GitHub CLI.
Codespaces is a different kind of product from boat: a dev environment for people who work on a GitHub repository, not a sandbox API for agents. Each codespace is a Docker container built from the repo's dev container config. It runs on its own newly built VM on Azure, with 2 to 32 cores. It is built for developers and teams who want every contributor to start from the same setup, with prebuilds, port forwarding and GitHub billing.
Ona
Ona, formerly Gitpod, is a platform for cloud dev environments and background coding agents, and is now part of OpenAI.
Ona is a different kind of product from boat: a dev-environment platform, not a sandbox API. Each task or developer gets an isolated VM built from a Dev Container config. People open it in a browser IDE, VS Code or JetBrains, and Ona's Codex Agent can plan, code, test and open pull requests in it. Ona has a built-in web browser that its AI can drive, prebuilds and Enterprise warm pools. It is built for engineering teams who want the same governed environment for every developer and agent. Since Ona Cloud shut down on October 31, 2026, every customer runs it in their own AWS or GCP account on an Enterprise contract.
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. “290th cheapest of 365” means 289 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 | GitHub Codespaces: price rank | Ona: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Both give an agent Docker in a dev container, and neither documents /dev/kvm. A codespace also stops at 12 hours. boat is a full VM with /dev/kvm and no session cap once auto-stop is off on a paid plan. | 290th of 365, with limits $4,618 a month | 334th of 365, with limits $7,315 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB Ona can keep an environment up when auto-stop is set to Never. Every codespace stops after 12 hours at most. On boat, turn auto-stop off on a paid plan (default 1 hour). | 320th of 361, with limits $6,970 a month | 147th of 361, with limits $8,504 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 | 283rd of 336, with limits $619 a month | 326th of 336, with limits $5,320 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 Neither is built to hand machines to your own users. GitHub does not publish how many codespaces can run at once, and Ona's per-user policy defaults to 10 running environments (admins can set 1 to 100). | 276th of 349, with limits $1,964 a month | 325th of 349, with limits $5,988 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 | 276th of 349, with limits $9,489 a month | 277th of 349, with limits $9,773 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 | 295th of 359, with limits $1,519 a month | 332nd of 359, with limits $5,768 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 copies a running machine. Codespaces starts each run from a dev container config or a prebuild. Ona starts from a prebuild, or an Enterprise warm pool hands out a ready environment in about 10 seconds. boat forks a running sandbox; each fork counts as a start. | 317th of 374, with limits $909 a month | 366th of 374, with limits $5,461 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Both are full cloud IDEs with dev containers and prebuilds. Codespaces is self-serve but stops at 12 hours. Ona has no hard session cap and sells Enterprise through sales. | 144th of 371, with limits $270 a month | 371st of 371, with limits $5,140 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 A codespace can add a basic noVNC desktop through the desktop-lite add-on. Ona has no full desktop, but its AI can drive a built-in browser inside the environment. boat streams a 60 fps desktop with Chrome and computer tools. | 297th of 367, with limits $1,367 a month | 355th of 367, with limits $5,691 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 | 306th of 356, with limits $678 a month | 219th of 356, with limits $5,346 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 | 324th of 343, with limits $922 a month | 220th of 343, with limits $5,468 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 | 279th of 327, with limits $18,637 a month | 261st of 327, with limits $14,360 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 On both, every copy is built again from a config, a prebuild or a warm pool. boat can fork one prepared sandbox into many while it runs; each fork counts as a start. | 284th of 351, with limits $445 a month | 150th of 351, with limits $5,228 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 | GitHub Codespaces | Ona | boat |
|---|---|---|---|
| Isolation | A Docker container on its own newly built VM, with its own virtual network | An isolated VM with dedicated compute, built from a Dev Container config | Full VM with its own kernel, on boat's own AMD Ryzen 7 9700X and Ryzen 9 9950X hosts; shared vCPUs |
| How long it runs | Stops after 30 idle minutes by default (up to 240) and after 12 hours at most, even while in use | No hard cap; stops after 30 idle minutes by default; background work does not count; can be set to Never | No cap once auto-stop is off on a paid plan; auto-stop defaults to 1 hour, up to 30 days |
| Docker and nested virtualization | Docker and sudo inside the dev container; /dev/kvm is not documented | Docker and root inside the Dev Container; nested virtualization not documented on its VM classes | Docker, root, systemd and /dev/kvm on every sandbox |
| Desktop and computer use | VS Code, JupyterLab and a terminal; a noVNC desktop through the desktop-lite add-on, which you configure | No full desktop; a built-in browser its AI can drive; browser IDE, VS Code and JetBrains | Built-in desktop and Chrome at 1920x1080 and 60 fps, computer tools for agents and an embeddable stream |
| Files after a stop | Files are kept and storage is billed; processes end; stopped codespaces are deleted after 30 days by default | Disk persists across stops, on your cloud bill; Enterprise archives a stopped environment after 3 days by default (admins can set 1 to 30) | Disk saved every minute and at each stop; no compute charge while stopped; disk kept at least 14 days, longer with a saved snapshot |
| Fork | No copy or snapshot endpoint; new codespaces start from a repo, branch, pull request or prebuild | No environment copy; create a project from an environment's config; Enterprise warm pools start a new environment in about 10 seconds | Fork a running sandbox from its last 1-minute disk snapshot; saved snapshots as templates |
| Starting point | Dev container config in the repository, with prebuilds built by GitHub Actions | Dev Container config per repo, with prebuilds that snapshot the whole Dev Container filesystem, and Enterprise warm pools | boat's image or a saved snapshot, shareable by code; you cannot boot your own Docker or OCI image |
| Buying it | Self-serve on any GitHub account; personal Free accounts get 120 core-hours a month | Ona Cloud and Core shut down on October 31, 2026; Enterprise only, through sales | Self-serve plans from $20 a month, all of it VM time for that month; 7-day trial with a card |
| Driving it from code | REST API and GitHub CLI to create, start, stop and delete; commands run over SSH | Python, TypeScript and Go SDK and a CLI for external agents such as Claude Code, on Enterprise, Ona's only plan | API, SDK and CLI to create, fork, stop and run commands, on every plan |
| Coding agents | GitHub Copilot as a VS Code extension; other agents you install yourself | Managed Codex Agent started from chat, Slack, a pull request, a Linear issue or an automation; you install other agents yourself | Seven harnesses installed, among them Claude Code, Codex and OpenCode, with a prompt, steer and events API |
| Keeping keys out of the sandbox | Secrets are copied into the codespace as environment variables | Secrets injected as environment variables or files; OIDC for short-lived cloud credentials | Optional AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests); with it on, real keys of supported providers stay outside the sandbox |
| Reaching the sandbox | A URL per forwarded port, private, organization or public; SSH; no public IP | HTTPS URL per port for you, your organization or everyone; SSH; no raw TCP or public IP documented | Up to 50 HTTPS URLs, token-gated by default; SSH; raw ports over IPv6 on sandboxes with no IPv4 of their own |
| GPUs | No GPU machine types in current docs | GPU instance types on Enterprise runners, such as one NVIDIA A10G with 16 vCPU and 64 GB | No GPU on any size |
| Regions and deployment | GitHub's cloud in US East, US West, Europe West and Southeast Asia | Enterprise runners in your own AWS or GCP account, in many regions; Ona Cloud shut down on October 31, 2026 | Germany, Finland and France; you cannot pick one; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | GitHub Codespaces | Ona | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Not published | No documented way | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Not published | Yes |
| Desktop GUI | With your own setup | No documented way | Yes |
| Browser | No documented way | Yes | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | No documented way | No documented way | Yes |
| Fork/clone | No documented way | No documented way | Yes |
| Live fork (no pause) | No documented way | No documented way | Yes |
| Memory fork | No documented way | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | No documented way | Yes | Yes |
| Idle auto-stop | Yes | Yes | No documented way |
| Wake on request | No documented way | No documented way | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No documented way | No documented way | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | No documented way | No documented way | No documented way |
| Secret proxy | No documented way | No documented way | Yes |
| Secret proxy for any API | No documented way | No documented way | Yes |
| Preinstalled agents | No documented way | Yes | Yes |
| Agent harness API | No documented way | Yes | Yes |
| MCP server | No documented way | No documented way | No documented way |
| GPU | No documented way | Yes | 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 | Yes | 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 | Yes | Yes |
| Usage per sandbox (API) | No documented way | No documented way | Yes |
| Audit logs | Yes | No documented way | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | No documented way | No documented way | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
GitHub Codespaces and Ona are not in the public benchmarks we use, so we cannot say which is faster. For reference, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15 in StarSling's run of 3 October 2026 (run 37073680030). 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.
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. GitHub Codespaces and Ona 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 | GitHub Codespaces, a month | Ona, 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 | $51 · Personal account: GitHub Free | $5,030 · Enterprise (AWS Marketplace 12-month contract) · with limits | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $270 · Personal account: GitHub Free · with limits | $5,140 · Enterprise (AWS Marketplace 12-month contract) · 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,019 · Personal account: GitHub Free | $6,521 · Enterprise (AWS Marketplace 12-month contract) · 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 | $850 · Personal account: GitHub Free · with limits | $5,432 · Enterprise (AWS Marketplace 12-month contract) · 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 | $1,889 · Personal account: GitHub Free · with limits | $5,955 · Enterprise (AWS Marketplace 12-month contract) · with limits | $8,800 · $2000/mo · with limits |
GitHub Codespaces: Codespaces bills $0.09 per core-hour while a codespace is active, used or not, plus $0.07 per GB-month of storage while it exists, stopped too. There is no 4-core machine with 8 GB, so a 4 vCPU / 8 GB job is priced on the 4-core 16 GB machine. Personal accounts get a free monthly quota, and organizations do not.
Ona: Ona Cloud and Core shut down on October 31, 2026, so Ona prices here use its Enterprise listing on AWS Marketplace: a 12-month, $60,000 contract, plus compute on your own AWS bill. Real Enterprise prices are negotiated with sales.
Ona: 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 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs, busy or idle. A stopped sandbox has no compute charge, and boat keeps its disk for at least 14 days. Saved snapshots above the included count and the optional AI credentials proxy still charge while sandboxes are stopped. The $20 plan includes 12 starts a minute, 60 an hour and 200 a day; create, fork and resume each count as one start, and an extra start costs $0.03 to $0.07. A card is required, also for the 7-day trial.
Limits in those scenarios
Every codespace stops after 12 hours at most, so the always-on price assumes a script that restarts it. GitHub does not publish how many codespaces can run at once, so 300 user sandboxes and 1,000 short jobs are not confirmed. No Ona scenario fits as published, because Ona sells only Enterprise, through sales. Ona publishes no Enterprise concurrency limit, so the table assumes 3 environments at once. boat's limits: auto-stop defaults to 1 hour, and each plan caps starts. For 1,000 short jobs at once, even the $2,000 plan needs paid extra starts and refuses starts above 270 a minute, so boat does not fit. boat has no US or Asia region and no GPU.
| Scenario | GitHub Codespaces | Ona | 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 GitHub Codespaces when
your developers want a ready VS Code environment for a GitHub repository, self-serve, in the US, EU or Asia, and sessions under 12 hours are fine.
- Built into GitHub. Useful if your team lives on GitHub: open a ready codespace from any repo, branch or pull request.
- Self-serve, with free hours. Useful for small teams and personal work: no sales call, and a GitHub Free account includes 120 core-hours a month.
- Regions in the US and Asia. Useful if your developers sit outside Europe: codespaces run in US East, US West, Europe West and Southeast Asia.
Use Ona when
your engineers want a governed cloud IDE shared with a Codex agent, inside your own AWS or GCP account or with a GPU, and you are ready to sign an Enterprise contract.
- Runs in your own cloud. Useful if environments must stay inside your own AWS or GCP account: Ona's Enterprise runners provision them there.
- No 12-hour stop, and warm pools. Useful for long work: an Ona environment has no hard session cap, and Enterprise warm pools hand out a ready environment in about 10 seconds.
- GPUs and a managed agent. Useful if agents need a GPU or a managed Codex Agent: Ona runners can use A10G VMs and start Codex from Linear or Slack.
Where boat fits
Codespaces and Ona are both cloud IDEs for engineers who open a repo and code. If your own code starts and watches the agents, boat gives each one a full VM with an API on every plan, self-serve from $20 a month. It has no session cap once auto-stop is off on a paid plan (default 1 hour). boat is not the pick for GPUs or for runs outside the EU.
Machines that keep running and keep their work
A codespace stops at 12 hours even while in use. An Ona environment stops after 30 idle minutes unless auto-stop is set to Never. boat runs until you stop it once auto-stop is off, and saves the disk every minute. A stopped boat sandbox has no compute charge, and a resume is like a reboot.
Fork a warm machine instead of rebuilding
Neither Codespaces nor Ona copies a running environment. Codespaces starts each attempt from a config or a prebuild, and Ona from a prebuild or an Enterprise warm pool. boat forks a running sandbox into copies from its last 1-minute disk snapshot.
A full VM with /dev/kvm, a desktop and open ports
Neither documents /dev/kvm. Codespaces needs a desktop add-on you configure, and Ona has a browser its AI drives but no full desktop. Every boat sandbox has /dev/kvm, a 60 fps desktop and up to 50 HTTPS URLs.
Use boat when your code starts and drives the agents: full VMs with /dev/kvm, a desktop and HTTPS URLs, an API on every plan, and machines that keep their disk and fork while running. Turn auto-stop off on a paid plan for long work (default 1 hour). Compare it one to one: boat vs GitHub Codespaces and boat vs Ona.
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 GitHub Codespaces cheaper than Ona?
In the scenarios we priced, yes. One coding agent on workdays is $51 a month on Codespaces against $5,030 on Ona's Enterprise listing, and 50 agents in parallel are $3,019 against $6,521. Ona's real Enterprise price is a sales quote, so yours may differ. boat comes to $20 and $317 for those two.
Which is faster, Codespaces or Ona?
Neither is in the public benchmarks we use, so we cannot say. In StarSling's run of 3 October 2026, boat did 28.06 V8 Web Tooling runs/s at 4 vCPU / 8 GB on a Ryzen 9 9950X host. boat does not promise a CPU model.
Can I run an agent 24/7 on Codespaces or Ona?
Not on Codespaces without restarts: a codespace has a maximum lifetime of 12 hours, even while in use. On Ona you can set auto-stop to Never, because there is no hard session cap. boat has no session cap once auto-stop is off on a paid plan (default 1 hour).
Can Codespaces and Ona run Docker?
Yes, both run Docker inside the dev container, with sudo or root. Neither documents /dev/kvm, so Android emulators and microVMs are not a supported setup. Every boat sandbox has Docker, systemd and /dev/kvm.
Is Ona the same as Gitpod?
Yes. Gitpod renamed itself Ona in 2025, and Ona is now part of OpenAI. Ona Cloud and Core shut down on October 31, 2026, so new customers buy Enterprise through sales.
Can I run Claude Code on Codespaces or Ona?
Yes. In a codespace you install it yourself, with your API key as an environment variable. Ona's CLI lets external agents such as Claude Code create environments and run commands, and its managed agent is Codex. boat installs Claude Code, Codex, OpenCode and others. With boat's paid credentials proxy on, the real keys of supported providers stay outside the sandbox.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs GitHub Codespaces
- boat vs Ona
- E2B vs GitHub Codespaces
- Daytona vs GitHub Codespaces
- Modal vs GitHub Codespaces
- Vercel Sandbox vs GitHub Codespaces
- Cloudflare Sandbox vs GitHub Codespaces
- Blaxel vs GitHub Codespaces
- Runloop vs GitHub Codespaces
- Tensorlake vs GitHub Codespaces
- Morph Cloud vs GitHub Codespaces
- CodeSandbox SDK vs GitHub Codespaces