we merged a PR from a hot air balloon in Mexico City

 (yes, really). This week, we're back on the ground and back to shipping.

This week, we're shipping repo-aware settings that make Railway context-aware about your codebase, graduating IPv4 Private Networks from Priority Boarding to general availability, and introducing a more secure way to query your databases directly from the dashboard using the private network.

Autocomplete for paths when setting the root directory or the path of your config-as-code file

Configuring a service's settings — things like root directory or the path to your config-as-code file — used to mean manually filling in values. Or worse, switching back and forth between Railway and your code editor to find the correct paths.

Not anymore. Service settings just got a whole lot smarter.

After you connect a repository to a service, Railway now reads your repo structure and config files, surfacing the exact settings you need right when you need them. No more manually hunting through your project structure or copy-pasting paths — Railway simply knows.

This is just the start. We're already working on adding support for watch paths soon, making the configuration experience even more seamless.

Our goal is simple: make Railway smarter. Infer as much as possible from your codebase, and make it easy to tweak when necessary. This is the beginning of making Railway more context-aware about the code you're shipping.

Go ahead and try it out. If you run into any issues or have feedback, drop us a line in 

Secure Database access from the dashboard to Priority Boarding

Query databases securely using the private network

Secure database access from the dashboard

Querying databases directly from the Railway dashboard has always been convenient, but there was a catch — it went through your database's public endpoint, which meant your queries traveled over the public internet.

With Secure Database Access, Railway now routes your database queries through the 

 — Your database queries never leave Railway's private network, adding an extra layer of protection

 — No egress fees since traffic stays within the private network

 — Same familiar dashboard experience, just with a more secure connection under the hood

Under the hood, this feature is powered by our SSH feature, which you can use from the Railway CLI.

Try it out in Priority Boarding and share your feedback in 

What started in Priority Boarding is now available for everyone: 

Private networking has been available on Railway for a while, but until now it’s only supported IPv6. Services got automatically assigned an IPv6 address when deployed in private networks, which worked beautifully... until it didn't. Some applications, frameworks, or services are IPv4-first — and in some cases, IPv4-only. The result? Network-related errors and extra workarounds.

A few weeks ago, we shipped IPv4 support for newly created environments in Priority Boarding. After putting it through its paces and seeing it work smoothly, we're opening the gates.

Now, when you create a new environment, it will support using IPv6 and IPv4, your private networks will just work.

Got questions or want to share your feedback? 

We fixed an issue in the "Transfer Project" modal where the workspace list would overflow when you had access to many workspaces, making it hard to view all available options. The workspace list is now scrollable, so you can easily browse through all your workspaces when transferring a project

https://res.cloudinary.com/railway/image/upload/v1760714333/2025-10-17_dze5mj.png

Repo-aware settings, Secure DB queries, IPv4 Private Networks

Changelog #0260