It's the last changelog of 2025! The Railway team is heading off on a well-deserved winter break, and we'll be back early next year with our regularly scheduled programming.

Before we sign off, we've got one more round of updates to share. This week we're unveiling a brand new landing page, leveling up the `railway dev` experience with a new TUI, giving you a production-ready 

, giving template creators visibility into how their templates are performing.

It's been an incredible year of shipping and we've come a long way together. Thank you for being part of the journey.

If you've ever tried explaining Railway to a friend or colleague, you know it can be tricky. "It's like Heroku, but..." or "It's a cloud platform that..." — none of it quite captures what makes Railway, well, 

. We wanted the new landing page to do the heavy lifting for you — whether you're sharing it with a skeptical teammate or someone's discovering us for the first time.

If you haven't visited the homepage in a while, 

. There might be a few easter eggs hiding in there. And if the new messaging clicks — tell your friends.

, it let you spin up your entire Railway environment locally with a single command. But managing multiple services meant juggling terminal windows — one for your frontend, another for your backend, a third for your worker. Tab back and forth, lose track of which is which, miss important logs.

The new TUI (Terminal User Interface) changes that. Run 

 and you get a single, unified view of everything running locally:

 — Each service gets its own tab. Your frontend, backend, worker, Redis — all in one place. Hit Tab to cycle through them, or press 1-9 to jump directly.

 — The bottom bar shows you the local URL and the pretty Railway localhost domain for the selected service, plus how many environment variables are loaded.

Previously, you'd either run each service in its own terminal (and lose track of which window was which) or pipe everything into a single stream (and struggle to tell services apart). Now you get the best of both worlds — all your services in one terminal, clearly separated and easy to navigate.

The default Postgres experience on Railway is a single node. Simple, easy to spin up, and honestly — it can take you pretty far. But depending on your requirements, a single node might not cut it. Maybe you need read replicas to handle increased load. Or you want to have automatic failover with a hot standby ready to go.

Previously, setting this up meant stitching together multiple services, configuring replication manually, and hoping you got the failover logic right. Not exactly a relaxing Friday afternoon.

 that handles all of this for you. One click, and you get a

 Patroni-based high availability PostgreSQL cluster

 with automatic failover, distributed consensus, and load balancing.

 — A distributed key-value store that handles leader election and keeps the cluster state in sync. If the primary goes down, 

 coordinates which replica gets promoted.

 — Three PostgreSQL instances managed by 

. One serves as the primary, two run as streaming replicas. Patroni handles promotion, demotion, and replication configuration automatically.

 — Your single connection endpoint. It routes writes to the current primary and distributes read queries across replicas. Your application connects to haproxy, and the routing happens transparently.

We’re using this template as an opportunity for us to collect feedback. The end goal is we want to incorporate a similar experience for Postgres on Railway with a smooth upgrade path.

This is still early, and we're iterating. Try out the template and let us know how it goes in 

View metrics for your published templates

In case you're not familiar: Railway lets you turn any project into a one-click template. Package up a multi-service app, 

 and anyone can deploy it instantly. And with the 

, you earn money when users deploy and run your templates.

But until now, you were flying blind. You published a template and... hoped it was doing well? There was no easy way to see deployment counts, usage patterns, or how much you were actually earning from a specific template.

That changes today. Template creators now have access to metrics that show exactly how their templates are performing — deployments, usage, and earnings — all in one place. You'll finally know which templates are resonating with the community and which ones might need some love.

What a year it's been. Before we head out for the break, here are the highlights of what we shipped in 2025:

 — Moved 100% of workloads to our own bare-metal infrastructure.(US West, US East, EU West ,Southeast Asia)  regions. 50% cheaper egress, 40% cheaper storage, faster performance, and no more per-seat charges on Pro.

— Write and deploy TypeScript code instantly from the canvas with sub-second deploys. No GitHub repo required. Supports cron jobs, webhooks, and volumes.

 — Next-generation builder with 38-77% smaller builds, better caching, and granular versioning. Supports Node, Python, Go, Ruby, Rust, Elixir, Deno, PHP/Laravel, and more.

 — SSH into running services via the CLI with single command execution and tmux mode.

 — Scale to zero when services aren't handling requests. Pay only for active compute time.

 — Configurable alerts for CPU, RAM, disk, and egress. HTTP metrics with latency percentiles and error rates. Per-replica metrics.

 — 2x faster logs with filtering, natural language time ranges, copy/download, and clickable tokens.

 — Passwordless authentication using Face ID, Touch ID, or hardware keys.

 — S3-compatible storage that lives alongside your services. Private by default, no egress fees, no per-operation costs.

 — AI-powered automatic detection of environment variables, frameworks, Docker Compose files, and project structure.

 — Spin up your entire Railway environment locally with a single command. New TUI with tabbed service logs and automatic Docker Compose management.

 — Connect to any SAML 2.0 identity provider (Okta, Azure AD, Google Workspace) with optional enforcement.

 — Achieved SOC 2 Type II, SOC3, and HIPAA compliance.

 — Full visibility into who did what, when, and where across your workspace.

 — Real-time dashboard notifications for build failures, deploy crashes, and usage warnings with per-project customization.

 — Configure automatic minor and patch updates for databases with customizable maintenance windows.

 — Official MCP server for AI coding agents to deploy, manage, and debug Railway projects.

 — Full IPv4 support for private networking.

 — Earn credits and cash for answering community questions and creating templates. Withdraw earnings via Stripe Connect.

 — Earn 15% commission on referral spend for the first 12 months.

 — $1/month in credits after trial for small projects and personal sites.

Thank you for building with Railway in 2025. We're incredibly grateful for this community, and we can't wait to show you what we've got for 2026.

We shipped an automated vulnerability scanner for third-party dependencies where builds will fail if we detect security vulnerabilities in your application’s dependencies

We shipped an improvement that automatically triggers a re-deployment for all services that were stopped due to subscription pause — whether from an exhausted trial, failed payment, or hard limits being reached. Previously, you'd have to manually redeploy each service after resolving the issue

https://res.cloudinary.com/railway/image/upload/v1766117034/2025-12-19_y3kasu.png

New Landing Page, railway dev TUI,  High Availability Postgres Template, Template Metrics

Changelog #0269