Railway
Application platform that builds services from a repository or Dockerfile and bills plan fees that include usage credits.
- paas
- Yes
- $5 / month (Hobby)
- 4 regions: California, Virginia, Amsterdam, Singapore
Who it suits.
Teams that want a plan fee which doubles as usage credit, and deploy services straight from a Dockerfile without managing servers. The $5 Hobby fee comes back as $5 of resource usage.
Consider something else if…
You need to run in a region outside California, Virginia, Amsterdam or Singapore.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Railway does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Railway plans ↗
“Free Plan: For running small apps with $1 of free credit per month”
Read 2026-09-05 · official docs
Entry paid plan
$5 / month (Hobby)
Sources (1) →Sources ↓
- Railway plans ↗
“Hobby Plan: For indie hackers and developers to build and deploy personal projects — $5/month”
Read 2026-09-05 · official docs
Pricing model
Plan fee that includes an equivalent usage credit
Sources (1) →Sources ↓
- Railway plans ↗
“The Hobby plan includes $5 of resource usage per month. The Pro plan includes $20 of resource usage per month.”
Read 2026-09-05 · official docs
Egress over allowance
$0.05 / GB
Sources (1) →Sources ↓
- Plans | Railway Docs ↗
“Network Egress | $0.05 / GB ($0.000000047683716 / KB)”
Read 2026-09-05 · official pricing
When you exceed a cap
Billed automatically: on the Hobby plan ($5/month, includes $5 of resource usage) usage above the included amount is charged as a delta on top of the subscription — no throttling or suspension is documented
Sources (1) →Sources ↓
- Pricing Plans | Railway Docs ↗
“If your total resource usage exceeds $5 in any given billing period, you will be charged the delta”
Read 2026-09-05 · official docs
Limits
Storage (entry plan)
5 GB maximum volume size on the Hobby plan ($5/month); volume storage is not included, it is billed on usage
Sources (1) →Sources ↓
- Pricing | Railway ↗
“Max volume size | 5 GB | 1000 GB”
Read 2026-09-05 · official pricing
Sites or apps included
50 projects and 50 services on the Hobby plan ($5/month); 3 members per project (Pro: 100 projects, 100 services)
Sources (1) →Sources ↓
- Pricing | Railway ↗
“Projects | 50 | 100”
Read 2026-09-05 · official pricing
Monthly visits cap
No monthly visit or bandwidth cap is published. Rate limits are enforced platform-wide on all services and all plans: approximately 11,000 HTTP requests/sec per domain and 10,000 concurrent connections
Sources (1) →Sources ↓
- Specs & Limits | Railway Docs ↗
“HTTP Requests/Sec | 11,000~ RPS | The number of HTTP requests to a given domain per second.”
Read 2026-09-05 · official docs
Max request duration
15 minutes while data keeps transferring; closed after 5 minutes with no data transferred. Websocket connections are exempt and can stay open indefinitely.
Sources (1) →Sources ↓
- Specs & Limits — Railway Docs ↗
“HTTP requests can run for up to 15 minutes if data keeps transferring (for example, keep-alive heartbeats), and are otherwise closed after 5 minutes with no data transferred. [...] Websocket connections are exempt from these duration and inactivity limits, and can stay open indefinitely, even while idle.”
Read 2026-09-05 · official docs
Execution
Streaming response limit
Platform-wide: a stream that keeps transferring data may run up to 15 minutes; a connection with no data transferred is closed after 5 minutes. Idle HTTP/1.1 connections are closed after 60 seconds between requests. WebSocket connections are exempt.
Sources (1) →Sources ↓
- Specs & Limits ↗
“HTTP requests can run for up to 15 minutes if data keeps transferring (for example, keep-alive heartbeats), and are otherwise closed after 5 minutes with no data transferred. [...] Websocket connections are exempt from these duration and inactivity limits, and can stay open indefinitely, even while idle.”
Read 2026-09-05 · official docs
Managed connection pooling
Supported
Sources (1) →Sources ↓
- PostgreSQL Connection Pooling — Railway Docs ↗
“Railway can add PgBouncer as a connection pooler in front of your PostgreSQL service. PgBouncer multiplexes many application connections into a smaller pool of server connections, reducing overhead and allowing your database to serve far more concurrent clients than max_connections alone would permit.”
Read 2026-09-05 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- Controlling GitHub Autodeploys — Railway Docs ↗
“Services linked to a GitHub repository automatically deploy when new commits are pushed to the connected branch.”
Read 2026-09-05 · official docs
Docker deployment
Supported
Sources (1) →Sources ↓
- Railway Dockerfiles ↗
“Use a Dockerfile to instruct Railway how to build a service.”
Read 2026-09-05 · official docs
Scheduled jobs
Supported
Sources (1) →Sources ↓
- Cron Jobs | Railway Docs ↗
“Cron Jobs allow you to start a service based on a crontab expression. [...] The shortest time between successive executions of a cron job cannot be less than 5 minutes.”
Read 2026-09-05 · official docs
Infrastructure
Persistent processes
Supported
Sources (1) →Sources ↓
- Services — Railway Docs ↗
“Persistent services: Services that are always running. Examples include web applications, backend APIs, message queues, database services, etc.”
Read 2026-09-05 · official docs
Persistent storage
Supported
Sources (1) →Sources ↓
- Volumes | Railway Docs ↗
“Volumes are a feature that enables persistent data for services on Railway. [...] When mounting a volume to a service, a volume is made available to the service on the specified mount path.”
Read 2026-09-05 · official docs
Managed databases
Limited
Sources (1) →Sources ↓
- Databases — Railway Docs ↗
“Railway enables you to deploy and manage databases alongside your applications. [...] The fastest way to deploy a database is through Railway's database templates [...] These templates are maintained by Railway and come pre-configured with sensible defaults.”
Read 2026-09-05 · official docs
Edge network
Supported
Sources (1) →Sources ↓
- Edge Networking — Railway Docs ↗
“Railway uses a globally distributed edge network to route traffic to your deployments. [...] Edge POPs are the entry points where user traffic first reaches Railway. Each request is terminated at the nearest POP and tagged with that POP's ID in the X-Railway-Edge header.”
Read 2026-09-05 · official docs
Scales to zero
Limited
Sources (1) →Sources ↓
- Serverless (App Sleeping) | Railway Docs ↗
“Serverless allows you to increase the efficiency of resource utilization on Railway and may reduce the usage cost of a service, by ensuring it is running only when necessary. [...] When Serverless is enabled for a service, Railway automatically detects inactivity based on outbound traffic. [...] Inactivity is sampled on an interval rather than measured continuously, so in practice a service sleeps somewhere between 5 and 10 minutes after its last outbound traffic. [...] Slept services still consume a slot on Railway's infrastructure.”
Read 2026-09-05 · official docs
Autoscaling
Limited
Sources (1) →Sources ↓
- Scaling | Railway Docs ↗
“Scaling your applications in Railway is made easy with configurable options for horizontal scaling as well as vertical autoscaling out-of-the-box. [...] Scale horizontally by manually increasing the number of replicas for a service in the service settings.”
Read 2026-09-05 · official docs
Regions
4 regions: California, Virginia, Amsterdam, Singapore
Sources (1) →Sources ↓
- Railway regions ↗
“US West Metal — California, USA; US East Metal — Virginia, USA; EU West Metal — Amsterdam, Netherlands; Southeast Asia Metal — Singapore”
Read 2026-09-05 · official docs