Northflank vs Railway
Both are app platforms that now run agent sandboxes as VMs with their own kernel. A Northflank sandbox runs until you pause it and keeps files through volumes or filesystem snapshots, with GPUs and 17 regions. A Railway sandbox bills for the CPU it uses and is destroyed after an idle timeout, unless you save a checkpoint first.
The companies and products
Northflank
Northflank is a London developer platform for running services, jobs and databases on Kubernetes, and Sandboxes is its product for running untrusted code.
A Northflank sandbox is a container image deployed as a service. CPU sandboxes run in Kata microVMs with their own kernel, and GPU sandboxes run under gVisor. You create and drive them from the JavaScript or Python SDK, the CLI or the dashboard, on Northflank's cloud or inside your own. It suits teams that want one platform for apps, databases, GPUs and sandboxes.
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.
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. “44th cheapest of 361” means 43 of the other 360 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 | Northflank: price rank | Railway: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Railway ranks 13th here with your own setup (checkpoints or Cloud Agents, Docker installed by you), and boat ranks 8th. On Northflank you snapshot the filesystem before a pause or use volumes. boat saves the disk at each stop with no code. | 186th of 365, with limits $1,413 a month | 28th cheapest of 365 $1,481 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB All three fit: boat ranks 6th, Northflank 20th and Railway 30th. Railway needs the idle timeout set to 0, and memory bills the whole time. On Northflank you snapshot or use volumes to keep files across a pause. | 44th cheapest of 361 $2,551 a month | 21st cheapest of 361 $3,977 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 Short code runs suit both: Northflank has per-second plans from 0.1 vCPU, and Railway (43rd here) bills for CPU used and ends the sandbox when the job ends. boat ranks 189th, because it caps starts per plan. | 91st of 336, with limits $114 a month | 42nd cheapest of 336 $413 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 allows 100 sandboxes per environment on Pro and Northflank does not publish a limit, so 300 at once is not confirmed on either. boat ranks 3rd here. | 94th of 349, with limits $810 a month | 46th of 349, with limits $290 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 | 333rd of 349, with limits $1,742 a month | 84th of 349, with limits $4,450 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 | 139th of 359, with limits $685 a month | 113th of 359, with limits $364 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 boat ranks 2nd, Northflank 35th and Railway 115th. Railway's sandbox docs do not mention Docker; you install and verify it yourself. boat adds /dev/kvm for emulators, and each boat CI job counts as a start. | 36th cheapest of 374 $347 a month | 116th cheapest of 374 $1,210 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Railway's Cloud Agents keep a disk and sleep or wake, but they are in Priority Boarding. A Northflank sandbox bills its full plan until you pause it. boat ranks 19th here. | 124th cheapest of 371 $106 a month | 69th cheapest of 371 $89 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 ranks 15th here with your own setup: add Xvfb and noVNC with its template builder. On Northflank you install a desktop and a stream in your own image. boat ranks 10th and ships a 60 fps desktop with Chrome. | 189th of 367, with limits $367 a month | 47th cheapest of 367 $407 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 | 83rd of 356, with limits $359 a month | 53rd of 356, with limits $93 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 | 94th cheapest of 343 $200 a month | 65th cheapest of 343 $570 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 | 83rd of 327, with limits $2,031 a month | 111th of 327, with limits $2,988 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 | 43rd of 351, with limits $180 a month | 71st of 351, with limits $574 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 Northflank ranks 5th here, with GPU sandboxes from L4 to H100, H200 and B200. Railway and boat have no GPUs. | 5th cheapest of 102 $692 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 | Northflank | Railway | boat |
|---|---|---|---|
| Isolation | Kata microVM with its own kernel for CPU; gVisor for GPU | Sandboxes are isolated Linux VMs; app services are containers | Full VM with its own kernel, on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat; vCPUs are shared |
| When the sandbox sits idle | Keeps running and billing its full plan until you pause it; no idle auto-pause | Destroyed after the idle timeout, 30 minutes by default, or never if set to 0; Cloud Agents sleep and keep their disk | Auto-stop is a timer (default 1 hour), not an idle check; a stopped sandbox has no compute charge and keeps its disk at least 14 days |
| What survives a stop | Attached volumes survive (billed while paused); the rest of the disk resets unless you snapshot the filesystem before the pause and restore it (microVM only) | The checkpoints you take, which boot new sandboxes; the sandbox itself is destroyed | The disk, saved every minute and at each stop with no code; memory and processes are not saved |
| Snapshots and fork | Filesystem snapshots of a running or terminating sandbox, opt-in; restore into a new one | Fork a running sandbox's filesystem; named disk checkpoints boot new ones | Automatic disk snapshots; fork a running sandbox from its last 1-minute snapshot |
| Docker and nested virtualization | Own kernel, so Docker can run; /dev/kvm not documented inside a sandbox | Root shell on Ubuntu; Docker and /dev/kvm are not documented, you install and verify them yourself | Docker, root, systemd and /dev/kvm on every sandbox |
| Desktop and computer use | No built-in desktop; you install one in your own image; a Playwright guide covers browser agents | No desktop included; you add Xvfb and noVNC with the template builder and publish the port | 1920x1080, 60 fps Linux desktop, Chrome and computer tools for agents, embeddable stream |
| Coding agents | Harnesses with Claude Code, Codex, Cursor, OpenCode, Pi, OMP or Devin CLI; you reach the agent through a terminal or SSH | Claude Code, Codex, OpenCode and Pi in the sandbox image, run through exec; Cloud Agents keep terminal sessions you reattach to | Seven agents installed, with a prompt, steer and events API |
| Keeping API keys out of the sandbox | Header injection for listed hosts in the network policy API (documented for your own cluster); otherwise env vars or files | Environment variables in the sandbox, or signed in and saved in a checkpoint | Optional paid proxy ($1 a day plus $1 per 1,000 requests) for supported model providers and HTTPS APIs you register; other secrets still enter the sandbox |
| Inbound access | HTTP ports on a code.run domain or your own domain, private by default; SSH; public TCP and UDP through a separate load balancer | Up to 10 public HTTPS domains, set only at creation; SSH and port forwarding | Up to 50 HTTPS URLs, token-gated by default; SSH; raw ports over IPv6 on sandboxes with no IPv4 of their own |
| Outbound rules | Network policies with allow lists by IP, CIDR or domain, documented for your own cluster | No sandbox egress allowlist documented | Open internet, no provider-side allowlist; you can add firewall rules inside the VM |
| Biggest sandbox | Up to 20 vCPU / 40 GB, custom sizes on request; a resize restarts the sandbox | 8 vCPU / 8 GB on Hobby; up to 32 vCPU / 32 GB on Pro per the docs | 8 vCPU / 16 GB on the $20 plan, 16 vCPU / 32 GB from $100 |
| Sandboxes at once | Limit not published | 50 per environment on Hobby, 100 on Pro; Enterprise can ask for more; no published start limit | 100 to 2,000 by plan, with included starts per minute, hour and day (12 / 60 / 200 on $20) |
| GPUs | L4, A100, H100, H200, B200, RTX PRO 6000 and more, billed per hour | No | No GPU on any size |
| Regions | 17 regions in North America, South America, Europe, Asia, Australia and Africa | US West, US East, Amsterdam and Singapore | Germany, Finland and France; you cannot pick a region; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Northflank | Railway | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Not published | Yes |
| Nested virtualization | No documented way | Not published | Yes |
| Root | Not published | Yes | Yes |
| Systemd | Not published | Not published | Yes |
| Desktop GUI | No documented way | With your own setup | Yes |
| Browser | With your own setup | Yes | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | With your own setup | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Yes | 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 | No documented way | 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 | Yes | No documented way | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | No documented way | No documented way |
| Secret proxy | Yes | No documented way | Yes |
| Secret proxy for any API | Yes | No documented way | Yes |
| Preinstalled agents | Yes | Yes | Yes |
| Agent harness API | No documented way | Yes | Yes |
| MCP server | No documented way | Yes | No documented way |
| GPU | Yes | No documented way | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | Yes | No documented way | No documented way |
| Self-hosting | Yes | 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 | Not published | Yes | Yes |
| Usage per sandbox (API) | Yes | No documented way | Yes |
| Audit logs | Yes | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | Yes | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Northflank and Railway 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 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. Northflank and Railway 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 | Northflank, a month | Railway, 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 | $30 · Developer Sandbox (free tier) | $16 · Hobby · with limits | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $106 · Developer Sandbox (free tier) | $70 · Hobby · 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 | $1,290 · Developer Sandbox (free tier) | $739 · Hobby · 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 | $359 · Developer Sandbox (free tier) · with limits | $223 · Pro · 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 | $684 · Developer Sandbox (free tier) · with limits | $781 · Pro · with limits | $8,800 · $2000/mo · with limits |
Northflank: Northflank bills per second for the plan size you pick, with no monthly fee and no start fee; 4 vCPU / 8 GB is $0.1333 an hour. There is no idle auto-pause, so a sandbox bills until you pause it. Volumes cost $0.11657 per GiB a month, also while paused, and outbound traffic costs $0.06 per GB.
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, which keeps billing while a sandbox waits. Plans: Free ($0 with $1 of usage a month), Hobby ($5) and Pro ($20); the Hobby and Pro fees count toward usage. Railway publishes no sandbox disk price, so our bills leave disk out.
Railway: 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. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots above the included count and the optional AI credentials proxy still charge while sandboxes are stopped. The $20 plan includes 12 starts a minute and 200 a day; each extra start costs $0.03 to $0.07. A card is required, also for the 7-day trial.
Limits in those scenarios
On Northflank, files outside attached volumes survive a pause only if you snapshot the filesystem first, and it does not publish how many sandboxes can run at once. Railway is marked as a different kind of product with no published disk price. It caps sandboxes per environment, 100 on Pro, so 300 user sandboxes or 1,000 jobs at once need several environments or an Enterprise limit. boat's limits: a stopped disk is kept at least 14 days, and a machine failure loses writes after the last good snapshot. The 1,000-job burst needs more starts than the $2,000 plan includes, and starts above 270 a minute fail with 429.
| Scenario | Northflank | Railway | boat |
|---|---|---|---|
| One coding agent, workdays | None for this scenario |
| None for this scenario |
| One agent that never stops | None for this scenario |
| 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 Northflank when
you need GPUs next to the agent, regions outside the US and Europe, outbound allow lists, or sandboxes inside your own cloud account.
- GPU sandboxes. For agents that train, fine-tune or run models: Northflank has GPU sandboxes from L4 to H100, H200 and B200, and Railway has none.
- Regions around the world. For users far from the US and Europe: Northflank also runs in Canada, Brazil, India, East Asia, Australia and South Africa.
- Your own cloud and outbound rules. For teams that must run in their own AWS, GCP or Azure account, or limit where sandboxes may connect.
Use Railway when
your app and databases already live on Railway and you want short-lived sandboxes on the same private network that bill for the CPU they use.
- Short jobs that bill for CPU used. For many quick code runs: a Railway sandbox bills for the CPU it uses and is gone when the job ends.
- Lower bills for most of these jobs. Railway's bills are lower than Northflank's in four of the five scenarios here, though they leave out disk, which Railway does not price.
- Sandboxes next to your Railway apps. For apps already on Railway: a sandbox can join the same private network as your Postgres and services.
Where boat fits
If your agents work on one machine for hours or days, look at boat. Northflank and Railway are app platforms that added sandboxes, and on both you set up snapshots, volumes or checkpoints to keep what the agent built. boat gives each agent a full VM that saves its disk with no code, with Docker, /dev/kvm, a desktop and coding agents you drive from your code. boat has no GPU, no US or Asia region, and caps starts per plan.
The disk is saved with no code
On Northflank, files outside volumes survive a pause only through a filesystem snapshot. Railway destroys a sandbox after 30 idle minutes unless you take checkpoints or set the timeout to 0, which keeps memory billing. boat saves the disk every minute and at each stop, and keeps it at least 14 days. A boat resume is like a reboot.
Agents you drive from outside
Northflank Harnesses hand you a terminal or SSH, and Railway runs agents through exec with the API key inside the VM. boat adds a prompt, steer and events API. With the optional paid proxy on, real model keys stay outside the sandbox.
A desktop, Docker and KVM, documented
On Northflank and Railway you build a desktop yourself. Neither documents /dev/kvm, and Railway's sandbox docs do not mention Docker. boat documents a 60 fps desktop, Chrome, Docker and /dev/kvm on every sandbox.
Use boat when your agents work for hours or days and should find their files as they left them: a full VM with Docker, /dev/kvm, a desktop and coding agents you drive by API. boat runs only in Germany, Finland and France. Compare it one to one: boat vs Northflank and boat vs Railway.
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 Northflank cheaper than Railway?
Mostly no. Railway is lower in four of the five scenarios: one agent that never stops is $70 on Railway against $106 on Northflank, and 50 agents in parallel are $739 against $1,290. Northflank is lower for 1,000 short jobs at once ($684 against $781). Railway's numbers leave out disk, which it does not price. boat costs $26 and $317 for the first two, and $8,800 for the burst, because it charges for extra starts.
Which is faster, Northflank or Railway?
Neither is in the public benchmarks we use, so we cannot say. boat did 28.06 V8 Web Tooling runs/s at 4 vCPU / 8 GB, second of 15 in StarSling's run of 3 October 2026, on a Ryzen 9 9950X host. boat does not promise a CPU model.
Can Northflank or Railway run Docker?
A Northflank CPU sandbox is a Kata microVM with its own kernel, so Docker can run inside. Railway's sandbox docs give you a root shell on Ubuntu but do not mention Docker; you install and verify it yourself. boat has Docker, systemd and /dev/kvm on every sandbox.
What happens to a sandbox when it goes idle?
A Northflank sandbox keeps running and billing until you pause it; volumes and filesystem snapshots keep its files. Railway destroys an idle sandbox after its timeout, 30 minutes by default, unless you set it to 0; checkpoints keep its files. A boat sandbox auto-stops after 1 hour by default, has no compute charge while stopped, and keeps its disk at least 14 days.
Do Northflank or Railway have GPUs?
Northflank has GPU sandboxes under gVisor with cards from L4 to H100, H200 and B200, billed per hour. Railway has no GPUs, and boat has no GPU on any size.
Where do they run?
Northflank runs in 17 regions, fixed per project. Railway has California, Virginia, Amsterdam and Singapore. boat runs on machines in Germany, Finland and France, you cannot pick a region, and snapshot copies can be stored outside the EU.
Try boat
Install the CLI, then run boat new.
7-day free trial