OpenNJet Ingress Controller
OpenNJet Ingress Controller: A self-hosted, open-source controller for teams that need flexible Kubernetes traffic routing. Ranked #18 of 28 in Kubernetes Ingress Controllers by our editors (7.5/10); pricing: Free plan; best for teams needing dynamic NGINX-style Kubernetes routing.
At a glance
- Editor score7.5 / 10
- PricingFree plan
- Best forTeams needing dynamic NGINX-style Kubernetes routing
- Free planYes
- Paid fromFree
- Ingress API modelBoth
- Facts checked23 Sep 2026
Where it wins
- Routes traffic with Kubernetes Ingress and VirtualServer resources
- Updates routes and upstreams dynamically without reloading proxy configuration
- Supports canaries, TLS/SNI, TCP/UDP, WebSockets and Prometheus metrics
Where it doesn't
- Requires deployment within a Kubernetes environment
- Support is community-based
- Named integrations are limited to ADC and Prometheus
Our verdict on OpenNJet Ingress Controller
OpenNJet Ingress Controller is an open-source Kubernetes ingress controller based on the OpenNJet proxy. It processes standard Kubernetes Ingress resources for host- and path-based routing, alongside VirtualServer custom resources for advanced content-based routing. Teams can use it to direct cluster traffic, manage upstreams, terminate TLS, and handle HTTP as well as TCP, UDP, and WebSocket traffic. Its self-hosted deployment suits teams that want to operate routing infrastructure inside their Kubernetes environment rather than adopt a managed service.
Routing and traffic management are its clearest strengths. OpenNJet documents dynamic updates to routes and upstreams without reloading proxy configuration, round-robin and consistent-hash load balancing, upstream health checks, and cross-namespace configuration. Canary releases and traffic management provide ways to steer traffic during releases. TLS termination and SNI cover encrypted connections, while Prometheus metrics support monitoring workflows. The mix of Ingress API and VirtualServer resources gives teams a standard entry point plus a custom-resource option for more advanced routing rules.
The project is free and open source, with a self-hosted deployment model and community support. Its named integrations are ADC and Prometheus, so teams should assess how that footprint fits their existing platform rather than assume a broader supplied ecosystem. This is a practical fit for Kubernetes operators who value dynamic NGINX-style routing and can manage the controller themselves. Teams seeking a managed service, commercial support, or a controller whose fit depends on specific authentication or rate-limiting capabilities should compare alternatives against those requirements before choosing OpenNJet.
Your product? Our editors can test OpenNJet Ingress Controller in depth and publish a review, labelled as paid · from $149/mo →
OpenNJet Ingress Controller pricing
OpenNJet Ingress Controller fact sheet
| Free plan | Yes |
|---|---|
| Paid from | Free |
| Ingress API model | Both |
| TLS automation | Not verified |
| Canary routing | Yes |
| Rate limiting | Not verified |
| Web application firewall | Not verified |
| Auth policies | Not verified |
| Deployment model | Self-hosted |
| Deployment | Self-hosted |
| Support | Community |
| Built for | Small business, Mid-market, Enterprise (editorial estimate) |
| Integrations | 2 integrations: ADC, Prometheus |
| Pricing | Free plan |
| Website | njet.org.cn |
| Facts checked | 23 Sep 2026 |
OpenNJet Ingress Controller integrations
OpenNJet Ingress Controller lists 2 integrations on its own site.
- ADC
- Prometheus
Alternatives to OpenNJet Ingress Controller
- Traefik ProxyA broad self-hosted ingress proxy with discovery, multi-protocol routing, and observability.9.3
- NGINX Ingress ControllerA free, self-hosted controller for routing, TLS, traffic policies, and edge integrations.9.2
- Kong Ingress ControllerA free, extensible choice for Kong-centered Kubernetes API platforms.9.1
See all OpenNJet Ingress Controller alternatives →
Used OpenNJet Ingress Controller? Be the first to review it
The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used OpenNJet Ingress Controller for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.
Write a reviewTwo minutes · verified accounts only · read by an editor before it appears
Featured on iTechGuides
OpenNJet Ingress Controller is listed in our Kubernetes Ingress Controllers directory. Add the badge to your site — it links back to this page.
<a href="https://www.itechguides.com/products/opennjet-ingress-controller/"><img src="https://www.itechguides.com/best/badge/opennjet-ingress-controller.svg" alt="Featured on iTechGuides" width="230" height="46"></a>
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update