Envoy Gateway vs OpenNJet Ingress Controller
Envoy Gateway
gateway.envoyproxy.ioOpenNJet Ingress Controller
njet.org.cnSide by side
| Figure | Envoy Gateway | OpenNJet Ingress Controller |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Kubernetes Ingress Controllers | 7.9 (#9) | 6.7 (#23) |
| Deployment | The project can manage Envoy Proxy as a standalone or Kubernetes-based application gateway. | The project README describes deploying KIC to Kubernetes using manifests, including namespace, service account, ConfigMap, IngressClass, custom resources, RBAC, Deployment and NodePort service. |
| Purpose | Envoy Gateway manages application and API traffic using Envoy Proxy as a standalone or Kubernetes-based API gateway. | OpenNJet KIC is a Kubernetes Ingress Controller built on OpenNJet proxy for cloud-native traffic management. |
| Traffic management | The project lists rate limiting, retries, circuit breaking, timeouts, and failover among its traffic management capabilities. | It provides dynamic locations, host and path routing, load balancing, dynamic upstreams, canary releases, TLS termination and SNI, TCP and UDP proxying, and WebSocket support. |
Plans
In their own words
Envoy Gateway
Envoy Gateway is a free, open-source application gateway for managing Envoy Proxy in standalone or Kubernetes-based deployments. It provisions and configures proxies through Kubernetes Gateway API resources, extending the API to expose Envoy features. Traffic management includes rate limiting, retries, circuit breaking, timeouts and failover. Security options include mTLS, JWT-based access control, OIDC integration and API-key authorization; listed authentication methods also include Basic Auth and external authorization. Envoy Gateway supports TLS termination and can attach an OCSP response from a Gateway certificate Secret during a TLS handshake. Metrics, access logging and distributed tracing are among its observability features. Installation options include Helm, Argo CD, Flux CD and Kubernetes YAML, though the quickstart requires a Kubernetes cluster. The project lists HTTP, HTTPS, gRPC, TLS, TCP and UDP support. Integrations and ecosystem projects include Envoy AI Gateway, Kuadrant, Knative, KServe and KEDA. Community help is directed through Envoy Slack, GitHub discussions and issues, and community meetings. Documentation cautions that the latest release includes recent main-branch commits and might not be stable.
OpenNJet Ingress Controller
OpenNJet Ingress Controller has no write-up on Specifiction yet; its figures are above.