The self-hosted Railway alternative

Levelrail vs Railway: one binary, about 200 MB idle, Apache 2.0.

Levelrail control plane memory, idle, measured

~200 MB

Install
1 binaryplus one agent per extra node
License
Apache 2.0one edition, no license key
Ahead on
7 of 38capabilities, per Railway's docs

The memory figure is one idle measurement of the Levelrail control plane (method). As of 2026-11-18.

01

What you gain over Railway

7 capabilities where Levelrail is a plain yes and Railway's own docs say partly or no. Full wording and sources are in the table.

Capabilities where Levelrail is ahead of Railway
Capability Levelrail Railway
Crashloop diagnosis with last log lines Crashloop detection surfaces the last log lines Partly Default On Failure restart policy restarts up to 10 times
One-click rollback with pinned images Prior images pinned so cleanup cannot remove them Partly Dashboard rollback to prior image
Readiness-gated deploys (zero-downtime on one node) Cutover only after the readiness probe passes Partly Healthcheck gates cutover
Request firewall, rate limits, bot protection Ordered rules, IP bans, bot handling, challenges and rate limits Partly Under Attack Mode plus Edge rules
IAM, audit log and 2FA in the free edition Allow/Deny IAM policies, passkeys and TOTP, and an audit log Partly Audit logs: 48 hours on Free, Trial and Hobby, 30 days on Pro
Two-person deploy approvals A different person with the deploy ability must approve Partly Deployment Approvals hold commits from users without a linked Railway account
Deploy freezes and policies Cron-defined freeze windows per app with an audited override reason Partly Wait for CI holds deploys until GitHub Actions check suites finish
02

All 38 capabilities

Statuses for Railway are what its own documentation states; "Not stated" means its docs do not say. For Levelrail, "Active" means the feature ships today, with beta and stable tags from the feature status page and the exact scope in each note.

Levelrail
YesActive
Railway
YesPartlyNo

A rule marks the 7 rows where Levelrail is ahead.

Levelrail compared with Railway, by capability
Capability Levelrail Railway
Architecture 3
No SSH: agents dial out Yesbeta Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out Not applicable
Level-triggered reconciler with status reasons Yes Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons Not applicable
Single control plane binary Yes One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary Not applicable
Observability 3
Metrics and log search built in Yes Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in Yes Dashboard CPU, memory, network, disk metrics; log search Source for Railway, Metrics and log search built in
Crashloop diagnosis with last log lines (Levelrail ahead) Yes Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines Partly Default On Failure restart policy restarts up to 10 times; Free and Trial capped at 10 and cannot use Always; paid plans have no restart limit. No automatic diagnosis Source for Railway, Crashloop diagnosis with last log lines
Public status page Yesstable Opt-in public page with components, 90 day uptime bars, incidents, maintenance and RSS Source for Levelrail, Public status page Not stated in their docs
Deploys 10
One-click rollback with pinned images (Levelrail ahead) Yesstable Prior images pinned so cleanup cannot remove them. A 5xx spike or crashloop after cutover rolls back automatically (live-tested); the latency signal is beta Source for Levelrail, One-click rollback with pinned images Partly Dashboard rollback to prior image; images kept 24 to 360 hours Source for Railway, One-click rollback with pinned images
Readiness-gated deploys (zero-downtime on one node) (Levelrail ahead) Yes Cutover only after the readiness probe passes. Live-tested on one node; multi-node is beta Source for Levelrail, Readiness-gated deploys (zero-downtime on one node) Partly Healthcheck gates cutover; volume services see brief downtime Source for Railway, Readiness-gated deploys (zero-downtime on one node)
Preview environments per pull request Yesstable Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request Yes Environments per PR Source for Railway, Preview environments per pull request
Docker Compose apps Active Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps Partly Imports Compose services; docker-compose.yml not run directly Source for Railway, Docker Compose apps
Git push deploys from GitHub, GitLab, Bitbucket Active GitHub, GitLab, Bitbucket and Gitea documented; GitLab and Bitbucket previews are beta (synthetic webhooks). A git push remote on your own server (no provider needed) is beta Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket Partly Autodeploy from GitHub only; GitLab and Bitbucket not documented Source for Railway, Git push deploys from GitHub, GitLab, Bitbucket
Builds from source without a Dockerfile Active Railpack detects Node, Python, Go and more. Ruby and PHP are accepted but only plan generation is verified, no live build; Rust, Deno and Elixir are rejected Source for Levelrail, Builds from source without a Dockerfile Yes Railpack detects stack without Dockerfile; Dockerfile takes priority Source for Railway, Builds from source without a Dockerfile
Scheduled jobs Yes Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs Yes Cron schedule per service; runs at least 5 minutes apart, UTC Source for Railway, Scheduled jobs
Deploy freezes and policies (Levelrail ahead) Yesstable Cron-defined freeze windows per app with an audited override reason; also gate image auto-update and scheduled deploys Source for Levelrail, Deploy freezes and policies Partly Wait for CI holds deploys until GitHub Actions check suites finish; Enterprise guardrails restrict deploy sources; no freeze windows documented Source for Railway, Deploy freezes and policies
CI deploys with no stored secret Active GitHub Actions only: a GitHub OIDC token is exchanged for a 15 minute token scoped to one app. Other CI uses an API token Source for Levelrail, CI deploys with no stored secret No No OIDC or keyless CI deploy documented; deploys use project or account tokens stored as CI secrets Source for Railway, CI deploys with no stored secret
Static site hosting Yes Static HTML from git served by the embedded ingress with TLS; drag-and-drop folder or zip deploy Source for Levelrail, Static site hosting Yes Zero-config static site deploys from GitHub with custom domains and automatic SSL Source for Railway, Static site hosting
Data 3
Managed databases with scheduled backups Active Many engines, scheduled S3 backups. Postgres point-in-time restore is tested live; MySQL, MariaDB and MongoDB are beta Source for Levelrail, Managed databases with scheduled backups Partly Scheduled volume and Postgres PITR backups; S3 export needs own job Source for Railway, Managed databases with scheduled backups
Point-in-time database restore Active Postgres stable with an S3 compatible bucket; MySQL and MariaDB beta; MongoDB has no point-in-time restore Source for Levelrail, Point-in-time database restore Not stated in their docs
Encrypted secrets for env vars Yes Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars Yes Variables encrypted at rest; sealed values write-only Source for Railway, Encrypted secrets for env vars
Networking 4
Private networking between apps or nodes Active Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes Yes WireGuard private DNS per environment, service.railway.internal Source for Railway, Private networking between apps or nodes
Load balancing across replicas Active Apps with more than one replica are round-robin balanced by default, with failed-replica skip and retry. The configurable balancer (health checks, sticky sessions, weights, drain) is experimental, behind a flag, verified on one machine only. HTTP only Source for Levelrail, Load balancing across replicas Yes Traffic spread across replicas and regions; no sticky sessions Source for Railway, Load balancing across replicas
Request firewall, rate limits, bot protection (Levelrail ahead) Yes Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection Partly Under Attack Mode plus Edge rules (block, allow, challenge, redirect, cache override); rate limiting not documented Source for Railway, Request firewall, rate limits, bot protection
Automatic TLS certificates Active Self-signed by default; public ACME (HTTP-01) has one recorded run on a live VPS. Renewal near expiry and DNS-01 wildcards are not exercised live; CAs needing EAB are unsupported Source for Levelrail, Automatic TLS certificates Yes Let's Encrypt certificates for custom domains, renewed automatically Source for Railway, Automatic TLS certificates
Platform 11
Multi-node Activebeta Join, cordon and drain with real container relocation verified across two local Docker daemons; WireGuard mesh and cross-host transport still unverified. Resource-aware placement is beta Source for Levelrail, Multi-node Not applicable
One-click service templates Yesbeta 592 catalog entries, 583 active; 346 proven on a real engine, 246 previews without that pass yet Source for Levelrail, One-click service templates Yes Template marketplace with one-click deploys Source for Railway, One-click service templates
Autoscaling Active Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling No Vertical scaling is automatic per container, but replica count stays where you set it; horizontal autoscaling means building your own with the API, railway scale CLI or cron Source for Railway, Autoscaling
Sleep idle apps, wake on request Yesstable Opt in per app; stops after 5 minutes to 7 days idle and wakes on the next request. Verified live against a real Docker daemon and the real ingress Source for Levelrail, Sleep idle apps, wake on request Yes Serverless setting per service; sleeps 5 to 10 minutes after last outbound traffic, wakes on inbound request, first request may be slow or return 502 Source for Railway, Sleep idle apps, wake on request
CLI and HTTP API Yes CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API Yes Public GraphQL API is the same API that powers the dashboard; CLI and MCP server also available Source for Railway, CLI and HTTP API
Deploy and alert notifications Active Webhook and SMTP email have live e2e; 15 vendor kinds (Slack, Discord, PagerDuty and more) are beta, tested against local fakes Source for Levelrail, Deploy and alert notifications Yes Slack and Discord webhooks; email via account notifications Source for Railway, Deploy and alert notifications
MCP / AI assistant integration Yesbeta MCP server (beta) with over 240 tools in toolsets an agent enables on demand (256 at last count, 21 in the default session); in-app chat is behind a flag Source for Levelrail, MCP / AI assistant integration Yes Official hosted MCP server at mcp.railway.com Source for Railway, MCP / AI assistant integration
Runs on servers you own Yes Runs on Linux servers you provide Source for Levelrail, Runs on servers you own Not applicable
Open source license Yes Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license Not stated in their docs
Declarative apply of the whole platform Activebeta YAML export, plan and apply from CLI, dashboard, MCP or CI, plus a Terraform and OpenTofu provider. Experimental, behind a flag Source for Levelrail, Declarative apply of the whole platform Yes Infrastructure as Code in .railway/railway.ts (GA; Python and Go in beta) defines services, databases, volumes, buckets, domains, variables, replicas; railway config plan and apply; railway.json/toml Config as Code is deprecated, legacy files read until 2026-12-01 Source for Railway, Declarative apply of the whole platform
Functions and one-off jobs Active Node, Python or Go handlers that sleep when idle and wake on the first request; scheduled and background calls with retries Source for Levelrail, Functions and one-off jobs Yes Cron services plus Functions (single TypeScript file on Bun, with optional cron schedule) Source for Railway, Functions and one-off jobs
Security 4
IAM, audit log and 2FA in the free edition (Levelrail ahead) Yesstable Allow/Deny IAM policies (stable, live e2e), passkeys and TOTP, and an audit log with a verifiable hash chain, CSV export and forwarding, all in the one edition Source for Levelrail, IAM, audit log and 2FA in the free edition Partly Audit logs: 48 hours on Free, Trial and Hobby, 30 days on Pro, 18 months on Enterprise; Environment RBAC and SAML SSO are Enterprise or committed-spend only Source for Railway, IAM, audit log and 2FA in the free edition
SAML or SCIM single sign-on Activebeta OIDC sign-in (17 named providers plus generic OpenID Connect) is on by default once configured. SAML and SCIM are beta, behind a toggle and off by default; SAML ran against Keycloak and SimpleSAMLphp in a local lab, not Okta or Entra Source for Levelrail, SAML or SCIM single sign-on Partly SAML SSO is an Enterprise feature; SCIM not mentioned Source for Railway, SAML or SCIM single sign-on
Audit log of every action Yes Every mutating request recorded; verifiable hash chain, CSV or NDJSON export, retention, streaming to a webhook or S3 bucket Source for Levelrail, Audit log of every action Yes Retention 48 hours on Free, Trial and Hobby, 30 days on Pro, 18 months on Enterprise; viewable by workspace admins Source for Railway, Audit log of every action
Two-person deploy approvals (Levelrail ahead) Yesstable A different person with the deploy ability must approve; the requester cannot approve their own. Approval also works from Slack or Discord Source for Levelrail, Two-person deploy approvals Partly Deployment Approvals hold commits from users without a linked Railway account; duplicated environments need staged-change review; Environment RBAC and approved-sources guardrail are Enterprise or committed-spend; no two-person production approval documented Source for Railway, Two-person deploy approvals

All ten projects are on the full matrix. Product names and logos belong to their owners and are used for identification only.

03

Move over from Railway

There is no Railway importer. Deploy from the same git repos and recreate env vars and domains.

docker pull ghcr.io/glincker/levelrail:latest
04

Questions about Levelrail and Railway

Is Levelrail a good alternative to Railway?

Yes. Levelrail does what Railway does with a lighter footprint and more built in. Runs on your Linux servers, so pricing is your own server cost. Secrets, metrics and logs stay on your nodes unless you configure an export. Self-hosted software only; there is no managed cloud version. A read-only importer and a dry-run mode let you move without touching Railway.

Can I move from Railway to Levelrail?

There is no Railway importer. Deploy from the same git repos and recreate env vars and domains.

Is Levelrail ready to replace Railway in production?

Run both side by side, move one domain at a time and keep Railway as a fallback until you are happy. The feature status page lists the maturity of every area.

05

Keep exploring