Railway
All Updates
CHANGELOG

Changelog #0140

Private Networking has been one of the most requested features on Railway for some time and let us tell you … it feels goooo-ooood to finally ship it for you.

We’re excited to deliver PrivNets to you for all your PrivNetting needs. We even made a little PrivNet Playground for you to check out!

Let’s jump into it.

Private Networking Generally Available

Check out the PrivNet Playground public project to see an example of Private Networking in action
Check out the PrivNet Playground public project to see an example of Private Networking in action

After launching Private Networking to Priority Boarding two weeks ago, we’re ready to launch Private Networking to general availability!

As a reminder, Private Networking allows you to connect your Railway services without exposing them to the open internet. This is useful any time you’d like to keep an internal service — well, internal.

To get started with Private Networking, we made a public Railway project called PrivNet Playground for you to check out on your own. In particular, be sure to check out the Service Settings.

The PrivNet Playground project links to an application playground, which you should also check out.

And then when you’re done with the playground, be sure to check out the docs we put together! We’re looking forward to seeing all the new use cases that this enables moving forward.

New Plans Next Week

We wanted to remind you that new plans will be introduced next week. This includes a new $5 plan as well as a new Pro plan.

We recommend you check out the blogpost introducing the new plan as well as the migration guide to answer any questions you might have.

Otherwise, we’ll be shipping out notifications next week to let you know that the new plans are available.

Improvements and Fixes

  • We fixed an issue that sometimes prevented redeploying a deployment
  • We added GitHub links to our About page so you can see what we’ve been up to
  • We fixed an issue with log filtering