We are back from the Great Lakes, but most of us are still recovering from the long trips and all the socializing (seriously, we peaked on fun). The Q4 retreat? An absolute blast! Now, it’s time to switch gears and jump into ship mode to close out the year strong.

So, what did we accomplish this week? Let’s dive in!

Transition music, camera pan to Jake Cooper, founder of Railway.

It’s been great to see 750,000+ unique developers deploy their code directly on Railway. We’ve witnessed side-projects blossom into the next big thing while simultaneously supporting ever larger companies trusting us as their end to end compute lifecycle provider.

During the first phase of this journey, our workloads are primarily driven by hosts and services hosted on GCP. 

We’ve been alluding to moving workloads to our own self-hosted servers on what we call: Railway Metal. 

As a fast growing hyperscaler- it’s very difficult to build a hyperscaler within an existing hyperscaler. As such, we embarked on a journey over the last two years. We’ve been hard at work delivering a new set of systems that’s 

 handling internet scale traffic processing billions of requests monthly. 

After shipping core pieces to our platform that enabled a major step function in performance- it’s time to start our very gradual move to Railway Metal. 

As we speak, thousands of customers are already taking advantage of Railway Metal with the following benefits:

However, just because something has immediate benefit doesn’t mean we are in a rush to get your workloads to experience them. Our 

transition to Railway Metal will span from 2024 well into 2025.

 The Railway team studied migrations and deprecations from the past from other companies as well as previous migrations that we’ve conducted. 

We are prioritizing stability over anything else. 

Last month, we allowed Priority Boarding members to test stateless workloads on our new datacenter location in US-West. 

We shortly moved over existing Trial workloads to deploy to Metal by default

 with no intervention required on the developer’s behalf.

Now, we are gradually moving over stateless Hobby workloads to our new boxes with no action is required.

Our main goal is to build production confidence on Railway Metal while we aim to get to feature parity of our GCP hosts.

We're taking a phased approach to rolling out Railway Metal. Pro workspaces and Businesses currently on GCP are in the final phase of this transition, 

 a seamless migration when the time comes. 

We know there will be a lot of questions and we stand at the ready to answer them in 

our Forum, our Discord, and your Slack Connect channel

. We also plan many more communications in our docs and our blog- we are committed to keeping you informed every step of the way.

Update Preferred Region via Command Palette

The option to update preferred deployment region now exists in the command palette

Railway users on the Pro plan can now easily update their 

.  It’s a quick and seamless way to optimize your app's deployment location with just a few clicks! 🚀🌍

The command palette in Railway is a powerful modal that lets you perform actions quickly by pressing 

 on Windows). It serves as a shortcut for tasks like managing services, handling deployments, and now, updating regions—without needing to navigate away from the dashboard. It's designed to streamline your workflow and boost efficiency!

We are pushing new guides to the Railway docs weekly!

We just rolled out more guides to help our awesome developer community! 🔥

Got a burning topic we haven’t covered yet? Don’t hesitate to open a 

 and let us know what you’d love to see next! 🚀

Help station Inbox page showing replies to discussions a user is subscribed to

Now, you can stay up-to-date with discussions you’re subscribed to and never miss a reply or important date.

We fixed a bug relating to the Trial usage cron. 💫

https://res.cloudinary.com/railway/image/upload/v1716596069/2024-0524_sugzfn.png

Hobby on Railway Metal, Support Inbox, More Guides

Changelog #0208