4 months ago
Currently, Railway's private networking is strictly isolated to a single project. If you have services spread across Project A and Project B, they are forced to communicate via the public internet (Public URL).
A very common architectural pattern is having a centralized auth server or a shared database/API in one project (Project A), which serves multiple other independent projects (Project B, C, etc.).
Why the current public-only approach is a pain:
- Need to authenticate the traffic.
- Latency
- Costs
This would be a great change for teams managing microservices or multi-tenant architectures.
0 Threads mention this feature
1 Replies
11 hours ago
Agree, having to put unrelated services into a single project just to preserve private networking is a pain.
One solution is to use Tailscale, but it's not really idiomatic and isn't 'Railway native':
https://docs.railway.com/guides/set-up-a-tailscale-subnet-router