Agent Gateway
3.7K stars. Single gateway for all agentic AI traffic — essential for enterprises running multiple AI agents needing security and governance.
Open-source proxy supporting MCP and A2A protocols. Routes traffic across LLM providers with RBAC and content filtering. Agent-to-agent collaboration support.
- Route all AI agent traffic through a single secure gateway
- Enforce access controls across multiple AI tools and agents
- Monitor and audit agent-to-agent communication
3.7K stars. Single gateway for all agentic AI traffic — essential for enterprises running multiple AI agents needing security and governance.
Enterprise teams running multiple AI agents that need centralized security, observability, and routing.
https://github.com/agentgateway/agentgateway
By agentgateway
How to Get It
See the Standalone Quickstart: https://agentgateway.dev/docs/quickstart (Kubernetes quickstart: https://agentgateway.dev/docs/kubernetes/latest)
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Once it’s connected, paste this into Claude:
Help me route all AI agent traffic through a single secure gateway
Trust Signals Reviewed
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- Agentgateway: a fast, feature rich, Kubernetes native proxy — Reddit · 60 pts
- Agentgateway v1.0: A Rust-based Kubernetes Gateway API implementation built for — Reddit · 33 pts
- What is the best MCP GATEWAY? — Reddit · 31 pts
3 mentions across 1 sources
Reviewer notes
Reviewed review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 3,724 GitHub stars; 179 contributors; last commit 4d ago; license Apache-2.0.
2026-05-10: Useful if you're running multiple agents across different LLM providers and need a single choke point for auth, routing, and content policy — the RBAC and MCP/A2A protocol support makes it a reasonable fit for enterprises trying to avoid per-agent security sprawl. The tradeoff is real: you're adding a critical path dependency, and with only one confirmed production mention, community adoption is still early. Config complexity scales fast with multi-provider policy rules. Worth watching, but teams with tight uptime requirements should stress-test failover before committing.
Things to check
- Introduces a network hop and dependency on gateway uptime; configuration complexity grows with policy rules and multi-provider setups. Open-source means community-driven maintenance and potential gaps in production hardening.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 3,724 GitHub stars; 179 contributors; last commit 4d ago; license Apache-2.0.