Railway vs Upstash Box

Railway is an app platform whose sandboxes are Linux VMs next to your apps and databases. Railway destroys a sandbox after its idle timeout, and files survive in checkpoints you take. Upstash Box gives each agent a light Docker container that bills only busy CPU, pauses when idle, keeps its files, and wakes on the next request.

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.

Upstash Box

Upstash Box is a cloud computer for AI agents from Upstash, the company known for serverless Redis, Vector and QStash.

Each box is a Docker container with its own filesystem, shell, git and an optional coding agent such as Claude Code, Codex, OpenCode or Cursor, which you drive from TypeScript or Python SDKs. A box pauses when it sits idle, keeps its files, and you pay for the CPU it actually uses. Upstash built it to run its own Context7 service and opened it to everyone in March 2026.

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 workloadRailway: price rankUpstash Box: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Both are a compromise for a software factory. Railway sandboxes are destroyed at the idle timeout unless you checkpoint them, and Railway does not document Docker. Upstash does not document Docker inside a box, which is itself a container. boat saves the disk with no code and documents Docker.
28th cheapest of 365
$1,481 a month
98th of 365, with limits
$464 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 with the idle timeout set to 0, or a Cloud Agent (Priority Boarding); memory bills the whole time. Upstash keeps an agent on all month in a keep-alive container at a flat monthly price.
21st cheapest of 361
$3,977 a month
170th of 361, with limits
$450 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
Upstash fits short code runs well, because an idle box costs no CPU and RAM is not billed. Railway bills CPU used and memory in use. boat's $20 plan includes 12 starts per minute and 200 per day.
42nd cheapest of 336
$413 a month
13th cheapest of 336
$119 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
Upstash fits sandboxes for your users: 1,000 boxes at once on Pay as You Go, and a request wakes a paused box. Railway's cap of 100 sandboxes per environment on Pro makes 300 users at once a compromise. boat allows 300 at once from the $100 plan.
46th of 349, with limits
$290 a month
4th cheapest of 349
$222 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
343rd of 349, with limits
$8,000 a month
39th of 349, with limits
$2,000 a month
Agent evals
250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month
113th of 359, with limits
$364 a month
67th cheapest of 359
$1,011 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 jobs that build containers need Docker. Railway's sandbox docs do not mention it, so you install and verify it yourself, and Upstash does not document it inside a box. boat documents Docker and /dev/kvm on every sandbox.
116th cheapest of 374
$1,210 a month
122nd cheapest of 374
$1,480 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
A flat-price keep-alive box makes Upstash a cheap light dev box, with up to 30 GB of disk. Railway's Cloud Agents keep their disk, but are in Priority Boarding and fixed at 4 vCPU / 4 GB on Pro. boat's default size has a 51 GB disk.
69th cheapest of 371
$89 a month
8th cheapest of 371
$19 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
Neither includes a full desktop. On Railway you can add Xvfb and noVNC with the template builder. Upstash runs Chromium on a virtual display with a view-only live view, and has no desktop or VNC. boat streams a full desktop at 60 fps.
47th cheapest of 367
$407 a month
123rd of 367, with limits
$76 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
48th of 356, with limits
$38 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
41st cheapest of 343
$400 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
201st of 327, with limits
$8,000 a month
73rd of 327, with limits
$1,800 a month
Parallel red teaming
200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month
71st of 351, with limits
$574 a month
255th of 351, with limits
$259 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

FeatureRailwayUpstash Boxboat
IsolationSandboxes and Cloud Agents are isolated Linux VMs; app services are containersOne Docker container per box on AWSFull VM with its own kernel, on physical hosts dedicated to boat; vCPUs are shared
When the sandbox goes idleDestroyed after the idle timeout (30 minutes by default); files survive in checkpoints you takeNo CPU charge while idle; pauses after 6 hours idle on paid plans and keeps its files; storage keeps billing while pausedFull rate while running, busy or idle; auto-stop after 1 hour by default; disk kept at least 14 days with no compute charge
Docker and nested virtualizationRoot shell on an Ubuntu VM; Docker and /dev/kvm are not documented, so you install and verify them yourselfNot documented; the box is itself a Docker container, and custom images are listed as coming soonDocker, root, systemd and /dev/kvm documented on every sandbox
Biggest machine8 vCPU / 8 GB on Hobby; on Pro up to 32 vCPU / 32 GB per the docs (24 vCPU / 24 GB per the pricing page)Large: 8 vCPU / 16 GB on self-serve plans; custom sizes on Enterprise8 vCPU / 16 GB on the $20 plan, 16 vCPU / 32 GB from $100
DiskSandbox disk size and price are not published10, 20 or 30 GB by size, billed per GB-month51 GB at the default 4 vCPU / 8 GB size, 51 to 251 GB by size; fixed per size
Wake on requestNo; you boot a new sandbox from a checkpointYes; a request to a public URL resumes a paused box and waits for the appNo; a stopped sandbox is started by API
Sandboxes at oncePer environment: 10 on Free, 50 on Hobby, 100 on Pro; Enterprise can ask for more1,000 on Pay as You Go, raised on request; no start limit published100 to 2,000 by plan; starts limited per minute, hour and day (12 / 60 / 200 on $20)
Desktop and browserNo desktop included; you can add Xvfb and noVNC with the template builder and publish the port on a sandbox domainManaged Chromium with AI page actions, CDP, screenshots, recordings and a view-only live view; no desktop or VNCBuilt-in desktop and Chrome at 1920x1080, 60 fps, with computer-use tools
Reaching the sandboxUp to 10 public HTTPS domains, set only at creation, with no built-in auth; SSH and port forwardingHTTPS URL per port, public unless you add a token or basic auth; SSH through a gateway; no raw TCP documentedUp to 50 HTTPS URLs, token-gated by default; SSH; raw ports over public IPv6; no dedicated IPv4
Outbound rulesNo outbound allowlist for sandboxesAllow all, deny all, or allow and deny by domain and CIDR, changeable on a running boxOpen internet, no provider-side allowlist
Coding agentsClaude Code, Codex, OpenCode and Pi in the image, run through execClaude Code, Codex, OpenCode and Cursor built in, with run and stream APIs, webhooks and scheduled promptsSeven harnesses installed, with a prompt, steer and events API
Keeping API keys out of the sandboxSecrets go into the sandbox as environment variables, or are signed in and saved in a checkpointHost proxy injects headers into outbound HTTPS on port 443 for any host; set when the box is createdOptional paid proxy ($1 a day when on, plus $1 per 1,000 requests) for supported model providers; other secrets still enter
Apps and databases next to the sandboxDeploy Postgres, Redis and services in the same project; a sandbox can join their private networkNo private network for boxesNo hosted databases or app services; host your own inside a sandbox
RegionsUS West, US East, Amsterdam and SingaporeAWS us-east-1; custom regions on EnterpriseGermany, Finland and France; you cannot pick a region; no US or Asia region
Every feature Battleships tracks (43)
FeatureRailwayUpstash Boxboat
Full VM (own kernel)YesNo documented wayYes
Docker insideNot publishedNot publishedYes
Nested virtualizationNot publishedNo documented wayYes
RootYesNot publishedYes
SystemdNot publishedNot publishedYes
Desktop GUIWith your own setupNo documented wayYes
BrowserYesYesYes
Computer-use APINo documented wayNo documented wayYes
SSHYesYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsNo documented wayNo 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 requestNo documented wayYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistNo documented wayYesNo documented way
Secret proxyNo documented wayYesYes
Secret proxy for any APINo documented wayYesYes
Preinstalled agentsYesYesYes
Agent harness APIYesYesYes
MCP serverYesYesNo documented way
GPUNo documented wayNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayYesNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCYesNo documented wayNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsYesNot publishedYes
Usage per sandbox (API)No documented wayYesYes
Audit logsYesNot publishedNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesYesNo documented way
HIPAAYesNo documented wayNo documented way
EU data residencyYesNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

RailwayNot measured
Upstash BoxNot measured
boat28.06 runs/s

Railway and Upstash Box are not in StarSling's CPU benchmark, so we cannot say which runs code 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. ComputeSDK measured Upstash Box at its default size: a median of 2.34 s to the first command with 100 at once (2026-11-06). Railway and boat are not in ComputeSDK.

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 Upstash Box 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.

ScenarioRailway, a monthUpstash Box, 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
$16 · Hobby · with limits$21 · Pay as You Go$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$70 · Hobby · with limits$21 · Pay as You Go$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$900 · Pay as You Go · with limits$317 · $20/mo × 3 seats
Sandboxes for your users
2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once
$223 · Pro · with limits$306 · Pay as You Go$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$1,822 · Pay as You Go$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.

Upstash Box: A standard box is billed for CPU it actually uses, at $0.10, $0.20 or $0.40 per active CPU hour for Small, Medium and Large, plus $0.10 per GB-month of storage, and RAM is free. Pay as You Go has no monthly fee. A keep-alive box costs a flat $8, $16 or $32 a month whether busy or not.

Upstash Box: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A default 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, 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. Its cap of 100 sandboxes per environment on Pro means 300 users or 1,000 jobs at once need several environments or an Enterprise limit. Upstash does not document Docker inside a box, so the 50-agent scenario does not fit there, and its egress price is not published. 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.

ScenarioRailwayUpstash Boxboat
One coding agent, workdays
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
One agent that never stops
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
50 agents in parallel
  • not confirmed: Docker inside
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
  • not confirmed: Docker inside
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
Sandboxes for your users
  • Pro: max 100 concurrent
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
  • egress price not published
None for this scenario
1,000 short jobs at once
  • Pro: max 100 concurrent
  • different kind of product: app platform
  • disk beyond 0 GiB: price unknown
  • egress price not published
  • 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 Railway when

your app and databases already live on Railway and you want VM sandboxes on the same private network, bigger machines, or regions in the US, EU and Asia.

  • Your apps and databases in one place. Useful if your app already runs on Railway: a sandbox can join the private network of your Postgres and services.
  • Regions on three continents. Useful if your users are spread out: Railway runs in California, Virginia, Amsterdam and Singapore; Upstash Box runs in us-east-1 on self-serve plans.
  • Bigger VMs. Useful for heavy builds: Railway sandboxes are VMs that go up to 24 to 32 vCPU on Pro, against 8 vCPU / 16 GB on Upstash self-serve.

Use Upstash Box when

your agents mostly wait, need to wake on an incoming request, must stay inside a strict outbound allowlist, or you need 1,000 boxes at once in the US.

  • Idle costs no CPU, and a request wakes the box. Good for agents that wait a lot: an idle box costs no CPU, RAM is free, and a request to its URL wakes it.
  • Outbound network rules. Useful when an agent may only reach a short list of domains or IP ranges, changeable on a running box.
  • Many boxes at once. Useful for big bursts: Pay as You Go runs 1,000 boxes at once, where Railway caps Pro at 100 per environment.

Where boat fits

For agents that work for hours or days and need a real machine, boat gives each one a full VM with Docker, /dev/kvm and a 60 fps desktop. It stops instead of disappearing, saves its disk with no code, and runs coding agents you drive by API. boat runs only in the EU, bills a running sandbox busy or idle, and limits starts by plan.

Docker and KVM, documented

An Upstash box is itself a container, and its docs do not mention Docker inside. Railway's sandbox docs do not mention Docker or /dev/kvm, so you install and verify them yourself. boat documents both on every sandbox.

A disk that stays, with room to work

Railway destroys an idle sandbox after 30 minutes by default unless you take a checkpoint, and turning that off keeps memory billing. Upstash keeps files, but disks stop at 30 GB. boat saves a 51 GB disk at the default size every minute and at each stop, and keeps it for at least 14 days. A boat resume is like a reboot.

A desktop the agent can see

Railway includes no desktop, though you can install one, and Upstash gives a Chromium driven over CDP with a view-only live view. A computer-use agent on boat gets a full Linux desktop at 60 fps, with desktop apps and dialogs in reach.

Use boat when your agents need a real machine for hours or days: Docker, /dev/kvm, a desktop, a disk above 30 GB that is saved with no code, and coding agents you drive by API. Compare it one to one: boat vs Railway and boat vs Upstash Box.

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 Upstash Box?

In most scenarios on this page, yes: one agent on workdays is $16 against $21, sandboxes for your users are $223 against $306, and 1,000 short jobs at once are $781 against $1,822. Upstash is lower for one agent that never stops, $21 against $70. Railway's numbers leave out disk, which it does not price. boat comes to $20, $200 and $26 for the workday, user and always-on jobs.

Which is faster, Railway or Upstash Box?

Neither is in StarSling's public CPU benchmark, so there is no fair comparison. 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 Upstash Box run Docker?

Railway's sandbox docs give you a root shell on an Ubuntu VM but do not mention Docker, so you install and verify it yourself. Each Upstash box is itself a Docker container, and custom images are listed as coming soon. boat sandboxes are full VMs where Docker, docker compose and systemd work as on any Linux server.

Are Railway sandboxes and Upstash boxes VMs or containers?

Railway calls each sandbox a fully isolated virtual machine, while its app services are containers. An Upstash box is a Docker container with its own filesystem, process tree and network stack. Every boat sandbox is a full VM with its own kernel.

What happens when a sandbox goes idle?

Railway destroys it once the idle timeout runs out, 30 minutes by default, unless you set it to 0; the checkpoints you took survive. Upstash bills no CPU while a box is idle, pauses it after 6 hours idle on paid plans, keeps its files and wakes it on the next request. 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.

Where do Railway and Upstash Box run?

Railway has regions in California, Virginia, Amsterdam and Singapore, and new sandboxes start in US West unless you pick one. Upstash Box runs in AWS us-east-1 on self-serve plans, with custom regions on Enterprise. boat runs only in Germany, Finland and France, and you cannot pick a region.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons