You’ve just surpassed 1M daily active users and investors are showing up at your doorstep with handwritten notes, piles of cash, and banh mi sandwiches.

They know you switched over to Railway and now that you’ve hit 1M DAU, they want you back.

But it’s too late for sandwiches and it’s too late for second chances. 

Your business is growing on Railway and there’s no looking back. 

What’s this? Another notification. It’s a new Railway changelog. 

“It’s Friday and you know what that means…”

Nice. You kick off your shoes and settle in to read about some new features.

Pro users now have access to private threads! 

While the company is undergoing a crisis of naming things … 

(What do we call our community page now?)

 Ray found it fit to add a super nifty new feature. 

Imagine you have a feature request that depends on you disclosing private information about your existing deployment. Or imagine you don’t wanna announce to the world that you spend $250,000 on AWS. 

We plan to roll this out to a variety of channels so that we can use these threads, aggregate the questions, and with your permission, make them public for common questions or make guides.

Private threads are now available to Pro users through the help menu

Now available — add a Slack channel to chat with Railway

We have a new way to connect with the Railway team! 

The chants of “Business! Business! Business!” have resumed from the revenue team and they grow ever louder. We have found that the more we talk to you, the user, the more you are happy. 

Kidding aside, we have had a Discord integration for some time on the platform and it was long past due time to add a Slack integration. We continue to offer pagers and 

, but for certain teams who cross a certain adoption level, you will now see this option within the Team Settings page.

Make sure that your email on Railway matches your company email as we will fire off invites to that attached email.

Keep in mind, however, that these channels are offered with no SLA on response time, We advise that all general support is done via Private Thread and Email.

There are a lot of under the hood improvements that we also put in place so the team can intervene at the right times. 

We should probably write a blogpost about this…

, we’ve been hard at work improving the template creation flow — and today we wanted to give you a little sneak peak of where we’re headed.

Internally we’ve introduced a new Template Composer to make it even easier to create new templates from one or more services and/or repos. 

The template composer will look a lot like the regular application canvas:

The new template composer is similar to a blank canvas

From this state, it will be possible to add GitHub repos or Docker images or Volumes — as many services as you like. 

In this example let’s try adding a popular Docker image for a Jupyter Notebook. 

…notice how we can stack primitives up here as much as we want? How cool is that?

As we work on getting the template composer right, we hope that it will lead to substantially deeper and more complex templates. 

The feature isn’t available just yet for use, but will be soon. 

give us your feedback on how we can improve the template creation feature.

We’re going to keep reminding you until the plugin deprecation date that 

We are deleting all legacy database plugins on 

, so please make sure to migrate before then. 

join the discussions in the Community Forum

We made some small improvements to modals through the application

We fixed a couple of small issues with the preferences pane

https://res.cloudinary.com/railway/image/upload/v1708134463/threads_brdumu.png

Private Threads, Slack Integration, Template Composer Sneak Peek

Changelog #0173