Solution · Infrastructure
A single private backbone across every cloud provider
Stop managing cross-VPC peering, firewall rules per provider, and provider-specific VPN gateways. Rabtly gives your services a shared private address space across AWS, GCP, Azure, and on-prem.
No VPC
peering complexity
P2P
direct inter-node routing
Any
cloud or on-prem supported
The problem
Multi-cloud networking is a full-time job
Each cloud provider has its own VPC model, routing tables, security groups, and peering constraints. Getting two clouds to talk securely takes days.
VPC peering requires non-overlapping CIDR blocks — hard to retrofit
Provider-specific VPN gateways charge per tunnel-hour
Firewall rules across three consoles drift out of sync
No unified view of cross-cloud service reachability
How Rabtly helps
One overlay network. No cloud coupling.
Provider-agnostic overlay
Rabtly nodes form a mesh over your existing cloud networking — no VPC peering, no provider-specific VPN gateways, no CIDR restrictions.
Direct peer-to-peer routing
Nodes establish direct WireGuard tunnels where possible. Traffic only touches a relay when NAT traversal requires it.
Uniform private address space
Every node — regardless of cloud — gets a private IP in the `100.64.0.0/10` range and a MagicDNS hostname.
Encrypted in transit
All cross-cloud traffic is end-to-end encrypted with WireGuard. Even if a provider's internal network is compromised, your data stays safe.
Getting started
How it works
Deploy control plane
Rabtly Cloud or self-hosted — either gives you a control plane accessible from every cloud.
Install agents on VMs
Run the Rabtly agent on instances in each cloud. They enroll and get a mesh IP automatically.
Add on-prem nodes
Add on-prem servers to the same mesh. Works through NAT, firewalls, and private links.
Services reach each other
Databases, APIs, and services on different clouds talk over the private mesh by hostname or IP.