One network across every cloud.
Connect AWS, GCP, Azure, and on-premise into a single flat network. No VPN gateways, no peering agreements, no cloud-specific tooling.
- Cloud-agnostic — same agent on every provider
- Kubernetes ready with cross-cluster pod communication
- CI/CD access to private resources across clouds
- DNS across clouds (
device.meshr)
Three steps to connect every cloud.
No cloud-specific configuration required.
Deploy agents on each cloud
Install the meshr agent on instances in AWS, GCP, Azure, or any on-premise server. One binary, same command everywhere.
curl -fsSL https://get.meshr.to/install.sh | sudo bashThey auto-discover and connect
Agents register with the control plane, discover peers across clouds, and establish encrypted tunnels automatically.
meshr login --token <setup-key>
# Connected to 4 peers across 3 cloudsAccess any resource by name
Every node gets a DNS name. Access resources across clouds as if they were on the same LAN. No IP juggling.
ping aws-api.meshr # 10.0.0.5
ssh gcp-worker.meshr # 10.0.0.12Everything you need for multi-cloud networking.
Subnet Routing
Expose entire VPC subnets through a single meshr node. Access private cloud resources without installing agents on every instance.
$ meshr routes add 172.16.0.0/16
✓ Advertising 172.16.0.0/16 via aws-gw
$ curl http://172.16.0.50:8080
# Reaches private AWS instanceKubernetes Ready
Cross-cluster pod communication without complex service mesh configs. Connect EKS, GKE, and AKS clusters into one network.
# Pod in GKE calls service in EKS
$ curl http://api-svc.eks-prod.meshr:8080
200 OK — 2ms cross-cloudAutomatic Failover
When direct connections between clouds fail, traffic automatically routes through relay nodes. No manual intervention, no downtime.
- Direct peer-to-peer when possible
- Automatic relay fallback on failure
- Sub-second failover detection
- Multi-path routing for redundancy
DNS Across Clouds
Every device and service gets a stable DNS name on the device.meshr domain. No more tracking IPs across providers.
$ dig aws-api.meshr
→ 10.0.0.5
$ dig gcp-worker.meshr
→ 10.0.0.12
$ dig azure-db.meshr
→ 10.0.0.20Multi-cloud the old way vs meshr.
Stop managing VPN gateways, peering connections, and cloud-specific networking tools.
| Capability | Traditional approach | meshr |
|---|---|---|
| Setup time | Days to weeks | Minutes |
| Cloud-specific config | VPC peering, Transit GW, VPN GW | None — same agent everywhere |
| Kubernetes support | Manual service mesh setup | Built-in cross-cluster networking |
| DNS resolution | Route53 / Cloud DNS / Azure DNS | Unified device.meshr domain |
| Failover | Manual BGP / routing changes | Automatic relay fallback |
| Subnet routing | Complex route tables per cloud | One command to advertise routes |
| Access control | Security groups + NACLs per cloud | Unified Zero Trust policies |
| Cost | $100s-1000s/mo in gateway fees | Free tier + fair pricing |
Connect every cloud in minutes.
Free for every feature while we're in beta. One agent, one control plane, no lock-in.