Railway vs Vercel
Two sides of the hosting decision: paaS and frontend cloud. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- 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.
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Use it whenYour app is Next.js, or you want a preview URL on every pull request with no setup.
Trade-offThe Hobby plan is non-commercial; costs grow with usage.
At a glance
| Used by | 112 makers' products | No maker's product yet |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $45/mo Hobby | $40/mo Pro + Flat Rate CDN 10M |
| Moved to it on GitHubpull requests since Oct 2024 | 94 from Vercel | 29 from Railway |
| Downloads | 5.7M/wk+93% vs npm | |
| Pricing | Usage-based with a small monthly minimum. · paid from $5/mo minimum usage | Free Hobby plan (non-commercial); Pro per seat plus usage. · paid from $20/mo |
| Free tier | No | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | no public status feed | 31 (10 major) |
Cost as you grow
At 100k requests Vercel costs less ($0 vs $40); from about 50M requests Railway does ($90 vs $127). They're different kinds of tool — paaS and frontend cloud — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Railway | Vercel |
|---|---|---|
| 0.1 | $40 Hobby | $0 Hobby |
| 0.5 | $41 Hobby | $0 Hobby |
| 1 | $41 Hobby | $0 Hobby |
| 5 | $45 Hobby | $40 Pro + Flat Rate CDN 10M |
| 10 | $50 Hobby | $40 Pro + Flat Rate CDN 10M |
| 50 | $90 Hobby | $127 Pro + Flat Rate CDN 50M |
| 100 | $140 Hobby | $353 Pro + Flat Rate CDN 150M |
| 500 | $540 Hobby | $2,766 Pro (on-demand CDN) |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Railway to Vercel" or the reverse — real code changes, by developers in general rather than makers only.
- chore(deploy): prepare migration from Vercel to Railwaycuongnc0211/roadmate · 2026-10-02
- Review pages before capturing; forward Vercel address to RailwayGenuineJack/site-snapper · 2026-09-30
- Connect Vercel dashboard to Railway APIRajvardhanPatil07/AirTwin · 2026-09-28
- Redirect the Vercel root path to Railway tooyouthachrist-web/protocolo-nordico · 2026-09-28
- Vercel: pass the root path through to Railwayidanmann10/persona-onboarding · 2026-09-28
- Migrate vercel to railwaywhartonAIclub/penn-tools · 2026-09-28
- Redirect Vercel to Railway and handle missing upsell PDF gracefullyyouthachrist-web/protocolo-nordico · 2026-09-28
- chore: setup vercel proxy to railway backendSIH-2026-RRAKSS/sihweb · 2026-09-25
- Configure Vercel to Railway connectivitykwizeraherve70/african_gcv_website · 2026-09-24
- DR-119 hotfix: route Vercel to live Railway hostnamedocbennyt/EchoZW · 2026-09-16
- Migrate BlackVision backend from Railway to Vercelblackvisionbr-eng/Black-Vision-projeto · 2026-09-09
- Migrate StudiosBook API from Railway to Vercelblackvisionbr-eng/studiosbook · 2026-09-09
- Swap hosting target from Railway to Vercel (Postgres + Blob + Cron)hipaasynth-svg/Whiskr · 2026-09-05
- feat(deploy): migrate hosting from Railway to Vercel + Supabasewillieavendano/qlass-lms · 2026-09-01
- Migrate backend from Railway (persistent server) to Vercel (serverless)roicherian/ACKO-Gen · 2026-08-31
- Scope Railway API fallback to Vercel productionleaguesports/landing-page · 2026-08-29
- Migrate hosting from Railway to Vercel + NeonOlowodarey/pmovies · 2026-08-16
- Migrate from Railway to Vercel: fold API and worker into the web app, replace BullMQ with durable workflowscrodris/Overlap · 2026-08-13
- chore: migrate deployment from Railway to VercelBrettConetta/my-portfolio · 2026-07-02
- chore(deploy): migrate dashboard from Railway to VercelRECTOR-LABS/quittance · 2026-07-02
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.
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.
No maker quote about Vercel for hosting yet.
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

