Isolated from the internet
The private network runs apart from the server’s public link. Internal traffic does not reach the internet and does not mix with public traffic.
Your servers on one network. Even in different countries.
Servers with a private network join an isolated network that is not visible from the internet. Databases, backups and internal services talk over it without going outside. A server’s page says whether it has one.
Capabilities
How it works
VLAN segments
The network can be split with VLAN tags (802.1Q): databases, backups, management and virtual machines each on their own.
Across countries
A server in Poland and a server in Germany or France share one network with no tunnels to configure. This is how a standby site is built.
Speed depends on the line
From hundreds of megabits to tens of gigabits per second. The private network speed is stated on each server’s page.
Good to know
What it gives you and what it does not
- Joins your servers within one country and across countries
- Whether a server has a private network, and how fast, is stated on its page under “Private network”
- An office connects to it through an encrypted tunnel (WireGuard or IPsec) to one of the servers
- Not on every server: where there is no private network, the server’s page says so plainly
- Distance does not disappear: between countries the response time is tens of milliseconds, and the speed is limited by the server’s private port
By line
Where the private network is available
| Line | Private network |
|---|---|
| Lite The most affordable servers for testing and non-critical workloads | none |
| Classic Proven servers at a moderate price | 500 Mbit/s on most servers |
| Standard Modern servers for most business workloads | 1 Gbit/s on most servers |
| Business The foundation for your production systems | 25 Gbit/s on every server |
| Turbo Maximum per-core speed | none |
| Power Many-core servers for heavy workloads | 50 Gbit/s on every server |
| Ultra Top-tier servers for clusters and storage | 50 Gbit/s on every server |
The table is drawn from the current catalogue. The exact figures for each server are on its page.
Getting started
Three steps to a shared network
- 1
Choose the servers
The page of every server of the future network must have a “Private network” line: the name of the product line alone is not enough.
- 2
Say so in the request
Write in the comment that the servers must share one private network — in one country or in several.
- 3
Configure the interfaces
Once the servers are delivered, set addresses on their private interfaces and, if needed, split the network into VLANs.
Ready to move your infrastructure to Europe?
Choose a server in the catalogue — with live availability and the price in hryvnia.