Alright alright, let’s go to Caller #9 out there — caller, you’re on the show!

Hey is this the people over at the Railway Changelog? I’m a first time caller long time listener and I was just wondering … when ya gonna finish this <bleep> migration to Railway Metal? I mean <bleep>! It’s been like 3 weeks!! Can’t you see we want some new features over here?? Can you please get your <bleep> <bleep> back to <bleep> some <bleepin> new features?? 

Ohhhhkay, thank you Caller #9, we hope you find the love that you’re looking for in your life, we’re sending big hugs out to you.

But Caller #9 is also absolutely 100% correct — we do want to get this 

 over and get our bleep bleep back to bleep some bleepin’ new features as soon as possible. 

More on that soon, but meanwhile we wanted to let you know that we’re now running

 for migrating to Railway Metal including deletion of additional per-seat costs, better performance, higher reliability, and more

We wanted to remind you that now is the time to migrate stateless and 

We wanted to remind you one last time that we’re 

soon to start deleting trial projects after 30 days

And we especially wanted to remind you that 

we’re now offering $10 bounties for answering questions in Central Station

Now let’s get to the <bleepin’> features! 

GCP instances are now marked “Legacy”

This 1-line code change is highly significant, so we wanted to call it out to reiterate the points above. 

The Great Metal Migration is more than 90% complete and we’ve officially started the process of labeling GCP instances as 

To read more about why we’re exiting the cloud and building our own, check out Jake’s post 

Ok! With that out of the way let’s go onward!

Less Stressful Data Migrations Between Regions

There’s a new flow when copying your volumes from region to region

Have you tried in the past to move stateful workloads (e.g. 

It wasn’t the most … uh … intuitive procedure. 

Well, more specifically, it was a leap of blind faith since we provided basically no UI reassurance that your volume was, in fact, being migrated. 

Well leap blindly no longer my friends, as this week we crafted a nice bit of interface around copying volumes region to region. 

You should now notice that the Volume settings will let you know all about the progress of your migration and that your BPM generally stays pretty level throughout the process, which is a huge improvement. 

Just remember, volumes follow the service they belong to, so if you’d like to move a volume, just change the region in the service settings.

That’s right folks! We’ve been teasing it for a while, but it looks like all systems are good to go for next week to release the new Free plan.

We mentioned it in the preamble (plus several times over the past few weeks) but this is made possible by the fact that we’re now 

 and running most everything on Railway Metal.

So stay tuned for that next week, because we’ll ask for your help telling your friends that might be new to Railway. 

We improved the activity feed descriptions of events across services and volumes

We smoothed over the turnaway experience when trying to deploy on an expired trial plan

We nerfed the Limited Trial a bit by eliminating Functions as an option

We fixed some overflow issues with long source image names

https://res.cloudinary.com/railway/image/upload/v1747438000/2025-05-16_ouvogu.png

Legacy Instances, Less Stressful Data Migrations, Free Plan Incoming

Changelog #0238