IPSEC GATEWAYS Overview Features Site-to-Site VPN Cloud Connectivity Supported Platforms

CLOUD CONNECTIVITY

Your cloud, on your private network

Encrypted IPsec tunnels between offices, data centres, and your VPCs — AWS, Azure, and Google Cloud, without exposing anything to the internet.

Plan a cloud deployment Supported clouds

Private paths to private clouds

Your cloud VPN endpoint (AWS VGW, Azure VPN Gateway, GCP Cloud VPN) peers with a VPNGeek gateway over standard IKEv2. Databases, internal APIs, and admin panels stay off the public internet — reachable only through the encrypted tunnel.

Databases & storage without public endpointsInternal APIs reachable only from your sitesAdmin access without bastion sprawl

Cloud scenarios we see weekly

Office → cloud

Staff reach VPC resources as if they were local.

Data centre → cloud

Hybrid workloads and migrations over a private path.

Multi-cloud

AWS ⇄ Azure ⇄ GCP through one gateway hub.

Cloud → cloud

Link VPCs across regions and accounts.

ARCHITECTURE

One hub, every environment

From plan to monitored, in a day

Plan

Choose regions and map VPC + on-prem CIDRs.

Configure

Cloud-specific templates prefill the tricky parts.

Validate

Both phases up, routes propagated, endpoints reachable.

Monitor

Live status, alerts, and event logs from day one.

Routing you design, not inherit

Subnets & routes — Define exactly which CIDRs traverse each tunnel.Segmentation — Keep prod, staging, and office traffic on separate tunnels.Firewall alignment — Works with your security groups and firewall rules, not around them.

SECURITY & RELIABILITY

Encrypted, redundant, and watched

IKEv2 · AES-256-GCM · PFS on every legRedundant tunnels & automatic failoverDPD monitoring with instant alertsSLA-backed support from network engineers

Supported cloud platforms

AWS — Virtual Private Gateway & Transit Gateway · route-based IKEv2Microsoft Azure — Azure VPN Gateway · route-based IKEv2Google Cloud — Cloud VPN (classic & HA) · route-based IKEv2

Full compatibility details →

Growing into more regions or providers?

Add tunnels from the same hub — every environment stays on one dashboard, one map, one bill.

Discuss your topology

Cloud connectivity questions

Which clouds are supported?

AWS, Azure, and Google Cloud via their native VPN endpoints — anything speaking route-based IKEv2 works.

Do we need public IPs in the VPC?

Only the cloud VPN endpoint is public; your workloads stay on private subnets.

What about redundancy?

Run paired tunnels (e.g. AWS's dual-tunnel VGW or Azure HA) — failover is automatic.

Multi-region deployments?

Place gateways in any of 6 regions and hub tunnels per continent for latency.

Take your cloud off the public internet

Plan a cloud deployment Check compatibility Talk to a specialist