Private Networking
Private networking enables secure communication between services within your Railway project without exposing traffic to the public internet. Services communicate over encrypted Wireguard tunnels using internal DNS.
Key features
- Zero Configuration - Services automatically discover each other via internal DNS
- Encrypted Traffic - All inter-service communication uses Wireguard encryption
- No Public Exposure - Traffic stays within Railway's private network
- Environment Isolation - Each environment has its own isolated network
Learn more
| Topic | Description |
|---|---|
| How It Works | Technical deep-dive into Railway's private networking architecture, including Wireguard tunnels, internal DNS, and IPv6 addressing. |
| Library Configuration | Configure your application libraries and frameworks to work with private networking. |
Quick start
To connect services privately:
- Deploy multiple services to the same project environment
- Reference other services using their internal DNS name:
SERVICE_NAME.railway.internal - No port exposure or configuration required
For example, if you have a service named api, other services can reach it at:
See How It Works for complete details on DNS resolution and network architecture.