 and you can have a database running in seconds. But a single instance doesn't protect you when things go wrong. No replicas, no failover, no redundancy. This week, we're shipping an experimental feature to Priority Boarding that changes that: turn your Postgres into a highly available cluster, same single click. More on that below. We're also bringing bucket management to the 

High-availability Postgres to Priority Boarding

Turn your Postgres into a highly available cluster with automatic failover

Running a single Postgres instance means any node failure takes your database offline. High-availability Postgres fixes that. With a single click, Railway turns your existing Postgres database into a full HA cluster with automatic failover and a dedicated monitoring UI.

 reverse proxy that routes traffic to the current primary, and an 

 cluster for leader election. If the primary goes down, the cluster promotes a replica and reroutes traffic automatically. No manual intervention, no downtime.

. Setting up HA Postgres typically involves configuring replicas, proxies, and consensus protocols yourself. Railway abstracts that away and gives you a dedicated UI for monitoring cluster health, replica status, and the current primary.

 production-ready. Don't upgrade a production database to an HA cluster yet. We're shipping this to Priority Boarding early so we can iterate on your feedback and harden the experience before GA.

Manage Railway Buckets without leaving your terminal

 give you S3-compatible storage right alongside your services on Railway. Now you can manage them without leaving the terminal.

 provisions a bucket and deploys it to your target environment. Pass a name and region inline, or let the CLI prompt you interactively

 shows all buckets in your current environment

 displays storage size, object count, and region for a specific bucket

 prints S3-compatible credentials (endpoint, access key, secret key, region) in a format you can pipe into an 

 to rotate credentials if they've been compromised

 removes a bucket from the environment, with confirmation and optional 2FA support

 for machine-readable output. Destructive operations like delete and credential resets support 

 for accounts with two-factor authentication enabled.

 to support bucket commands, so your coding agents can provision and manage storage on your behalf.

 for the full command reference. If you run into any issues, 

We fixed clicking log rows to open the detail panel. Single-clicking any cell in a log row now opens the attribute panel as expected

We fixed the log selection overlay on mobile. The overlay is disabled on smaller screens where there isn't enough space for it

https://res.cloudinary.com/railway/image/upload/v1773430920/2026-03-13_boijuo.png

One-click highly available Postgres, Buckets in CLI

Changelog #0281