A managed mesh designed to run in your perimeter
Some networks can't hand control or key material to anyone else. On Enterprise, Vexaro Mesh, now in development, is designed to run the controller and keys inside your own perimeter, with full control of your data. It remains a managed product, hosted where your data has to stay.
Why teams insist on self-hosting
For regulated, air-gapped or sovereignty-bound networks, where the control plane lives is the whole decision.
Compliance or data-residency rules require that key material, routing decisions and access logs never leave your perimeter, which rules out a cloud-only control plane.
Open-source self-hosted meshes can deliver the perimeter requirement, but you take on running, patching and supporting the control plane yourself.
Hosted SaaS gives you support and polish, but it puts the control plane, and often the keys, in someone else's cloud, outside your audit boundary.
How self-hosting will work
The control plane is designed to move inside your walls while the experience stays managed.
- 1
The controller in your perimeter
On Enterprise, the controller is planned to run inside your own environment, so the brain of the network lives behind your firewall, not in a shared cloud.
- 2
Keys stay with you
Key material is designed to stay inside your perimeter under your control, so the cryptographic trust of the network never leaves your audit boundary.
- 3
Gateways mesh as usual
Site gateways are designed to register with your controller and build the same direct full mesh, so the whole data plane is governed from inside your walls.
- 4
Audit on your terms
Routing, access logs and policy are designed to stay in your environment, so audits read from systems you own and can export to your own SIEM.
What self-hosting is planned to give you
Control over the parts that matter for compliance, designed without giving up the managed experience.
Controller in your perimeter
On Enterprise, the control plane is planned to run inside your environment rather than a third-party cloud, so routing decisions are made behind your firewall.
Your keys, your boundary
Key material is designed to stay under your control inside the perimeter, keeping the cryptographic trust of the network within your audit scope.
Full data control
Access logs and policy are designed to live in systems you own, so data-residency and sovereignty requirements are addressed by the architecture.
A supported product
Instead of a mesh you assemble and maintain yourself, the plan is a product you host with vendor support and a polished console.
Why Vexaro Mesh is designed for self-hosting
On Enterprise, the controller and keys are planned to run inside your own perimeter with full control of your data. Self-hosting is planned as a main deployment mode, not an add-on.
It is planned as a managed product you self-host: vendor support and a polished console, while the control plane sits inside your walls.
Hybrid by design: some sites run against a self-hosted controller and others against the cloud console, all in one network. That helps during a migration or in mixed estates.
Pricing is planned per connected site, so a self-hosted estate would be priced by location, with no per-user or per-device control-plane fees on top.