Fly.io Machines vs Railway

Fly.io Machines are fast microVMs that boot your own image in 17 regions, and you build the sandbox around them yourself. Railway is an app platform that sells sandbox VMs with an SDK, forks, checkpoints and coding agents. Railway destroys an idle sandbox after its idle timeout unless you save a checkpoint first, and its Cloud Agents keep their disk.

The companies and products

Fly.io Machines

Fly.io is an app hosting platform, and Machines are the microVMs underneath it that you can also start and stop through a REST API.

A Fly Machine boots your Docker image as a Firecracker microVM on Fly's own servers, in one of 17 regions. You pick a shared or performance CPU preset and mount one Volume at a time for data that must last. Fly Proxy can stop, suspend and wake Machines as traffic comes and goes. Machines themselves are an app-hosting building block; for agent sandboxes Fly also sells Sprites (see boat vs Sprites), so this page compares only the Machines product.

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. “123rd cheapest of 365” means 122 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 workloadFly.io Machines: price rankRailway: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Railway is a full match here with your own setup: you keep work with checkpoints or a Cloud Agent, and install Docker yourself. Fly is a compromise: you build the image and keep files on a Volume or with opt-in persist_rootfs. boat saves the disk at each stop and has Docker and /dev/kvm on every sandbox.
123rd of 365, with limits
$836 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
Railway fits an always-on assistant once its idle timeout is set to 0, or with a Cloud Agent; memory bills the whole time. A Fly Machine has no time cap, and files last on its Volume or with persist_rootfs. boat runs with no session cap once auto-stop is off (default 1 hour) on a paid plan.
186th of 361, with limits
$816 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
Both suit short code bursts better than boat: Fly bills per second with no plan fee, and Railway bills for CPU used and ends the sandbox when the job ends. boat's start caps push it to its $2,000 plan here.
83rd of 336, with limits
$94 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 Fly's API takes about one create request per second per app, so 300 users at once need extra setup on both. boat allows 300 at once from the $100 plan, with start limits per plan.
75th of 349, with limits
$600 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
52nd of 349, with limits
$2,838 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
124th of 359, with limits
$457 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
CI keeps the CPU busy, which drains a shared Fly vCPU's burst balance. Railway's sandbox docs do not mention Docker, so you install and check it yourself. boat has Docker on every sandbox, and each CI job counts as a start.
154th of 374, with limits
$288 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 are in Priority Boarding and fixed at 4 vCPU / 4 GB on Pro. A Fly Machine keeps its Volume, and its root file system with persist_rootfs.
160th of 371, with limits
$35 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 includes no desktop; you add Xvfb and noVNC with its template builder. On Fly you add a desktop to your own image. boat ships a 60fps desktop with Chromium and computer tools.
140th of 367, with limits
$173 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
229th of 356, with limits
$90 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
233rd of 343, with limits
$67 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
Fly ranks highest of the three here: its bill is $1,232 a month against $1,800 on boat and $2,988 on Railway, and it can spread scrapers across 17 regions.
47th of 327, with limits
$1,232 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
168th of 351, with limits
$63 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
Not ranked: misses a requirementNot ranked: misses a requirementNot 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 requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureFly.io MachinesRailwayboat
Kind of productApp hosting platform; Machines are microVMs you boot from your own image through a REST API. Fly sells Sprites separately for agent sandboxesApp platform that added Sandboxes and Cloud Agents in 2026, driven from a CLI or TypeScript SDKAgent sandbox: a full VM per agent, ready to use
IsolationFirecracker microVM with its own kernelSandboxes and Cloud Agents are isolated Linux VMs; app services are containersFull VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Docker, systemd and nested virtualizationRoot and Docker you install yourself; Fly's own init by default (systemd as PID 1 is not a documented setup); /dev/kvm not documentedRoot shell on Ubuntu; Docker and /dev/kvm not documented, so you install and check them yourselfDocker, root, real systemd and /dev/kvm on every sandbox
Files after a stopRoot file system resets by default; opt-in persist_rootfs keeps it, but Fly staff say not to trust it with critical data. Lasting data goes on one Volume, billed for its full size around the clockSandboxes are destroyed after the idle timeout (30 minutes by default, or 0 for never); files survive in checkpoints you take. Cloud Agents sleep and keep their diskDisk saved every minute and at each stop; no compute charge while stopped; kept at least 14 days, longer with a saved snapshot
Pause and memorySuspend keeps memory for Machines up to 2GB; the snapshot is dropped on deploy or host moveCheckpoints save the disk only, no memoryResume reboots from disk; memory is not saved
ForkClone copies a Machine's config; its Volume starts empty unless you restore a volume snapshot or fork the VolumeFork a running sandbox's filesystem; boot many from one named checkpointFork a running sandbox from its last 1-minute snapshot; saved snapshots start new ones
Wake on requestFly Proxy stops or suspends idle Machines and wakes them when a request arrivesSandboxes are not woken by traffic; Cloud Agents sleep and wakeYou start and stop sandboxes through the API; auto-stop is a timer, not an idle check
Coding agentsNot built in on Machines; you install agents in your image. Fly's separate Sprites product ships coding agentsClaude Code, Codex, OpenCode and Pi preinstalled; you run them through exec. Cloud Agents keep terminal sessions you reattach toSeven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API
Keeping keys out of the sandboxSecrets arrive as environment variables; you deploy Fly's open-source tokenizer proxy yourselfSecrets enter as environment variables, or you sign in and save it in a checkpointOptional AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests); other secrets still enter the sandbox
Desktop and computer useNot built in; you add a desktop and browser to your own imageNot included. You set it up: add Xvfb and noVNC with the template builder and publish the port on a sandbox domain60fps desktop and Chromium, computer tools and browser control, embeddable stream
Reaching the sandboxPublic HTTPS and TCP through Fly Proxy, Anycast IPs, custom domains, private network between MachinesUp to 10 public HTTPS domains, set only at creation; SSH and port forwardingUp to 50 HTTPS URLs, token-gated by default; SSH; public IPv6 for raw ports; no dedicated IPv4
Apps and databases next to the sandboxHost your own apps on Machines with a private network, Anycast IPs and custom domainsDeploy Postgres, Redis and services in the same project; a sandbox can join their private networkNo hosted databases or app services; host your own inside a sandbox
CPUShared vCPUs guarantee 6.25% of a core plus bursts; performance vCPUs get the full core at a higher rateBilled on CPU actually used; sandboxes up to 8 vCPU on Hobby and 32 vCPU on ProShared vCPUs with no baseline quota or burst balance; billed at full rate while running, busy or idle
Regions17 regions on six continentsUS West, US East, Amsterdam and SingaporeGermany, Finland and France; you cannot pick one; no US or Asia region
Every feature Battleships tracks (43)
FeatureFly.io MachinesRailwayboat
Full VM (own kernel)YesYesYes
Docker insideYesNot publishedYes
Nested virtualizationNot publishedNot publishedYes
RootYesYesYes
SystemdNot publishedNot publishedYes
Desktop GUINo documented wayWith your own setupYes
BrowserNo documented wayYesYes
Computer-use APINo documented wayNo documented wayYes
SSHYesYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesNo documented wayYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkNo documented wayNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo documented way
Wake on requestYesNo documented wayNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundYesNo documented wayYes
Public IPv4YesNo documented wayNo documented way
Egress allowlistYesNo documented wayNo documented way
Secret proxyNo documented wayNo documented wayYes
Secret proxy for any APINo documented wayNo documented wayYes
Preinstalled agentsNo documented wayYesYes
Agent harness APINo documented wayYesYes
MCP serverYesYesNo documented way
GPUNo documented wayNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayNo documented wayNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayYesNo documented way
Open sourceYesNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNo documented wayYesYes
Usage per sandbox (API)No documented wayNo documented wayYes
Audit logsNot publishedYesNo documented way
SSONo documented wayYesNo documented way
SOC 2YesYesNo documented way
HIPAAYesYesNo documented way
EU data residencyYesYesNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

Fly.io MachinesNot measured
RailwayNot measured
boat28.06 runs/s

Fly.io Machines 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 V8 Web Tooling Benchmark runs per second 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. On Fly, speed also depends on the CPU class, since shared vCPUs guarantee 6.25% of a core and get throttled under long load.

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. Fly.io Machines 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.

ScenarioFly.io Machines, a monthRailway, a monthboat, 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
$15 · Pay As You Go · with limits$16 · Hobby · with limits$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$36 · Pay As You Go · with limits$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
$487 · Pay As You Go · with limits$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
$110 · Pay As You Go · 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
$232 · Pay As You Go · with limits$781 · Pro · with limits$8,800 · $2000/mo · with limits

Fly.io Machines: Fly bills each Machine per second while it runs, by CPU preset and memory, with no plan fee. Stopped Machines pay for their root file system, and Volumes bill for their full size all month. The figures here use shared vCPUs bought in 1-year reservation blocks for 40% off, Fly's lowest rate.

Railway: Railway bills sandboxes per second at about $50 per vCPU-month on CPU used and $50 per GB-month on memory in use, which keeps billing while a sandbox waits. A nearly idle sandbox can cost less there than on boat. Free costs $0 with $1 of usage a month; the Hobby ($5) and Pro ($20) fees count toward usage. Sandbox disk has no published price, so it is left 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. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs. A stopped sandbox has no compute charge; extra saved snapshots and the optional AI credentials proxy still charge. The $20 plan includes 200 starts a day; extra starts cost $0.03 to $0.07 each.

Limits in those scenarios

Both are marked as a different kind of product, an app platform, in the priced scenarios. Fly's lowest figures need a 1-year reservation and use shared vCPUs that guarantee 6.25% of each core, so long builds get throttled, and its API takes about one create request per second per app. Railway caps sandboxes at 50 per environment on Hobby and 100 on Pro, has no published disk price, and does not document Docker inside for the 50-agent fleet. On boat the 1,000-job burst needs more starts than the $2,000 plan includes, so paid extra starts bring its bill to $8,800, and starts above 270 a minute fail with 429.

ScenarioFly.io MachinesRailwayboat
One coding agent, workdays
  • different kind of product: app platform
  • files survive a stop only in one Fly Volume (root file system too with opt-in persist_rootfs): packages installed elsewhere reset
  • 1-year commitment
  • burstable CPU: 6.25% of each vCPU guaranteed, throttled above that
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
None for this scenario
One agent that never stops
  • different kind of product: app platform
  • files survive a stop only in one Fly Volume (root file system too with opt-in persist_rootfs): packages installed elsewhere reset
  • 1-year commitment
  • burstable CPU: 6.25% of each vCPU guaranteed, throttled above that
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
None for this scenario
50 agents in parallel
  • different kind of product: app platform
  • files survive a stop only in one Fly Volume (root file system too with opt-in persist_rootfs): packages installed elsewhere reset
  • 1-year commitment
  • burstable CPU: 6.25% of each vCPU guaranteed, throttled above that
  • not confirmed: Docker inside
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
None for this scenario
Sandboxes for your users
  • different kind of product: app platform
  • 1-year commitment
  • burstable CPU: 6.25% of each vCPU guaranteed, throttled above that
  • Pro: max 100 concurrent
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
None for this scenario
1,000 short jobs at once
  • different kind of product: app platform
  • 1-year commitment
  • burstable CPU: 6.25% of each vCPU guaranteed, throttled above that
  • Pro: max 100 concurrent
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use Fly.io Machines when

you want to build your own machines from a Docker image, run them near users in many regions, and let them sleep and wake on traffic.

  • 17 regions worldwide. Useful if users are spread around the world: Fly runs Machines in 17 regions, from the US to Sydney and Johannesburg.
  • Wake on request and memory suspend. Useful for services that sleep between requests: Fly Proxy wakes a Machine on traffic, and small Machines resume with memory kept.
  • Build any machine you want. Useful if you want full control: you boot your own Docker image, and network policies limit which ports it can reach.

Use Railway when

your app and databases already live on Railway and you want ready sandboxes with an SDK, forks and coding agents for short jobs on the same private network.

  • A sandbox API out of the box. Useful if you want sandboxes without building them: Railway gives you an SDK, templates, forks and checkpoints, with coding agents preinstalled.
  • 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.
  • Short jobs that bill for CPU used. Useful for many quick code runs: a Railway sandbox bills for CPU used and ends when the job ends.

Where boat fits

Fly.io Machines and Railway are app platforms first. On Fly you set up a Volume or persist_rootfs for lasting files, and on Railway you take checkpoints before the idle timeout or use a Cloud Agent. If you run agents that work for hours, boat gives each one a full VM that saves its disk with no code, with Docker, /dev/kvm, a desktop and coding agents you drive from outside. boat's limits: start caps per plan and no US or Asia region.

A disk saved with no code

On Fly, lasting files need a Volume billed for its full size all month, or persist_rootfs, which Fly says not to trust with critical data. Railway destroys a sandbox after 30 idle minutes by default unless you checkpoint it, or turn the timeout off and keep paying for memory. boat saves the disk every minute and at each stop; a machine failure loses what was written after the last good snapshot.

Docker, /dev/kvm and a desktop ready

Fly does not document /dev/kvm or systemd as PID 1, and you build the desktop into your image. Railway's docs do not mention Docker, and you add a desktop with its template builder. boat ships all of it on every sandbox.

Agents driven from outside

On Fly you install agents and run your own tokenizer app to keep keys out. On Railway you run each agent through exec, and its API key sits in the VM. boat adds a prompt, steer and events API, and an optional paid credentials proxy.

Use boat when your agents work for hours or days: a full VM that saves its disk with no code, with Docker, /dev/kvm, a desktop and coding agents you drive by API. Compare it one to one: boat vs Fly.io Machines 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 Fly.io Machines cheaper than Railway?

In most of our scenarios, yes. One agent running all month is $36 on Fly and $70 on Railway, 50 agents in parallel are $487 against $739, and 1,000 short jobs at once are $232 against $781. One agent on workdays is $15 against $16. Fly's figures assume a 1-year reservation of shared vCPUs, and Railway's leave out disk, which it does not price.

Which is faster, Fly.io Machines or Railway?

Neither is in the public benchmarks we use, so we cannot say. On Fly, shared vCPUs are throttled after their burst balance runs out, so pick performance vCPUs for long CPU-heavy work. boat did 28.06 V8 Web Tooling runs per second in StarSling's run of 3 October 2026, on a Ryzen 9 9950X host.

Can Fly.io Machines or Railway run Docker?

You can install and run Docker inside a Fly Machine yourself; Fly does not document /dev/kvm for nested VMs. Railway's sandbox docs do not mention Docker or /dev/kvm, so you install and check them yourself. boat has Docker, systemd and /dev/kvm ready on every sandbox.

Do they keep my files when a machine stops?

On Fly, the Volume keeps files, and opt-in persist_rootfs keeps the root file system, which Fly says not to trust with critical data. Railway destroys a sandbox after its idle timeout, 30 minutes by default, so you keep files with checkpoints or use a Cloud Agent. boat saves the whole disk every minute and at each stop, and keeps it at least 14 days, longer with a saved snapshot.

Which one has coding agents built in?

Railway's default sandbox image includes Claude Code, Codex, OpenCode and Pi, which you run through exec. Fly Machines have none built in; you add them to your own image, and Fly's separate Sprites product ships them. boat installs seven coding agents and lets you prompt, steer and watch them through an API.

Where do Fly.io Machines and Railway run?

Fly runs Machines in 17 regions on six continents. Railway runs in California, Virginia, Amsterdam and Singapore, and new sandboxes start in US West unless you pick a region. boat runs sandboxes in Germany, Finland and France; snapshot copies can be stored outside the EU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons