Multi-Cloud Networking
Your infrastructure spans multiple cloud providers or regions, and services need to talk to each other privately — without VPC peering gymnastics or public endpoints.
The problem
Connecting networks across AWS, GCP, Azure, and bare metal traditionally means provider-specific peering, transit gateways, and overlapping-CIDR headaches. Each new provider or region multiplies the configuration.
How Rabtly helps
- One flat private network — every instance joins the same Rabtly network and gets a private IP, regardless of provider.
- Encrypted, direct traffic — cross-cloud connections are end-to-end encrypted and go peer-to-peer where the network allows.
- No inbound rules — works behind security groups and firewalls with nothing exposed publicly.
How it works
Install Rabtly on each instance
Add the daemon to instances in every cloud and region as part of your provisioning.
They join the same network
All instances appear on one private network and can address each other by Rabtly IP or name, across provider boundaries.
Restrict cross-service traffic with groups
Use group-based access control so, say, web reaches api reaches database — and nothing talks to what it shouldn’t.