Welcome y’all to Changelog #0150 🇺🇸

Sometime around Changelog #023, we received a request for adding regions to Railway.

Now, we knew we wanted to do regions. It’s kinda a tablestakes feature right? But we wanted the regions experience to be “magical,” just like every other part of the product. You shouldn’t need to turn off boxes or anything like that — just add or remove your boxes from any region around the world and have that “just work.”

It took us a while, but like all good things, we think this has been worth the wait. Today, Regions is available in 

. You just change the region and we’ll automatically spin up the new region and cut over seamlessly.

Now let’s get into the details, shall we?

Setting up a region is as simple as setting the 

 variable. We wanted to move quickly, so we literally didn’t have time to put in a dropdown. It’s a “We’re Sorry”/”You’re Welcome” type of situation. 😅

Teams in Priority Boarding can set the above variable to the following property and have it deployed, seamlessly, in the following regions:

 Singapore, Singapore? (Guess who failed Geography 🙃)

This feature is currently limited to Pro users and above who are enrolled in Priority Boarding.

Want more regions? Want the ability to run replicas in other regions? Let us know 

It is now possible to emit structured JSON logs from your deployments! 

When you’d like to preserve multi-line logs, like stack traces

When you’d like to add custom attributes to filter by (via 

For the initial release, we’re supporting the ability to view and filter by custom attributes. Meanwhile, we’re working on more goodies like custom attribute UI columns, log levels, and more. 

Utilizing structured logs is as simple as … emitting the structured logs. Checkout the 

, or skip it and just start using your favorite logger. (We like 

Once you get the hang of it, let us know what else you’d like to see on 

One of the things that we’ve wanted on Railway for a long time is the ability to expose your service to the public internet over TCP rather than HTTP. 

With TCP Proxying, we’re introducing a new primitive that unlocks 

 of stuff. First and foremost of which is the ability to deploy databases other 

 users, it’s now possible to create a TCP proxy in the service settings and then specify the port that you’d like to proxy to. Any TCP traffic sent to the generated domain and port will be proxied to your service at the port you specify. Check out 

TCP proxies can also be added to templates on the 

Specifying a port for TCP proxy in a template

We added support for Bun 1.0 (when the Nix Archive updates from 

We overhauled the look and feel of the Support pane when selecting 

We added support for duplicating a template on 

We fixed an issue with the data tab when using Redis

 button to Cron Jobs and added a shortcut to edit the cron schedule

We improved the naming convention when creating a Private Network

We improved the look and feel of the navigation and log loading experience in the Observability tab

We added support for string values in filter tag expressions

We added fixes for changing project/environment in Observability mode

We updated Nixpacks to include Gradle 8 support and Moon support

https://res.cloudinary.com/railway/image/upload/v1694220723/regions_ct0xfk.png