Cloudflare vs Railway
Two sides of the hosting decision: edge platform and paaS. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- Your app is a static site or docs and should cost nothing to host
Use it whenYou want the cheapest global hosting and can live with the Workers runtime.
Trade-offThe Workers runtime isn't full Node.js; some libraries need adapting.
- You have a long-running server, a background worker and a database to deploy together
Use it whenYour app is a server plus a database and a worker, and you want them in one project.
Trade-offUsage-based billing needs watching; fewer regions and compliance options than a hyperscaler.
At a glance
| Used by | 375 makers' products · 190 open-source projects | 112 makers' products |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $12/mo Workers Paid | $45/mo Hobby |
| Moved to it on GitHubpull requests since Oct 2024 | 19 from Railway | 6 from Cloudflare |
| Downloads | 18.6M/wk3.1× vs npm | |
| Pricing | Generous free tier; usage-based paid plans. · paid from $5/mo (Workers Paid) | Usage-based with a small monthly minimum. · paid from $5/mo minimum usage |
| Free tier | Yes | No |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | 50+ | no public status feed |
Cost as you grow
At 100k requests Cloudflare costs less ($0 vs $40); from about 100M requests Railway does ($140 vs $175). They're different kinds of tool — edge platform and paaS — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Cloudflare | Railway |
|---|---|---|
| 0.1 | $0 Workers Free | $40 Hobby |
| 0.5 | $5.12 Workers Paid | $41 Hobby |
| 1 | $5.84 Workers Paid | $41 Hobby |
| 5 | $12 Workers Paid | $45 Hobby |
| 10 | $19 Workers Paid | $50 Hobby |
| 50 | $88 Workers Paid | $90 Hobby |
| 100 | $175 Workers Paid | $140 Hobby |
| 500 | $871 Workers Paid | $540 Hobby |
From each vendor's pricing page: Cloudflare, Railway.
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Cloudflare to Railway" or the reverse — real code changes, by developers in general rather than makers only.
- Move hosting from Railway to Cloudflare Workersbyw1/superordinary-audit · 2026-10-01
- Add safe one-way Railway to Cloudflare syncemadmir68/NabezSardo · 2026-09-21
- Port from Railway to Cloudflare Workersskazler/morning-brief-tool · 2026-07-26
- feat: migrate from Bun + Hono on Railway to Cloudflare Workersmartinzachariassen/mlz-no · 2026-07-25
- PE gratis: deploy backend to Railway, frontend to Cloudflare Workersorkait/gratis · 2026-07-12
- Migrate BuildBridge from Railway to Cloudflare WorkersCSMSYNERGY/buildbridge · 2026-07-10
- feat: migrate from Railway to Cloudflare Workersivolivares/iolivares.com-v2025 · 2026-06-30
- chore(storage): repoint chat uploads from Railway bucket to Cloudflare R299Yash/alfred · 2026-06-24
- Migrate from Railway to Cloudflare Pages with static exportbrendanciccone/portfolio · 2026-06-11
- Migrate hosting from Railway to Cloudflare Pagesbrendanciccone/tempotuner · 2026-06-11
- Custom domains: bridge Cloudflare-for-SaaS Host header to Railwayparkerron1971-hash/kmj-intake-server · 2026-07-14
- chore(deploy): migrate apps/app from cloudflare workers to railwayAyaan2907/wingmic · 2026-05-23
- Add Cloudflare R2 storage to fix ephemeral Railway filesystemfao102/Style-Finder · 2026-05-19
- Revert: roll back Cloudflare Workers migration to Railwayhalfhacked/gecko · 2026-04-28
- feat(cloudflare): DNS proxy to Railway + named tunnel for coordinator servicesjankneumann/agentic-coding-tools · 2026-04-04
- Migrate deployment from Cloudflare to Railwaylicitacaotecnogrid-bot/barreiro36018 · 2025-12-11
What makers say
Makers on using it for hosting, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
Cloudflare handles everything for iVox — DNS, website hosting on Pages, R2 file storage for downloads, and Workers for the license backend. All of it, basically free at indie scale.
Cloudflare Workers and Pages let us deploy instantly at the network edge, delivering lightning-fast performance and reliability without the usual complexities of traditional hosting.
Snapset’s website, licensing backend, and email routing all run on Cloudflare. Pages, Workers, and D1 let me keep the infrastructure simple and manage almost everything in one place.
Railway makes deploying and scaling our backend effortless. Push to main, it's live. No Dockerfiles to debug, no infra to babysit. We went from zero to production in an afternoon.
🚀 Shoutout to Railway for making API deployment a breeze! As a frontend developer without much backend experience, their platform made it super easy to set up and deploy changes.
Railway is simple and handles deployment transitions really well. Old deployments drain cleanly while new ones come up, so users are never interrupted when we ship.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Platform-wide outages, including one when Google Cloud blocked Railway's account, took customer services down. HNHN 2HN 3HN 4
- It adds a middle layer on Google Cloud that controls your availability, features and security. HNHN 2
- API tokens grant every operation without clear warnings, which let an agent instantly delete a production database. HNHN 2

