One network across every cloud and your data center
Vexaro Mesh, now in development, is designed to link on-prem with AWS, GCP and private clouds into a single address space. Each environment will peer into one shared fabric, clouds will reach each other directly across it, and it is all planned to be defined as code.
Why multi-cloud networking gets tangled
Stitching clouds together with each provider's native plumbing leaves you with a patchwork.
Each cloud has its own VPC peering, transit gateways and route tables, so a connection between AWS and GCP becomes a per-provider integration to design, build and keep in sync.
Overlapping CIDR ranges and NAT between environments turn a simple cross-cloud call into an addressing puzzle, and the rules drift as teams add subnets.
Access policy ends up scattered across security groups, firewall rules and provider IAM, with no single place to see who can reach what across all of it.
How clouds will join one fabric
The same planned gateway model that links offices is designed to link cloud regions and on-prem.
- 1
A gateway in each environment
A gateway is planned to run as a container or VM in each cloud account and region and in your data center, provisioned from the infrastructure as code you already use.
- 2
Peer into one overlay
Each gateway is designed to join the shared fabric and get an address in one coherent space, so environments stop colliding on overlapping ranges.
- 3
Clouds reach each other directly
AWS, GCP, private clouds and on-prem are designed to hold direct encrypted tunnels across the overlay, so cross-cloud traffic takes the shortest path instead of detouring through a hub.
- 4
Govern it centrally
Access rules for the whole multi-cloud network are planned to be set centrally from one console, instead of being scattered across per-provider tools.
What is planned for multi-cloud teams
A single fabric designed to replace a stack of per-provider integrations.
Single address space
Every environment is designed to share one coherent address space, so services reach each other without per-cloud NAT gymnastics.
Direct cloud-to-cloud paths
Clouds are designed to peer into the same fabric and connect directly across it, keeping inter-cloud latency low and paths predictable.
Infrastructure as code
Sites and policy are planned to be defined through the API, so a new region or account joins from your pipelines, not a console click-path.
One policy plane
Role-based access for the entire multi-cloud network is planned from one place, with the access log exportable to your SIEM.
Why Vexaro Mesh is designed for multi-cloud
A gateway is planned as a plain VM or container, so it fits into any cloud account or region the same way. There is no provider-specific networking product to learn for each cloud.
Planned per-site pricing means a cloud region would cost the same as an office: one price per connected gateway, regardless of how many workloads sit behind it.
The full mesh is designed to give direct cloud-to-cloud and cloud-to-on-prem paths, instead of hairpinning everything through one transit hub.
The controller is planned to run in the cloud or, on Enterprise, in your own perimeter. That helps when one of the environments is a private or regulated cloud.