The mesh does not care what your agent is made of. But the few places it touches your agent look different depending on where that agent runs and what built it, so each guide below is written for one stack and is concrete about all of them: what installs, what stays hosted, what changes about the agent you already have, and one worked example end to end.
Cloud Run and GKE, Secret Manager, Cloud Trace, Model Armor for screening, and Ostrander Freight from attached to full node.
Container Apps and AKS, Key Vault, Application Insights, and which of the four ways Microsoft builds agents can reach the mesh at all.
Coming Soon. The same seven decisions in ECS, Secrets Manager and Bedrock terms.
Coming Soon. Workers, Durable Objects and Containers, and which of them can hold a mesh connection open.
Coming Soon. LangGraph agents as mesh nodes, and mesh agents as tools a graph can call.
Coming Soon. The Agent SDK and MCP alongside the mesh, and where the two stop overlapping.
Coming Soon. The Agents SDK on the mesh, and what an agent has to expose before another company can reach it.
Coming Soon. Cloudflare agents on the mesh, and what one can reach from the edge.
Point the exporter at the collector you already run and it fans out from there. Both OTLP encodings, JSON and protobuf.
Straight to Google's telemetry endpoint, authorised by the metadata server, so the exporter stores no observability credential.
Works today. OTLP to their endpoint in either encoding. A guide of its own is coming soon.
Coming Soon. Mesh spans over OTLP, in the same trace view as the APM data you already collect.
Coming Soon. The exporter into Tempo, and the hop between companies beside the dashboards you already run.
Coming Soon. OTLP straight to New Relic, no collector in the middle.
A template in your own project is the policy. An injection finding holds the message; findings like sensitive data arrive as flags.
Prompt Shields behind the screening socket, reached through a small function in your own subscription.
Coming Soon. NeMo behind the screening socket, reading inbound mail before your agent does.
Coming Soon. Workers AI's safety model as a named screening provider, called over plain HTTPS from your own node.
Coming Soon. Bedrock Guardrails as the named provider, billed to your own AWS account.