Agent telemetry is data too. Every trace holds tool calls, token counts, spend, and operational metadata about your agents, so residency and sovereignty rules apply to it like any other data. Three deployment models, described honestly.
The fastest path to value. Sign up, point your agents at our OpenTelemetry endpoint, and see traces, cost attribution, and governance evidence the same day.
Teams without data residency requirements who want to start now.
A dedicated, single-tenant instance of the control plane deployed in an EU cloud region. Same features as SaaS, with your telemetry stored only in the EU.
Buyers whose requirement is EU data residency.
We deploy the control plane single-tenant inside your environment (your Kubernetes cluster or VMs), operated jointly with your platform team. Raw agent telemetry never leaves your perimeter.
Strict sovereignty mandates where the evidence chain must stay under your jurisdiction.
Under the EU AI Act, deployers of high-risk AI systems need logging and human oversight evidence (Articles 12 and 26). That evidence is built from agent telemetry. If your workloads are bound by residency or sovereignty rules, the record of what your agents did is bound by the same rules: you cannot satisfy a sovereignty mandate with a governance layer that ships every trace to someone else's cloud by default.
MeshAI is OpenTelemetry-native, which keeps the evidence portable by design. Your agents emit standard OTLP traces, and the control plane can receive them in our cloud, in a dedicated EU region, or inside your own perimeter. The instrumentation does not change when the deployment model does.
Yes, for qualified design partners. MeshAI deploys the control plane single-tenant inside your environment (your Kubernetes cluster or VMs), operated jointly with your platform team, so raw agent telemetry never leaves your perimeter. Customer-hosted deployment is offered as a paid design-partner pilot with written deployment requirements and a named executive sponsor, not as self-service general availability.
Yes, on request. MeshAI offers a dedicated single-tenant instance of the control plane deployed in an EU cloud region, with agent telemetry stored only in that region. Contact us to scope an EU-region deployment for your organization.
MeshAI stores agent telemetry metadata: OpenTelemetry traces of agent activity including tool calls, token usage, cost data, and model and agent identifiers, plus the governance evidence derived from them (policy evaluations, approval records, audit trails). MeshAI never stores prompt text or completion content. Telemetry metadata can still identify people, systems, and business activity, which is why deployment model and data residency matter.
It depends on the requirement. EU-region hosting keeps telemetry physically stored in the EU, which satisfies data residency requirements. MeshAI Labs is a US company, so EU-region hosting alone does not place data beyond the reach of US legal process. Organizations whose requirement is jurisdictional control rather than geographic storage should evaluate the customer-hosted deployment model, where telemetry stays inside their own infrastructure.
Tell us what would have to be true (hosting, data flow, and sign-off) for your organization to run an agent control plane. We are selecting a small number of design partners in regulated verticals.
Talk to us