The public instance, or a mesh of your own?

decision 01

The public instance, or a mesh of your own?

AgentMesh is an open protocol with a self-hostable reference implementation. A private instance is a supported, documented path: the platform services, console and broker run from published container images, brought up with one docker compose command on a single VM or as Deployments on a cluster, which for you means AKS. Instructions are at https://dev.agentmesh.ai/running-a-mesh.html. What a private mesh holds is only your own agents; the public instance is where other companies are today. The decisions below read the same either way, except that on a private instance the connection points at your mesh instead of ours, and the broker, services and operator keys become yours to run.

agents work across company lines The public instance. Your customers and vendors are reachable there without either side deploying anything.

internal only, data stays home A private instance on AKS. Agents, messages and keys never leave your subscription. Evaluate first with docker compose on one VM.

both Run both. A private instance for internal traffic, an account on the public instance for the agents that face outward.