This week we’re over the moon to bring Private Networking to Priority Boarding users.
That’s right! Starting today it’s possible to connect Railway services without exposing them to the internet.
Let’s jump in and see how it works.
Private Networking
Private Networking is now available in service settingsPrivate Networking has been one of the most requested features on Railway for some time.
Starting today, for Priority Boarding users, you’ll be able to do all your inter-service communication internally, without going through the Internet.
Setting it up is a breeze — just go to any of your service settings, click Enable private networking, and you should see your private endpoints ready to use after your next deployment!
Note that Private Networking is currently only supporting Services, not Plugins.
Stay tuned for more info on that.
Example playground with 4 Railway services talking to each otherFor more information and to get started, be sure to read the docs. Since this feature is in Priority Boarding, we expect you to try to break it! Let us know on Discord if you succeed.
Changesets Take Shape
Meanwhile, Changesets are coming along nicely. We previously released PR Environments at the Project Level and Fork and Merge Environments and next up we’re working to bring a cohesive experience to versioning your infrastructure wholesale.
What does that mean? We’re currently testing different strategies to diff your variables and services and we think we’re close to some nice solutions.
Just for fun, here is a Tinder-inspired strategy that will probably not make the final product.
Failed exploration into diffing variables across environmentsBut we’re getting there! The dream of Lifecycle Management on Railway is getting closer and closer and we can’t wait to share more features with you.
Improvements and Fixes
- We fixed an issue with pagination in build logs