Solo.io
Sources: Solo.io (homepage) · Introducing agentdesktop · agentgateway joins the Linux Foundation
Identity and role
Solo.io is a cloud-native networking and API infrastructure vendor, built on contributions to Istio and its own Gloo Edge API gateway. The company carries that networking and policy-enforcement background into agentic-AI infrastructure, positioning its products as the connectivity and governance layer beneath AI agent deployments rather than as a model- or prompt-layer control.
Agentic AI product line
Solo.io maintains two complementary products for agentic-AI traffic. agentgateway is a Rust-based open-source data plane for MCP and A2A traffic, serving as a network-layer control point for agent-to-tool and agent-to-agent communication; the Linux Foundation announced Solo.io’s donation of the project on August 25, 2025.1 agentdesktop, released September 3, 2026 under an Apache 2.0 license, extends the same governance model to the endpoint: it discovers and governs the AI agent harnesses (Claude Code, Codex, VS Code agent extensions) running on developer desktops, and hands short-lived credentials carrying user, device, and tool context to agentgateway for enforcement at the traffic layer. The two products divide the stack: agentdesktop supplies inventory, device and user context, and declares and enforces policy locally on the endpoint (sandbox and MCP-connection restrictions translated into each harness’s native configuration); agentgateway enforces that same policy in-path against model, MCP, and inter-agent traffic once it leaves the endpoint. Solo.io announced a commercial distribution, Solo Enterprise for agentgateway, on September 10, 2026, extending the same enforcement to any deployment environment rather than the mesh alone.2
Relevance to this wiki
The CMM’s D5 Egress & Network domain lists agentgateway as its sole open-source example of a mesh-deployed agent-aware proxy. Solo.io positions agentdesktop as extending agent governance from cloud and Kubernetes environments to the developer’s machine, reaching the agent-harness layer that mobile device management leaves uncovered because MDM inventories the device rather than the harness running on it.