Private network between your VPS
Free isolated networks between your servers.
Invisible from the internet, addressing under your control.
A real Layer 2 network
Not a routed VPC with imposed subnets. There is no DHCP server, no NAT gateway and no cloud-init hook: the segment is yours end to end, any protocol, any addressing, and nothing changes unless you change it.
Free of charge, and private traffic is never metered.
How it appears in your server
Each attached server gets a second network interface with its own hardware address. Traffic between members stays inside the datacenter and never touches the public network.
You set a static IP on it, same subnet on every member, and that is all there is to it.
What it is for
Anything that should talk to your servers, and nothing else.
Databases off the public network
Your app talks to PostgreSQL or MySQL over the private segment. No public exposure, no firewall gymnastics.
Add a second server and take your database off the internet.
Clusters and replication
k3s, k0s, database replication, Redis: cluster chatter stays private and off your public bandwidth.
Build the cluster you kept postponing.
Internal-only services
Monitoring, queues, admin panels: reachable from your other servers, invisible from outside.
Give your internal tools a network of their own.
HA pairs with keepalived
True Layer 2 means gratuitous ARP and failover work. Run keepalived in real-MAC mode and float an IP between servers.
Set up the failover a routed VPC cannot do.
Up and running in four steps
Create a network from your panel
Pick a name and a location. The network exists immediately, free of charge.
Attach your servers
Private networks are attached after a server is deployed and running, not during the order. Attaching takes a few seconds and does not restart the server. If the new interface does not show up right away, a reboot brings it up. If you do not see the private networks option in your panel yet, open a ticket and we set it up for you.
Set a static IP inside each server
No DHCP, no gateway: pick your range and use the same subnet on every member. Reinstalling an OS keeps the server attached but clears the address, so reapply your config.
Done: traffic flows privately
Verify with a ping between two members. From now on this traffic never touches the public network.
The numbers
Isolated means isolated
- Per-network isolation enforced at the hypervisor. Your segment shares nothing with other customers.
- Each interface is bound to its own hardware address. This is also why VRRP virtual-MAC mode does not pass; real-MAC keepalived with gratuitous ARP works.
- Broadcast storm protection keeps a noisy neighbor from ever becoming your problem.
- Source-address filtering applies to your public interface only. On the private network the addressing is entirely yours.
- We never inspect or meter private traffic.
Common questions
Still have questions? Talk to our network team
Connect your servers privately
Free private networks on every VPS. Deploy two servers and try it in minutes.