Agent protocols are becoming infrastructure.
Infrastructure needs operations.
Our story
Rivano was started by engineers who ran AI agents in production and felt the gap firsthand — Datadog APM saw opaque JSON-RPC bodies, security teams had no audit story for tool usage, and "we trust the agent" was the de facto policy. The hyperscaler answer was a managed gateway with vendor lock-in. There wasn't a self-hosted answer that respected operators' existing observability stack.
We built the first one we needed: mcpgw, a single-binary gateway for the Model Context Protocol that drops inline between agents and MCP servers, applies policy, and emits OpenTelemetry spans your existing Datadog Agent already understands. One inline hop. Three policy actions. No phone-home.
mcpgw is the first product. Rivano is the company that makes it. We expect to ship more gateways for adjacent agent protocols — A2A is the next one we're tracking — but every Rivano product will follow the same posture: self-hosted, single binary, no phone-home, transparent pricing, no per-call billing.
The Rivano gateway portfolio
One company, multiple gateways, shared posture. Each Rivano product solves a specific agent-protocol gap with the same playbook.
mcpgw
Self-hosted gateway for the Model Context Protocol. Datadog-native tracing. Single Go binary.
a2agw
Self-hosted gateway for Agent-to-Agent (A2A) skill invocations. Same posture as mcpgw, different protocol.
Future Rivano gateways will appear here as they reach v1. Same self-hosted, no-phone-home posture. Same transparent pricing.
Try mcpgw today.
10 minutes from docker pull to first traced span in Datadog. No credit card.