public cloud  private network

A flexible, private connection between your instances

The emergence of software-defined networks (SDNs) in cloud infrastructures has given users increased flexibility when it comes to network management. In this spirit, the OVH Public Cloud lets you design and build your network architecture on demand. By creating private networks, you implement virtual switches that can hot-connect your project instances in real time, without any service interruptions.

Extended networks between regions

Public Cloud Private Networks are built on OVH vRack technology. You can use it to extend private networks between OVH datacentres, connecting instances across different regions around the world through private communication channels.


You can create up to 4,000 level 2 private networks. In concrete terms, launching a Private Network implements a new VLAN, whose communications are only accessible to the resources connected to it. This isolation can be used to segment control plane and data plane networks, for example.

Extension to other OVH services

You can also use the vRack to connect different OVH services to one another. You can extend your Public Cloud Private Network to connect with your Private Cloud or dedicated servers, for example. This way, you can distribute your application to suit your needs, while keeping the connections private.

Use cases

Multi-region disaster recovery plans (DRP)

As the Public Cloud is available in several OVH datacentres, by setting up a disaster recovery plan, your services will benefit from a private network’s capacity to expand into other regions. This way, you can sync your data via a secure channel to organise a simple, efficient DRP.

Terraform deployment industrialisation

Terraform's OpenStack driver is used to manage the OVH Public Cloud's Private Networks. If you are looking to deploy complex infrastructures that are difficult to industrialise, you can do so with resources like networks, subnets and ports via this Infrastructure-as-Code (IaC) tool.

Load balancing between locations

A distributed application can be deployed across multiple locations, without sacrificing the security and reliability of collaborative communications between nodes. This way, data from the same application or cluster can move between locations, with quick response times and full isolation.

How to

Create a Private Network

openstack network create net01

Create a subnet with DHCP

openstack subnet create subnet01 --network net01 --subnet-range




Ready to get started?

Create an account and launch your services in one minute



DHCP servers

When you create a network, you can choose to use addressing via DHCP. If you choose this option, a DHCP server will be launched on the network to serve your settings.

DNS integration

The DHCP configuration can include the definition of the DNS servers that should serve your network. This way, you can point to the DNS server of your choice.

Range definition

DHCP servers can serve a specific CIDR configuration, targeting only a part of the IP address range you have chosen.

Fixed or dynamic addresses

You can choose specific addresses in the network range for a port or instance. You will always need to configure this via DHCP, but you will retain control over the addressing plan by doing so.

Unattached ports

Private networks' ports are independent of their instances, so you can detach a port from an instance without losing it. This can be useful for projects that involve infrastructure orchestration.

tarif public cloud

Private Network billing

Private Networks and their traffic are both free of charge.