Railway
All Updates

Changelog #0231

Follow along with updates and improvements made to Railway

Follow us on Twitter

Mar 28, 2025

🎉 Welcome to this week’s edition of the Railway Changelog! 🚀

Before we get started, we hope your month has been nothing short of magical as we begin wrapping up the first quarter of the year.

record scratch

There is no finer right a Railway passenger can exercise than voting!

We’re about to enter Q2 planning! Influence the product! Vote on our roadmap now!

https://station.railway.com/roadmap

music resumes

Now, let’s hop aboard and see what we shipped this week! 🚂✨

Preferred Deployment Region

                     Preferred Deployment Region set to EU West (Amsterdam, Netherlands) in a workspace

Preferred Deployment Region set to EU West (Amsterdam, Netherlands) in a workspace

You now have the keys to lock in your preferred deployment region for new services in your workspace.

Just head to your workspace settings, choose a region, and click “Update Region.” From then on, every new service you deploy in that workspace will default to your selected region.

By setting a default region for your workspace, you no longer need to manually update regions to your preferred region each time you spin up a new service. Set it once and you’re good to go!

Metal Feature Parity + Migration Timeline

People who have been closely following developments of Railway Metal (to get that sweet performance + pricing) have been waiting with bated breath for a feature or two.

We’re pleased to announce: no blockers remain.

For all services, this week we shipped:

  • Static Outbound IPs
  • For stateful services, services with a volume, we shipped:

  • Migrations within Metal Regions
  • Migrations for Pro (behind a feature flag)
  • Backups
  • Metrics
  • The last step is to migrate people over.

    Over the last month, we have been migrating Hobby workloads to Metal. By May 2nd, we will begin to “force” migrate Pro workloads. You can see our timeline on our cutover here.

    We strongly urge businesses on the platform to reach out to Railway if you’d like the Railway team to oversee your migration: open a Private Thread with the team.

    Ruby & Rust Support in Railpack

                                                             Railpack deploying a Rocket app

    Railpack deploying a Rocket app

    This week, we’re back with another big round of updates and improvements to Railpack!

    We’re stoked to announce that Railpack now supports Ruby apps with zero config. If you’re a Ruby on Rails developer, your app will just work out of the box. No extra setup needed.

    And that’s not all. Railpack now supports Rust apps too! Whether you’re building with Rocket or Axum or anything rusty, we’ve got you covered.

    Fixes & Improvements

  • Projects scheduled for deletion are now hidden from the dashboard
  • We fixed decrypting of sealed shared variables
  • We now stage a runtime change to v2 if a metal region is selected for users that are on legacy runtime
  • We fixed a bug with upgrading from pricing page when logged in
  • We now lock volumes when restoring a backup
  • We added plan name to workspace switcher in the settings page
  • We fixed a bug that prevented the configured target port from being used in TCP proxy routes
  • We now redirect /new/team to new/workspace
  • We fixed a bug with creating PR Env with Copy Volume Data
  • We fixed railway.com sitemaps
  • We fixed a bug that caused Costs by Resource and Costs by Service not to add up correctly
  • P.S. We've started seeing some MCP servers pop up in the wild. Do you have one? Share it with us, we'd love to try it out!