VPC Private Networking
Last updated 20 February 2026
Overview
A Virtual Private Cloud (VPC) creates an isolated private network between your servers. Traffic on a VPC stays within our network and never traverses the public internet.
Benefits
- Security — keep database and backend servers off the public internet
- Performance — private traffic has lower latency and higher throughput
- No bandwidth charges — VPC traffic is not counted towards your bandwidth allocation
Create a VPC
- Go to Networking → VPC in the dashboard.
- Click Create VPC.
- Choose a name and the data centre.
- Define the IP range (e.g.,
10.10.0.0/16). - Click Create.
Add Servers
Attach servers to the VPC from the VPC detail page or from the server's networking tab. Each server receives a private IP from the VPC's IP range.
Example Architecture
A typical setup:
- Web server — public IP + VPC IP (10.10.0.2)
- Database server — VPC IP only (10.10.0.3), no public access
- Cache server — VPC IP only (10.10.0.4), no public access
The web server connects to the database and cache using private IPs. The database and cache have no public IP, making them inaccessible from the internet.
Limitations
- VPC traffic is limited to servers within the same data centre.
- Cross-DC VPC is not currently available.