
agentgateway
7.5#4 in kubernetes ingress controllersFree planFree planWebAPILinuxmacOS
Visit
| Fact | agentgateway | Kusk Gateway |
|---|---|---|
| Authentication | Documented authentication methods include JWT, API keys, basic authentication and MCP authentication specifications. | Documented authentication modes include JWT, OAuth2/OIDC, custom authorization and Cloudentity. |
| Deployment | The project provides standalone binary, Docker and Kubernetes deployment paths. | Kusk says APIs can be published by adding an annotation to a service deployment, without additional configuration or DevOps support. |
| Intended users | The site invites tool-builders, platform engineers, and AI enthusiasts to join the community and describes the controls as suited to platform teams. | The maker presents Kusk for teams building modern REST APIs on Kubernetes and following an OpenAPI-first APIOps workflow. |
| Licence | The open-source project is licensed under Apache-2.0. | Kusk is presented as 100% open source under the MIT License. |
| Self-hosting | Agentgateway is designed to run on bare metal, virtual machines, containers or Kubernetes. | The product must run inside a Kubernetes cluster and can be installed locally or on a remote cluster. |
Agentgateway is aimed at platform engineers, tool-builders, and AI enthusiasts who need self-hosted traffic controls for services, LLMs, or agent systems. It also suits platform teams seeking routing, security, and observability features in one gateway.
Kusk Gateway suits teams building REST APIs on Kubernetes that use OpenAPI-first practices. It may fit teams seeking an open-source gateway with API validation, policy controls, and a central dashboard.