The Railway team usually conducts business all around the world, remotely. This week was a little different with the team meeting physically for a retreat. With the time spent together, we dedicated time to plan the future of the product for the coming year.

Which means we don't have much to announce in terms of updates to the current product.

However, we know that developers need Railway to be flexible to their needs, scalable, and most of all- easy to use. 

We know that if we want to achieve our goal of radically simplifying software development- we need to have a product that makes it dead simple to build and deploy apps of all types. From monoliths to multi-service apps, our vision for the Railway to come supports any way how you choose to develop software.

There is much more to share in the coming days on how we are changing the platform for the better.

Keep in mind, this is far from final, and we want as much feedback as possible. Please join us on our Discord to share what you think!

Changed the email vendor, this fixed issues with unsubscribing and email preferences

Some removed deploys no longer get marked as "crashed"

Fixed crash copy to make it easier to understand.

Redeploy latest deploy if last was crashed

https://user-images.githubusercontent.com/3044853/142716209-e5ffbe6b-3775-43d1-b146-84d650e5596f.png

Railway Goes to the Beach and Future Plans

Changelog #0056