No. 12 of 27 ·Kubernetes Ingress Controllers

N42 Gateway

Linux · Self-hosted

Visit site Alternatives

Freedom report

One barScore 5.4

Free tierNo free tier on record
Open codeNo open-source code on record
Runs widely1 of 6 device platforms
DocumentedPlans, terms and facts published

N42 Gateway is ranked #12 of 27 in Kubernetes ingress controllers on Freedom251. It runs on Linux, Self-hosted.

Compared on Kubernetes ingress controllers

Ingress API model: both
TLS automation: Yes
Canary routing: Yes
Rate limiting: Yes
Web application firewall: Yes
Auth policies: Yes
Deployment model: self-hosted

Best N42 Gateway alternatives

See all 20

Two bars ngrok Free tier No. 1$10/mo6.6 Two bars Traefik Proxy Free tier No. 2Free6.5 One bar agentgateway Free tier No. 3Free6.3 One bar Airlock Microgateway Free tier No. 4Free6.3 One bar Contour Free tier No. 5Free6.3 One bar Envoy Gateway Free tier No. 6Free6.3

The record

Purpose: N42 Gateway is a Kubernetes Ingress and Gateway API controller that configures HAProxy to route external requests to applications inside the cluster.
Dynamic updates: It reads routing configuration from Kubernetes resources and applies cluster updates to HAProxy on the fly.
Load balancer: The project describes N42 Gateway as built on the HAProxy load balancer.
Configuration: The maker says N42 Gateway has more than 200 configuration options for Ingress and Gateway API resources.
Configuration sources: Configuration can be set globally through ConfigMaps, per IngressClass through a linked ConfigMap, per Ingress, and per backend through Service annotations.
Scale: The documentation says there is no hard limit to the number of Ingresses or Services and reports clusters with tens of thousands working smoothly and fast.
TLS and certificates: Configuration options include TLS settings, client certificate authentication, secure TLS connections to backends, and ACME certificate management.
Installation: The maker documents installation with Helm into a running Kubernetes cluster and requires cluster administrative privileges for installation.
Platform and prerequisites: The documented v0.16 release requires Kubernetes 1.21 or newer and the maker lists Minikube, kind, k3s, k3d, and Colima as supported local Kubernetes environments.
Support: Users can ask questions in the #n42-gateway Kubernetes Slack channel and GitHub Discussions.
License: The GitHub repository identifies the project as licensed under Apache-2.0.
Use case: The maker presents N42 Gateway for exposing services running in Kubernetes clusters to external networks.
Live updates: Changes made to Kubernetes routing configuration are applied to HAProxy on the fly.
HAProxy: The project describes itself as powered by the HAProxy load balancer.

Where it ranks on Freedom251

Best Kubernetes Ingress Controllers in 2026#12 of 27

Is N42 Gateway yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote N42 Gateway

Sources

github.com/n42-gateway/n42-gateway· checked 4 Oct 2026
n42-gateway.github.io· checked 4 Oct 2026
n42-gateway.github.io/docs/configuration/keys/· checked 4 Oct 2026
n42-gateway.github.io/docs/getting-started/· checked 4 Oct 2026