Skip to main content

Railway

Platform · PaaS

Application services, workers, functions, cron jobs, and database containers on managed infrastructure.

Railway turns source repositories, container images, and small inline functions into running services. A project groups the application with its databases, storage, networking, and environment configuration. Railway operates the underlying infrastructure, while the project remains the unit teams deploy and manage. Automatic scaling here means vertical allocation, while serverless sleep is opt-in. Database failover and point-in-time recovery refer to Railway’s native PostgreSQL HA/PITR configurations.
Best for

Product teams that want Git- or Docker-based application deployment with databases and workers in the same project, without operating the underlying servers.

Watch out for

Railway's convenience defaults are not universal guarantees. Zero-downtime deploys depend on health checks and volume layout; backups require scheduling, and database failover/PITR require native PostgreSQL HA/PITR configuration.

Workloads
  • APIs
  • Backend Services
  • Background Workers
  • Scheduled Jobs
  • Web Applications
Services
  • Compute
  • Databases
  • Functions
  • Object Storage
Hosting model
  • Managed

Development & Execution

Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.

Runtimes

  • Bun
  • Custom Runtime
  • Deno
  • .NET Runtime
  • JVM
  • Node.js

Languages

  • C#
  • Go
  • Java
  • JavaScript
  • Kotlin
  • PHP
  • Python
  • Ruby
  • Rust
  • TypeScript

Frameworks

  • Astro
  • Django
  • Express.js
  • Fastify
  • Laravel
  • Next.js
  • Nuxt
  • Remix
  • Ruby on Rails
  • Spring Boot
  • SvelteKit

Capabilities

  • Compute Autoscaling
  • Scale to Zero
  • Zero-Downtime Application Deployments
  • Deployment Rollbacks
  • Preview Environments
  • Automatic Failover
  • Point-in-Time Recovery
  • Automated Backups

Database support

  • MongoDB
  • MySQL
  • PostgreSQL

Architecture

  • x64
  • ARM

Deployment & packaging

  • Docker / OCI
  • Serverless (Managed Runtime)

Integrations

  • Datadog
  • GitHub
  • GitLab
  • Redis

Triggers

  • Scheduled Invocation
  • HTTP Requests
  • Queue Messages

Pricing

Published pricing structure, representative costs, and material billing factors.

Free Tier
Recurring free allowances No card required
Free Trial
New users receive a one-time trial credit valid for up to 30 days. No card required
Commitment
Plan fees count toward monthly resource usage additional usage is billed separately.
Starting Price
$5 / month minimum Hobby

Railway Plans

Primary Pricing

Railway plans combine monthly plan charges or credits with metered resource usage.

Free

$0 / month

The recurring post-trial plan for lightweight experimentation.

  • $1 of resource usage included per month
  • Available after the one-time trial ends
Hobby

$5 / month minimum

For personal projects with usage included in the monthly minimum.

  • $5 of resource usage included per month
  • Usage beyond the included credit is billed separately
Pro

$20 / month minimum

For production teams with higher limits and included usage.

  • $20 of resource usage included per month
  • Usage beyond the included credit is billed separately
Railway Resource Usage Additional Usage Cost

Resource consumption is billed according to actual usage.

ResourceBilling UnitPrice
Memoryper GB per month$10
CPUper vCPU per month$20
Volume storageper GB per month$0.15
Service egressper GB$0.05
Object storage Object storage egress is freeper GB-month$0.015

Free Tier

No card required

The Free plan includes a recurring monthly resource credit after the trial.

  • Resource credit: $1 usage credit per month

Free Trial

No card required

New users receive a one-time trial credit valid for up to 30 days.

  • Trial credit: $5 usage credit for up to 30 days

Enterprise Pricing

Custom Enterprise plans with tailored limits, support, and commercial terms are available through Railway sales.

Billing Commitment

Plan fees count toward monthly resource usage; additional usage is billed separately.

Infrastructure & Availability

Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.

Railway currently offers four active Railway Metal deployment regions in California, Virginia, Amsterdam, and Singapore. These are the locations where application workloads run. Railway's separate edge-networking layer can terminate and route traffic elsewhere and is not included in this deployment-region inventory.

Execution

  • Single Region
  • Multi Region

Deployment scope

  • Regional

Geographic availability

North America
2
Europe
1
Asia Pacific
1

Infrastructure providers

  • Railway Metal

Available regions

LocationAreaRegion ID
US West, California Active Railway Metal deployment region.North Americaus-west2
US East, Virginia Active Railway Metal deployment region.North Americaus-east4-eqdc4a
Europe West, Amsterdam Active Railway Metal deployment region.Europeeurope-west4-drams3a
Southeast Asia, Singapore Active Railway Metal deployment region.Asia Pacificasia-southeast1-eqsg3a

Availability reviewed · Availability source

Resource & Execution Limits

HTTP headers

32 KB

Per request

Request duration

15 minutes

While transferring data

Idle timeout

5 minutes

Per HTTP request

Security & Compliance

Security Controls

Access Control
Workspace and project roles, access groups, and scoped tokens Railway workspaces and projects
Secrets Management
Sealed write-only variables Railway projects
Private Networking
Environment-isolated WireGuard network Railway project environments
Audit Logging
Workspace and project administrative events 48 hours Free/Hobby; 30 days Pro; 18 months Enterprise
Single Sign-On
SAML Enterprise
DDoS Protection
Managed Layer 4 mitigation Railway public networking
Web Application Firewall
Under Attack Mode Railway HTTP services

Audits & Certifications

SOC Reports
SOC 2 Type II and SOC 3 Railway managed platform

Compliance

HIPAA
Eligible use BAA add-on and paid spend threshold required; customer safeguards apply

FAQ

Does Railway support Kubernetes?
No. Railway is not a Kubernetes platform. You deploy applications as Railway services while Railway manages the underlying orchestration.
How does Railway pricing work?
Railway combines plan charges or monthly credits with metered resource usage. Railway has a $0 Free plan, a $5 Hobby monthly minimum, and a $20 Pro monthly minimum; usage beyond what the plan covers is billed separately.
Does Railway still have a free plan?
Yes. Railway currently has a $0 Free plan. New users receive a trial first, then the Free plan provides a recurring monthly usage credit for small workloads.
Does Railway require a credit card for the free plan?
No. Railway’s current Free plan path does not require a credit card. A card is needed when you move to paid usage or otherwise enable billable resources.
How much does Railway Postgres cost?
Railway Postgres does not have a separate database subscription price. It runs as a Railway service and is billed from the plan plus the CPU, memory, volume storage, and network resources the database consumes.
What databases does Railway support?
Railway supports PostgreSQL, MySQL, and MongoDB database services. Railway can deploy database services from templates or images, so operational responsibility varies by service.
Is Railway good for Docker deployments?
Yes, Docker images are a first-class Railway deployment path. Railway can deploy an image directly or build a repository into a container, while the service is then billed and operated under Railway’s normal resource model.

Explore