Site-to-Site VPN
Connect your Public Cloud private network to your datacentre, a branch office or another cloud provider, over encrypted IPsec tunnels, with static or BGP routing and automatic failover between two tunnels. Alpha opens November 17, 2026, in Gravelines (GRA7), and is free to use.
- Status
- Alpha
- Category
- Network & Security
- Access
- Early access
- Release date
What is Site-to-Site VPN?
Site-to-Site VPN interconnects your Public Cloud private network with your site, your datacentre, a branch office or another cloud provider. A VPN gateway in that private network routes the traffic over encrypted IPsec tunnels across the Internet.
Your instances and your on-premises servers then communicate on their private addresses, as if they shared a network, and their traffic never crosses the Internet unencrypted. Two tunnels to the same site keep the connection available when one of them fails.
How does it work?
- Open Site-to-Site VPN. In the OVHcloud Console, select your Public Cloud project, then open the Network section and click Site-to-Site VPN, tagged Alpha.
- Create a VPN gateway. Choose its region and, for each subnet it must serve, a private network and a subnet. The gateway receives a public IPv4 and a public IPv6 address.
- Create the IPsec connection, in one page:
- Choose the routing: static, or BGP with one eBGP session per tunnel.
- Define the endpoint groups: the local networks, on the OVHcloud side, and the remote site's networks.
- Choose the security proposal, the recommended one or your own IKE and IPsec policies, then one or two IPsec tunnels, each with the remote device's public address and its pre-shared key.
- Configure the remote device with the values the recap shows for each tunnel: our public IP, the networks on each side, the IKE and IPsec algorithms and, with BGP, the BGP addresses.
- Route your instances to the VPN gateway. On the recap, click Add the routes: each subnet gets a host route to the remote networks through the gateway. Instances pick the routes up at their next DHCP lease renewal, or when they restart.
For further details, follow the Get started in the Console guide on docs.ovhcloud.com.
Use cases
Extend your datacentre
Connect your on-premises network to your Public Cloud instances, in both directions, over an encrypted connection.
Connect another cloud provider
Interconnect a Public Cloud private network with a network at another cloud provider, through its VPN service, with static routes or BGP.
Connect a branch office
Give a remote site private access to the applications you run on Public Cloud, without exposing them to the Internet.
What are the benefits for you?
- Encrypted connection. Traffic between your private network and your site is encrypted with IPsec for its whole way across the Internet.
- Private addressing. Your instances and your on-premises servers communicate on their private addresses, without exposing your instances to the Internet.
- Built for failover. Two tunnels to the same site fail over to each other automatically, with static routing or BGP.
- Modern encryption only. Tunnels negotiate IKEv2 with AES-CBC or AES-GCM, SHA-2 and Diffie-Hellman groups up to Curve25519. IKEv1, SHA-1, 3DES and the weak groups are refused.
What's next on the roadmap?
The Beta brings high availability of the VPN gateway, with two instances and automatic failover between them, gateway sizes with guaranteed bandwidth, private IPv6 traffic through the tunnels, tags and a Terraform provider.
General Availability adds metrics for each tunnel and BGP session, logs and an audit trail, and access control with OVHcloud IAM.
Help shape Site-to-Site VPN
This Alpha is open to the first 100 customers. We're looking for feedback on real remote devices, real networks and real routing setups before opening it more broadly. No SLA applies during the Alpha.
How to share your feedback?
Comment on the Site-to-Site VPN roadmap item.
Need some help?
Follow the Get started in the Console guide on docs.ovhcloud.com, step by step.
Ready to try it?
Open Site-to-Site VPN in the Console, in a Public Cloud project.
Questions, answered.
No. Site-to-Site VPN is in Alpha, for testing and evaluation only: do not use it for production workloads. OVHcloud reserves the right to close the Alpha, or to suspend the service, at any time. During the Alpha, each VPN gateway runs on a single instance: a failure of that instance interrupts its tunnels until it is back. High availability comes with the Beta.
For now, the Alpha is limited to the first 100 customers, and OVHcloud will raise this limit progressively.
Yes, Site-to-Site VPN is free to use during the Alpha and the Beta. Pricing is published at General Availability.
No. As with any OVHcloud Labs product, no SLA applies while Site-to-Site VPN is in Alpha.
Any device or cloud VPN gateway that supports IKEv2 with pre-shared keys: an on-premises router or firewall, or another cloud provider's VPN service, with static routes or BGP.
Yes. Site-to-Site VPN connects to the VPN service of AWS, Azure, Google Cloud and Scaleway over IPsec, with static routes or BGP. A step-by-step guide is available for AWS: Connect to AWS, on docs.ovhcloud.com. Guides for the other providers will follow.
Not yet. The Alpha is managed from the OVHcloud Console, and a Terraform provider is planned for the Beta.
Shape what ships next.
Join the User Experience Program to test upcoming products, get early alpha and beta access, and put your fingerprints on the roadmap.