--- title: "One-click CDN, Railway x Stripe Projects, HA Postgres" date: 2026-03-27 number: 0283 url: https://railway.com/changelog/2026-03-27-cdn --- # One-click CDN, Railway x Stripe Projects, HA Postgres Your users in Tokyo shouldn't wait for bytes to travel from us-west. Starting this week, they don't have to. We're shipping a built-in CDN you can enable in one click, a partnership with Stripe that lets agents provision Railway in one command, and a one-click path to high-availability Postgres for everyone. Let's get into it! 🚄 ## One-click CDN [Image: Enable CDN caching in one click for your custom domains] Railway now has a built-in CDN, and it's completely free. Faster load times for your users, lower costs for you. Every static asset served from the edge instead of round-tripping to your origin. Most CDN setups involve DNS changes, cache configuration, and a separate bill. Railway's CDN is one click. To get started, hit the ⚡ icon on any custom domain in your service's network settings, and your assets propagate worldwide in about one second. No DNS changes, no external provider, no configuration required. Caching follows sensible defaults that work for the vast majority of applications: - HTML is always treated as dynamic and fetched from origin, so your server-rendered pages stay fresh. - `Cache-Control` headers are always respected, giving you full control when you need it. - Static content types (images, fonts, JavaScript, CSS, audio, video, and more) get a default 2-hour TTL when no cache headers are present. - Responses with `Set-Cookie` are never cached. In practice, this means your JavaScript bundles, stylesheets, images, and fonts are cached at the edge automatically. Your origin handles the dynamic requests it's supposed to. Your users get fast page loads regardless of where they are, and you stop paying for bandwidth on assets that don't need to hit your server. Under the hood, we partnered with [Fastly](https://www.fastly.com/) to power the CDN across their network of 100+ points of presence on six continents. Fastly's edge network is trusted by some of the largest sites on the internet, and it's now available to every Railway user at no extra cost. We've got more planned, including configurable default TTLs, manual cache purging, and cache analytics. Try it out, check the network tab to see how fast your static assets load and share your feedback on [Central Station](https://station.railway.com/new?type=feedback) ## Railway x Stripe Projects [Image: provision Railway resources from the Stripe CLI] We've partnered with [Stripe](https://stripe.com/) and built on their Agentic Provisioning Protocol spec to let developers (and their agents) go from nothing to deployed without leaving the terminal. ```bash $ stripe projects link railway ✓ Successfully linked Railway account $ stripe projects add railway/postgres ✓ Provisioned PostgreSQL — credentials synced to .env $ stripe projects add railway/hosting --config '{"image": "nginx:latest"}' ✓ Deployed nginx:latest on Railway ``` Install the `projects` plugin in the Stripe CLI and you get access to their provider catalog, where you can provision Railway resources on demand. We join PostHog, Supabase, Vercel, and others in the developer preview as Stripe grows the APP ecosystem. This fills a gap that MCP doesn't cover. MCP is great for tool-calling when you already have a Railway account, but it has no concept of account creation, billing, or resource lifecycle management. Stripe's APP protocol handles all of that in a single flow. `stripe projects link railway` creates your account, sets up a trial with $5 in credits, and hands back credentials in one round-trip. Add a resource, and we provision it and sync the connection string to your `.env`. No dashboard. No signup form. No billing page. The resource you asked for, ready to go. The starting catalog includes PostgreSQL, MongoDB, Redis, Object Storage (Buckets), and compute services for Docker images or GitHub repos. To get started: ```bash stripe plugin install projects stripe projects init stripe projects link railway stripe projects catalog railway ``` We wrote a longer piece on why we built this and where we're headed. [Read the full blog post](https://blog.railway.com/p/railway-stripe-app). ## High-availability Postgres [Image: Convert your Postgres database to a highly available cluster in one click] After weeks in Priority Boarding, high-availability Postgres is available to all users. A single Postgres instance means any node failure takes your database offline. With HA enabled, Railway provisions a full cluster behind the scenes: [Postgres](https://www.postgresql.org/) replicas managed by [Patroni](https://github.com/patroni/patroni), an [HAProxy](https://www.haproxy.org/) load balancer routing traffic to the current primary, and an [etcd](https://etcd.io/) cluster handling leader election. If the primary fails, the cluster promotes a replica and reroutes traffic automatically. The feature is built on the [Postgres HA template](https://railway.com/deploy/postgres-ha). 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. Enable HA on any existing Postgres database from its settings, and share your feedback in the [Central Station thread](https://station.railway.com/feedback/high-availability-postgre-sql-d02c9651).