Railway vs Ona
Railway is an app platform that added self-serve sandbox VMs. Railway destroys a sandbox after its idle timeout, and files survive in checkpoints you take. Ona, formerly Gitpod and now part of OpenAI, runs cloud dev environments for engineers and its Codex agent. Since Ona Cloud shut down on October 31, 2026, Ona sells only Enterprise, through sales, on runners in your own AWS or GCP account.
The companies and products
Railway
Railway is a cloud platform for deploying web apps, servers and databases. It also sells Sandboxes and Cloud Agents.
Railway's main product is app hosting: you deploy services and databases as containers on its own hardware. In 2026 it added Sandboxes: isolated Linux VMs that you create from the CLI or a TypeScript SDK, run commands in and destroy. It also added Cloud Agents: a personal VM for a coding agent that keeps its disk and sleeps or wakes. Cloud Agents are in Priority Boarding, and breaking changes may occur. Railway suits teams that already host on Railway and want sandboxes next to their apps.
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. “28th cheapest of 365” means 27 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 | Railway: 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 Railway sandboxes are destroyed at the idle timeout, so you keep work in checkpoints, or use a Cloud Agent (Priority Boarding). Ona keeps each VM's disk, and its SDK starts environments from code on Enterprise, its only plan. boat saves the disk every minute with no code and documents /dev/kvm on every VM. | 28th cheapest of 365 $1,481 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 Railway fits if you set the idle timeout to 0, and memory then bills the whole time. Ona needs auto-stop set to Never, because background work does not count as activity. On boat you turn auto-stop off on a paid plan (default 1 hour). | 21st cheapest of 361 $3,977 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 Railway fits short code runs well: a sandbox bills for CPU used, is gone when the job ends, and Railway publishes no starts-per-minute limit. boat's $20 plan includes 12 starts per minute and 200 per day. | 42nd cheapest of 336 $413 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 Railway caps sandboxes per environment (100 on Pro). Ona is built for your own engineers, and its per-user policy defaults to 10 running environments. boat allows 100 to 2,000 sandboxes at once by plan, with start limits per plan. | 46th of 349, with limits $290 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 | 84th of 349, with limits $4,450 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 Railway can fork a running sandbox and boot many from one checkpoint. Ona cannot copy an environment, but warm pools start one in about 10 seconds. boat forks a running sandbox from its last 1-minute snapshot. | 113th of 359, with limits $364 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 Ona has no fork, so each CI run starts from a prebuild or an Enterprise warm pool. Railway can fork a running sandbox but does not document Docker. boat documents Docker on every sandbox, and each CI job counts as a start. | 116th cheapest of 374 $1,210 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 Ona is a full cloud IDE with Dev Containers and prebuilds, sold as Enterprise through sales. Railway's Cloud Agents keep their disk but are in Priority Boarding. boat is a full VM you reach over SSH, HTTPS or a desktop. | 69th cheapest of 371 $89 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 Railway includes no desktop; you can add Xvfb and noVNC with the template builder. Ona's AI can drive a built-in web browser, but there is no full desktop for other apps. boat streams a 60 fps desktop with Chrome and computer-use tools. | 47th cheapest of 367 $407 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 | 53rd of 356, with limits $93 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 | 65th cheapest of 343 $570 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 | 111th of 327, with limits $2,988 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 | 71st of 351, with limits $574 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 | Railway | Ona | boat |
|---|---|---|---|
| Kind of product | App platform for services and databases, with sandbox VMs and Cloud Agents added in 2026 | Cloud dev environments for engineers and the Codex Agent; each task gets an isolated VM | Sandbox API for agents; every sandbox is a full VM with its own kernel |
| Buying it | Self-serve: Free, Hobby ($5) and Pro ($20 per workspace), usage billed per second | Enterprise only, through sales; Ona Cloud and Core shut down on October 31, 2026 | Self-serve plans from $20 a month; the 7-day trial needs a card |
| When the sandbox goes idle | Destroyed after the idle timeout (30 minutes by default, or 0 for never); files survive in checkpoints you take | Stops after 30 idle minutes by default and keeps its disk; storage stays on your cloud bill, and Enterprise archives it after 3 days by default (1 to 30 days) | Auto-stop after 1 hour by default (a timer, not an idle check); disk saved every minute and at stop, kept at least 14 days; no compute charge while stopped |
| Docker and nested virtualization | Root shell on an Ubuntu VM; Docker and /dev/kvm are not documented, so you install and verify them yourself | Docker and root inside the Dev Container; nested virtualization is not documented | Docker, root, systemd and /dev/kvm documented on every sandbox |
| Fork and checkpoints | Fork a running sandbox's filesystem; named disk checkpoints boot new ones | No environment copy; you can create a project from an environment's config, and warm pools start one in about 10 seconds | Fork a running sandbox from its last 1-minute snapshot; saved snapshots start new ones |
| Starting point | Templates built from ordered steps (apt packages, env, commands) and cached | Dev Container config per repo, with prebuilds that snapshot the filesystem, and Enterprise warm pools | boat's image or a saved snapshot, shareable by code; you cannot boot your own Docker image |
| Driving it from code | CLI and TypeScript SDK to create sandboxes and run commands | Python, TypeScript and Go SDK and a CLI, on Enterprise, Ona's only plan | API, SDK and CLI on every plan, including the trial |
| Coding agents | Claude Code, Codex, OpenCode and Pi in the image, run through exec | Managed Codex Agent, started from chat, Slack, a pull request, a Linear issue or an automation; you install Claude Code yourself | Seven harnesses installed, with a prompt, steer and events API |
| Keeping keys out of the sandbox | Secrets are environment variables, or signed in and saved in a checkpoint | Secrets are injected as environment variables or files; OIDC can swap them for short-lived cloud credentials | Optional paid proxy ($1 a day when on, plus $1 per 1,000 requests) keeps real keys of supported model providers out; other secrets still enter |
| Desktop and computer use | No desktop included; you can add Xvfb and noVNC with the template builder and publish the port on a sandbox domain | Browser IDE plus VS Code and JetBrains; a built-in web browser Ona's AI can drive; no full graphical desktop for other apps | Built-in desktop and Chrome at 1920x1080, 60 fps, with computer-use tools and an embeddable stream |
| Reaching the sandbox | Up to 10 public HTTPS domains, set only at creation, with no built-in auth; SSH and port forwarding | HTTPS URL per port for you, your organization or everyone; SSH; no raw TCP documented | Up to 50 HTTPS URLs, token-gated by default; SSH; public IPv6 for raw ports; no dedicated IPv4 |
| Apps and databases next to it | Deploy Postgres, Redis and services in the same project; a sandbox can join their private network | No hosted databases; environments are for development work | No hosted databases or app services; host your own inside a sandbox |
| GPUs | No GPU for sandboxes | GPU instance types on Enterprise runners in your own cloud, such as one NVIDIA A10G with 16 vCPU and 64 GB | No GPU on any size |
| Regions | US West, US East, Amsterdam and Singapore; new sandboxes start in US West unless you pick one | Enterprise runners in your own AWS or GCP account, in a region you choose | Germany, Finland and France; you cannot pick a region; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Railway | Ona | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Not published | 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 | Yes | 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 | Yes | No documented way | Yes |
| Live fork (no pause) | Yes | 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 | Yes | 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 | Yes | Yes | Yes |
| Agent harness API | Yes | Yes | Yes |
| MCP server | Yes | 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 | Yes | 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 | Yes | No documented way | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Railway and Ona 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 sandboxes on other hosts and does not promise a CPU model.
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. Railway 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 | Railway, 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 | $16 · Hobby · with limits | $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 | $70 · Hobby · 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 | $739 · Hobby · with limits | $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 | $223 · Pro · 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 | $781 · Pro · with limits | $5,955 · Enterprise (AWS Marketplace 12-month contract) · with limits | $8,800 · $2000/mo · with limits |
Railway: Railway bills sandboxes per second at about $50 per vCPU-month on CPU actually used and $50 per GB-month on memory in use, plus $0.05 per GB out, and memory keeps billing while a sandbox waits. Plans: Free ($0 with $1 of usage a month), Hobby ($5) and Pro ($20 per workspace); the Hobby and Pro fees count toward usage. Sandbox disk has no published price, so our bills leave it out.
Ona: Ona Cloud and Core shut down on October 31, 2026, so the Ona prices here use its Enterprise listing on AWS Marketplace: a 12-month, $60,000 contract (about $5,000 a month), 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, billed per second while a sandbox runs. A stopped sandbox has no compute charge, but saved snapshots above the included count and the AI credentials proxy still charge. The $20 plan allows 100 sandboxes at once and 12 starts per minute, 60 per hour, 200 per day. Extra starts cost $0.03 to $0.07 each.
Limits in those scenarios
We mark every Railway scenario as not a clean fit because Railway publishes no sandbox disk price, so its bills count CPU and memory only. It caps sandboxes per environment at 50 on Hobby and 100 on Pro, so 300 user sandboxes or 1,000 jobs at once need several environments or an Enterprise limit. No Ona scenario fits as published, because Ona sells only Enterprise through sales and publishes no concurrency limit, so the table assumes 3 environments at once. On boat, the 1,000-job burst needs about 6,667 starts a day, above the 2,400 the $2,000 plan includes, so the extra starts are paid, and starts above 270 a minute fail with 429.
| Scenario | Railway | Ona | boat |
|---|---|---|---|
| One coding agent, workdays |
|
| 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 Railway when
your app and databases already live on Railway and you want self-serve sandboxes on the same private network, or regions in the US and Asia.
- Your apps and databases in one place. Useful if your app already runs on Railway: sandboxes can join the same private network as your Postgres and services.
- Sign up and start today. Useful if you want to try it now: Railway has self-serve plans, while Ona sells only Enterprise through sales.
- Short jobs that bill for CPU used. Useful for many quick code runs: a Railway sandbox bills for CPU used and is gone when the job ends.
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 buy through sales.
- A full cloud IDE for your team. Useful if your engineers work beside their agents: Ona has browser, VS Code and JetBrains IDEs with Dev Containers, prebuilds and warm pools.
- Runs in your own cloud. Useful if environments must run inside your own AWS or GCP account: Ona's Enterprise runners do that.
- GPU environments. Useful if your agents need a GPU: Ona's Enterprise runners can use GPU instance types, such as an A10G VM.
Where boat fits
If your own code starts the agents, both picks have a catch: Railway destroys idle sandboxes unless you checkpoint them, and Ona's SDK comes with an Enterprise contract. boat gives each agent a full VM with Docker, /dev/kvm and a desktop, saves its disk with no code, and lets you drive the agents inside by API on every plan. boat runs only in the EU, has no GPU and limits starts by plan.
Machines that keep their work
A Railway sandbox is destroyed after 30 idle minutes by default; with the timeout at 0, memory bills until you destroy it. Ona keeps the disk, but on your cloud bill, and archives a stopped environment after 3 days by default. A boat sandbox has no compute charge while stopped and keeps its disk for at least 14 days. A boat resume is like a reboot.
Docker, KVM and a desktop, documented
Neither Railway nor Ona documents /dev/kvm, and Railway's sandbox docs do not mention Docker. Railway includes no desktop, though you can install one, and Ona's AI drives a built-in web browser but not a full desktop. Every boat sandbox has Docker, /dev/kvm and a 60 fps desktop with Chrome.
Agents you drive from outside
On Railway you run each agent through exec and parse its output, with its API key in the VM. Ona's SDK is on Enterprise and its managed agent is Codex. boat has a prompt, steer and events API on every plan, and its optional paid proxy keeps real keys of supported providers outside.
Use boat when your code starts and drives the agents: full VMs with Docker, /dev/kvm, a desktop and public ports, an API on every plan from $20 a month, and a disk saved with no code. boat runs only in the EU and limits starts by plan. Compare it one to one: boat vs Railway 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 Railway cheaper than Ona?
In every scenario we priced, yes: one agent running all month is $70 on Railway against $5,140 on Ona, and 50 agents in parallel are $739 against $6,521. Ona's numbers use its Enterprise listing on AWS Marketplace and Railway's leave out disk, so neither is exact. On boat the same jobs come to $26 and $317 a month.
Which is faster, Railway or Ona?
We cannot say. Neither is in the public benchmarks we use. boat did 28.06 V8 Web Tooling runs/s at 4 vCPU / 8 GB in StarSling's run of 3 October 2026, on an AMD Ryzen 9 9950X host.
Can Railway or Ona run Docker?
Ona gives you Docker and root inside the Dev Container. Railway's sandbox docs give you a root shell on an Ubuntu VM but do not mention Docker or /dev/kvm, so you install and verify them yourself. boat documents Docker, systemd and /dev/kvm on every sandbox.
What happens when a sandbox goes idle?
Railway destroys it after the idle timeout, 30 minutes by default, and the checkpoints you took survive. Ona stops it after 30 idle minutes and keeps the disk, though background processes do not count as activity. A boat sandbox auto-stops after 1 hour by default, keeps its disk for at least 14 days, and has no compute charge while stopped.
Is Ona the same as Gitpod, and can I still sign up?
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. Railway and boat both have self-serve plans.
Do Railway and Ona come with coding agents?
Railway's default sandbox image includes Claude Code, Codex, OpenCode and Pi, which you run through exec. Ona's managed agent is Codex, and you install Claude Code yourself. boat installs seven coding agents and lets you prompt, steer and watch them through an API.
Try boat
Install the CLI, then run boat new.
7-day free trial