The Railway team conducts business all around the world, remotely. This week was a 

 different with the team meeting physically for a retreat. We dedicated time to plan the future of the product for the coming year. 

It’s inspiring to see cities transform into who they are today. It requires great trust and hard work to make something of use to someone. We hope we carry this energy into building Railway. 

This week, we don’t have many features to announce. Remote work is great— but its nice to hash out the finer details that may get lost over WebRTC. The team looks forward to more homemade pasta, fist bumps, and spirited debates over whats best for our customers.

, we announced our near term roadmap. You may already be familiar with announced features like Horizontal Scaling, APIs, Multi-Region (we want it too!) and Infrastructure as Code.

However, we aren’t merely satisfied with good enough. There is much more that needs to be done to make Railway the default choice for all workloads: big and small. To become a cloud deployment platform that makes engineers radically productive. There are many milestones we need to reach.

Last retreat, we were at 15,000+ active users. Now, we have much… much more. As we head into next year, keep your eyes peeled for product updates that make developer’s lives easier. But also look out for a massive investment in support, content, and stability. This is the type of work that doesn’t neatly make it into changelogs like these, but is the dark matter that makes this all possible. All this done in service for you, the builder. 

Psst… we are hiring, more job postings incoming

Improved the error message experience for first time users of the Railway CLI

Stood up more infrastructure to meet demand, there sure are a lot of ya! (complement)

Fixed errors related to “No Stacker Found”. Our orchestrator/builder wanted to chuck your deploys into the void. Now the builder’s nihilistic tendencies have been tamed. More work expected here to come. We apologize for the disruption.

NixPacks - Fixed an issue for Node build steps for Rails apps - ty 

https://res.cloudinary.com/railway/image/upload/v1665149104/docs/Retreat_pqvjiz.png

Railway Goes to an Oasis and Future Plans

Changelog #0102