Mesh Manager.
The product for federating Borz Clans.
A Borz Mesh will connect multiple Clans running on different hosts into a single typed message-routing layer. Mesh Manager will manage that federation — with the same policy, audit, and type safety that govern traffic inside a single Clan. On the design roadmap; planned to ship after Clan Control matures.
What Mesh Manager will give you.
Cross-host typed messages
An agent in one Clan will be able to send a typed message to an agent in a different Clan, on a different host — with the same type-checking the compiler applies locally.
Unified audit trail
Every cross-Clan message will carry the audit chain from its origin. Compliance logs will span the whole Mesh, not just individual Clans.
Declared data topology
A Mesh declaration will specify exactly which Clans exist and which agents may route to which others. No implicit side-channels; the topology is auditable at a glance.
Consistent policy enforcement
Per-tool and per-agent policies set in the Clan manager will extend across Mesh boundaries. A rule applied in one Clan will propagate to the others automatically.
EU-sovereign by design
Each Clan in a Mesh will run on infrastructure you control. The routing layer will never move data across a host boundary you have not declared.
Incremental adoption
Mesh will be an optional extension of the Clan runtime — not a replacement. You add Mesh when you have multiple Clans to connect. You do not need it to get started.
Organisations outgrow a single Clan.
A Borz Clan is designed to run in one supervised deployment unit. As teams grow, different parts of the organisation naturally want to run their own Clan — their own agents, their own policies, their own infrastructure.
Mesh will let those Clans collaborate without giving one Clan admin rights over another. The message boundary between Clans remains an explicit, audited, typed interface — the same discipline that holds inside a single actor, extended to the whole federation.
Each team runs their Clan on their own infrastructure with their own policy set.
Work that crosses a Clan boundary does so through a declared, typed message route.
Clans do not inherit each other's secrets or policies by default. Trust is declared explicitly in the Mesh definition.
Mesh Manager is on the design roadmap.
The first milestone is a reliable, fully-featured Clan Control.
We are in early access on the Clan runtime now.
Multi-Clan Mesh federation is the next major capability,
designed alongside Borz language–level
agent and
actor integration.
If your organisation needs to plan for multi-Clan federation,
get in touch early — input from early Clan deployments is shaping the design.
Start with a single Clan.
Mesh Manager will extend the Clan model to multiple hosts. The foundation is a working Clan Control deployment — request early access today.