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

Before we get started, I hope you’ve had a great week so far and gearing up for the long weekend! Happy Easter to those that celebrate!

This week, we’ve been focused on fixing things around the product and smoothing out rough edges as we begin to get back to our desks.

Now, let’s dive in and see what we shipped this week! 🚂✨

The Railway Dashboard is where your projects and services live, and it’s often the first thing you interact with. Record user numbers mean record latency… So when it’s slow or not as fast as it should be, everything feels a bit off…

This week, we rolled out some under the hood performance upgrades to make the dashboard feel noticeably faster and more responsive. 

Opening the dashboard where your list of projects show up, opening a project, opening services, navigating between services, and dragging things around the canvas should now feel lighter and snappier.

Think of it as a turbo boost to the same dashboard you already know and love. 

Support for Migrating Larger Volumes to Metal

We’ve improved our volume migration system to better support users moving to Railway Metal.

As of this week, we’ve increased the max volume size that can be successfully migrated to Metal. This should make the migration experience smoother and reliable especially for users running stateful services. 

If you’ve previously hit volume size limits while trying to migrate, now’s a great time to try again. And if you’re still running into issues, please reach out to us on 

This is part of our ongoing effort to make Metal not just powerful, but easy to use for both stateful and stateless services no matter how large your workloads are!

When certain workspaces are firing off deployments at minutes at a time, many companies reported that it would take considerable time to clean up old deployments, or worse… they would hang around.

Engineer Jared went into the guts of our deployment systems and found a thing or five that our deployment system shouldn’t have been calling. The result: faster and more deterministic deployments.

We currently offer new users a free trial to explore the platform, which includes access to basic core features and a one-time $5 credit. Your trial can last for many months, as long as you haven’t used up all the credit. 

We’re changing this system for two reasons.

 rolling out a system where we can get a perpetual free plan for users. Nothing final yet, but it’s looking like we can offer Serverless compute, infinitely vs. the old Trial.

We want finality on how users engage with the platform and see if they naturally churn, or re-engage. By capping the time on the Trial, we can see how users “upgrade” through the funnel.

You may be wondering: “Wow, the people at Railway are nakedly telling the user base what it wants to do!”

We’re updating the trial experience starting next week. Free trials will now be limited to 30 days from the date you sign up. After 30 days, your access will end, even if you haven’t exhausted your credit.

We made an update to our Privacy page on the website

We fixed the bug concerning the incorrect removed tab count on the project list page

We fixed a bug with the pre-deploy timer on a service reseting after 60 minutes

We fixed a visual bug with the featured blog posts on the website careers page

We fixed a bug where the URL environment query params does not update when switching a project via the dropdown

We updated max memory resource validation for enterprise customers

We added improved visibility by logging a warning when deleting plan limit override without a matching customer

We fixed a bug to ensure only unique pro metal coupon exist on invoices

We removed duplicate queries to ensure better load performance in workspaces

We fixed an issue that caused some deployment removals to error out early

https://res.cloudinary.com/railway/image/upload/v1744996788/2025-04-18_dlrlbe.png

Snappier Dashboard, Large Volume Migration Support, Deployment Lifecycle Fixes

2025-04-18-dashboard-fixes-larger-volume-migration-support

Changelog #0234