
Envoy Gateway
6.1#8 in kubernetes ingress controllersFree planFree planAPISelf-hosted
Visit

| Fact | Envoy Gateway | Higress |
|---|---|---|
| Deployment | The project can manage Envoy Proxy as a standalone or Kubernetes-based application gateway. | A Docker all-in-one deployment exposes the console on port 8001, HTTP gateway on 8080 and HTTPS gateway on 8443. |
| Observability | The project lists metrics, access logging, and distributed tracing as observability features. | The AI statistics plugin records token counts, first-token latency, total request latency and logs across gateway, route, service and model dimensions. |
| Security | Its security controls include mTLS, JWT-based access control, OIDC integration, and API-key authorization. | Listed protections include prompt-attack detection, sensitive-content identification, data privacy protection, and output-content filtering. |
| Traffic management | The project lists rate limiting, retries, circuit breaking, timeouts, and failover among its traffic management capabilities. | Its AI gateway supports Token-based quotas and rate limiting, API key pool rotation, and consumer authentication. |
Envoy Gateway suits teams deploying a self-hosted application gateway with standalone or Kubernetes-based modes. The quickstart requires a Kubernetes cluster, and installation options include several deployment tools and Kubernetes YAML.
Higress suits teams that need a self-hosted gateway for AI services and cloud-native traffic. It may also fit those needing MCP, Kubernetes gateway, or API lifecycle capabilities.