Private Networks & Routers

Private networks

When you create a VPS on Patrii Cloud, it connects to a private network inside your project. Private networks:

• Use private IP ranges (e.g. 10.0.0.x, 192.168.x.x)
• Are isolated to your project — other tenants cannot see or reach them
• Let your own VPS talk to each other freely (subject to security groups)
• Are not reachable from the Internet on their own

This is exactly what you want for databases, internal services, and any machine that should never be exposed directly to the public.

What a router does

A router connects networks together. Think of it as the same kind of box you have at home: everything on your local network sits behind it, and it decides what may pass between networks.

On Patrii Cloud a router lets you:

• Join multiple private networks in your project so they can route to each other
• Reach the Internet over IPv4 — but only once you attach a Public External Gateway (see the next article)

⚠️ A router on its own has no connection to the public Internet. It only routes between the networks you attach to it until you give it an external gateway.

How the pieces fit

• Private network — where your VPS live; isolated, private IPs
• Router — connects your private networks and (optionally) the IPv4 Internet
• Public External Gateway — the router's link to the public IPv4 network (paid — see next article)

Do I always need a router?

No. A router is required for IPv4 Internet access (outbound NAT and Floating IPs). If you only need IPv6 connectivity, you can skip the router entirely and attach your VPS directly to the public6 network — see the IPv6 article.