Why use private networking?
A private network lets your servers talk to each other (and to your devices) over an encrypted WireGuard mesh, without exposing those services to the public internet. Use it for databases, internal APIs, dashboards, Home Assistant, Pi-hole, NAS shares, and anything else that should not be reachable from outside.
One network per customer
Every account is assigned a unique private subnet, typically 10.<customer_id>.0.0/24. The same network spans all of our datacenters — a server in Montreal and one in Halifax can reach each other privately at full speed.
Joining a VPS to the network
- Open the VPS service page and select the Network tab.
- Click Join Private Network.
- The panel assigns the next available
10.x.0.Naddress and pushes the WireGuard config to the host. - Within seconds the VPS can reach other members of your private network.
Public VPS vs Private Homelab VPS
| Service | Public IP | Private network |
|---|---|---|
| VPS (public) | Yes | Optional, free to join |
| Private Homelab VPS | No | Required — only way in |
| Game Server | Yes | Not supported |
| Web Hosting | Yes | Not supported |
Worked example
Customer network: 10.42.0.0/24
Public VPS (web) 10.42.0.1 + 203.0.113.10 public
Private VPS (database) 10.42.0.2 no public IP
Private VPS (Home Assist) 10.42.0.3 no public IP
Your laptop 10.42.0.100 WireGuard peer
The web server connects to the database over 10.42.0.2:3306.
You reach Home Assistant from anywhere via 10.42.0.3:8123 over WireGuard.
The internet cannot reach the database or Home Assistant at all.Leaving the network
From the VPS’s Network tab click Leave. The peer is removed and the IP is returned to the pool. Private Homelab VPSes cannot leave (they have no other way in).