Happy Grok 3 launch to all the AI Aficionados!

This week’s update is brief as the team has been all hands on deck at the station, syncing, planning, heads down prepping for the second edition of Railway Launch Week. 

We’ve been drinking loads of coffee, eating feedback for lunch, and slapping our keyboards until perfection comes alive. 

Now let’s get into this week’s Changelog. 🚂✨

Tick! Tock! It’s time to start counting down to the next edition of 

Railway Launch Week 02 will commence on March 3rd through March 7th. Get ready for five feature-packed days where we unveil what we've been crafting to transform your app deployment and scaling experience into something truly magical!

Mark your calendars and join us for a glorious deployment week and special event of the year. The countdown has begun, we can't wait to show you what we've built!

A lot of you really like to sync your environments. We now have customers who merge in 300+ diffs of changes- and merge like you are on the highway!

Because of the traffic that you all are causing, we spent some time with our largest customers on a call co-creating some upgrades to the Sync Environment feature.

Now, if you are focused within a service group, and you press “Sync” we will only apply the changes from services within that group.

To illustrate this we have a video. Notice that at the root view, all changes were applied. Once we were in the group scope, only services in that scope had changes staged. You can use this mechanism to selectively apply your staged changes.

There is one original sin on the platform. …and that is the Pro plan.

When we implemented it’s earlier version, the Team plan. We originally thought that users on Railway would closely follow the GitHub model. We have “actors” and then we have “organizations”. We’d thought that users should have an independent upgrade path than organizations.

Users expressed confusion that when they would upgrade their account to Pro- they wouldn’t see any of their projects (because we made a new subscription object). We patched around this experience for a while, but our inbox is still filled with confused new users. We’re sorry.

Engineer Paulo is fixing 4 years of mistakes in two months, and you are seeing the first few steps to fix this. If you see him on the street, thank him. 

Now on Railway, all new accounts will have a “Personal” workspace, that can be upgraded all the way to Pro.

Or… you can make a new one if you want to keep your business separate from your personal one. 

Or… if you signed up with a company email like: accounts@, that can be the root of your Railway experience. 

You won’t notice anything, but you no longer need to make a new “object”.  The point is- there should be no more User / Team / Workspace confusion.

As mentioned, fixing four years of data debt will take some time. We’re going to take our time rolling this out but it means we will be moving some settings around, if you need help finding out on how to do something on the platform. 

We fixed a bug that made the Usage limits button a bit responsive when clicked.

We fixed a bug on the GraphiQL Explorer that made the page crash when clicking on the explorer icon.

We fixed a bug that affected webhook tabs on mobile devices. 

We fixed a visual bug that affected a service start command view within a template canvas.

https://res.cloudinary.com/railway/image/upload/v1740177993/docs/quick-start/2025-02-212_kk2az9.png

Railway Launch Week March 03-07, Sync Environment Upgrades, Workspaces

Changelog #0226