Railway's pricing trips up developers who assume it works like Vercel or Netlify with a generous free tier and predictable monthly bills. It doesn't — it's usage-based, and the bill can climb fast once you move past hobby projects. Here's what you're actually paying for in 2026.
How Railway pricing actually works
Railway bills on three axes: compute (vCPU-hours), memory (GB-hours), and egress (GB). There's no seat-based pricing and no per-project fee. Every service you spin up — a Next.js app, a Postgres instance, a Redis container, a background worker — accumulates compute and memory cost independently.
This is the first gotcha: a monorepo with three separate Railway services isn't one bill line, it's three. A typical Next.js + Postgres + Redis stack is billing on all three simultaneously, 24/7, even if traffic is zero — unless you enable Railway's Serverless (app sleeping) option on services that can tolerate a cold start.
Railway free tier limits in 2026
The Hobby plan costs $5/month and includes $5 of usage each month. If your services stay within that credit, you pay only the base $5. Exceed it and Railway charges the overage at standard rates. List rates at the time of writing (check railway.com/pricing):
| Resource | Rate (billed per second) | Roughly per month |
|---|---|---|
| vCPU | $0.00000772 / vCPU-second | ~$20 per vCPU |
| Memory | $0.00000386 / GB-second | ~$10 per GB |
| Egress | $0.05 / GB | — |
| Volume storage (e.g. Postgres data) | $0.00000006 / GB-second | ~$0.15 per GB |
| Hobby limits | 3 members per project, up to 48 vCPU / 48 GB and 6 replicas per service | — |
The credit math is easy to exhaust. A single 512 MB Node.js service running continuously costs roughly 0.5 GB × 3600 s × 24 h × 30 d × $0.00000386/GB-s ≈ $5/month in memory alone — the whole credit, before CPU. Add a small Postgres instance and a Redis container and you're paying overage. The $5 base is essentially the minimum floor, not a ceiling.
The free trial (no credit card) gives a one-time $5 credit that expires after 30 days. There's also a Free plan with $1 of monthly usage and small per-service limits (1 vCPU / 0.5 GB). Either is enough for testing — not a production staging environment.
Pro plan: what changes
The Pro plan costs $20/month per workspace and includes $20 of monthly usage; you pay usage above that. You get:
- Unlimited workspace members (seats are included in the workspace fee)
- Much higher per-service ceilings — up to 1,000 vCPU / 1 TB RAM and 42 replicas per service
- Longer log history and team-oriented features (check the pricing page for the current list)
For a small agency running client staging environments, Pro makes sense at around two to three active projects. Below that, Hobby per-workspace is cheaper even if you're paying overages.
What triggers an upgrade on a real Next.js project
Four things push teams off Hobby faster than expected:
1. Persistent services. By default every service runs 24/7. Railway's Serverless setting can sleep a service after roughly 10 minutes without outbound traffic, but the first request after that is slow (or can 502), and databases generally shouldn't sleep. A Postgres database costs compute and memory even at midnight on a weekend.
2. Egress on media-heavy apps. If your Next.js app serves images or video directly from Railway (not from a CDN), the $0.05/GB egress rate accumulates. A site doing 50 GB/month of image traffic adds $2.50 — and it scales linearly with traffic. Sanity's CDN or Cloudinary sidesteps this — Railway is not an image host.
3. Preview environments. Running a branch deploy for each PR means each open PR is a live service. Three open PRs with a database each = six services billing simultaneously. Teams using Railway for CI preview environments should budget $15–30/month more than their production cost.
4. Background workers. A queue worker that runs 24/7 at 0.25 vCPU is roughly 0.25 × 3600 × 24 × 30 × $0.00000772/vCPU-s ≈ $5/month in compute, plus its memory. Two or three of those on Hobby and you're well past the included credit. (For jobs that only run periodically, Railway's cron schedules avoid paying for idle time.)
Railway vs Vercel vs Render: cost comparison for Next.js
| Scenario | Railway Hobby | Vercel Pro | Render Starter |
|---|---|---|---|
| Next.js app only (no backend) | $5 + usage | $20 + usage over included credit | $7/service/mo |
| Next.js + Postgres | $5 + ~$5–12 usage | Via Marketplace provider | $7 + managed DB plan |
| Three preview environments | $5 + ~$15 usage | Included | $21+ |
| Team of 3 | $5 (up to 3 members per project) | $20 per developer seat | $7/service |
| Background worker | $5 + ~$10–30 usage | N/A (Vercel functions only) | $7/worker |
Vercel is almost always cheaper for a pure Next.js front-end with no backend services. Railway's advantage is the ability to run arbitrary Docker containers alongside your Next.js app — Postgres, Redis, custom workers — without managing a VPS. Render is competitive on fixed-cost services but slower builds.
When Railway is the right call
Railway wins on developer experience for full-stack apps that need multiple services: a Node.js or Python API, a database, a background queue, and a Next.js front-end — all wired together with private networking and zero infrastructure config. For that pattern, the usage billing is worth the simplicity compared to stitching together Vercel + Supabase + Upstash.
It's the wrong choice if your Next.js app is primarily content-driven and Sanity (or any other headless CMS) handles the data layer. In that case you're paying Railway's 24/7 compute for a Next.js process that could run serverlessly on Vercel Pro from $20/month — or free on Vercel's Hobby tier for personal, non-commercial projects.
The upgrade threshold in practice
Budget $20–40/month for a real Hobby-tier full-stack project once usage is counted honestly. If you need larger teams or bigger per-service limits, the Pro plan at $20 base (including $20 of usage) is still reasonable against AWS or GCP equivalents. The ceiling on Pro is uncapped — large teams with many services should request Railway's volume pricing or evaluate self-hosted Coolify/Dokku on a dedicated VPS, which can be cheaper above ~$150/month total spend.
Top comments (0)