Side by side
Kong Ingress Controller vs N42 Gateway
Both stand on kubernetes ingress controllers. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan Linux
Visit Kong Ingress Controller Free plan LinuxSelf-hosted
Choose N42 Gateway if you need a free, self-hosted controller that configures HAProxy from Kubernetes Ingress or Gateway API resources. Its wide configuration set and live routing updates suit teams managing external access to cluster services. Check the Kubernetes and HAProxy version requirements before deploying; the project cautions against using its alpha and snapshot development versions in production.
Visit N42 GatewayThe facts
| Kong Ingress Controller | N42 Gateway | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Not published |
| Runs on | Linux | Linux, Self-hosted |
| Lowest paid plan | Not published | Not published |
| Plans published | None | None |
| Maker | Not published | Not published |
| Website | developer.konghq.com | github.com |
| On kubernetes ingress controllers | #22 of 28 | #18 of 28 |
Kong Ingress Controller: what it does well
N42 Gateway: what it does well
- Supports both Kubernetes Ingress and Gateway API models.
- Applies routing changes to HAProxy as Kubernetes configuration changes.
- Offers more than 200 configuration options.
- Includes TLS, ACME certificate management, rate limiting, and canary routing options.
- Apache-2.0 licensed and free to use.
What to know first
- Installation requires cluster administrative privileges.
- The latest listed release requires Kubernetes 1.21 or newer.
- External HAProxy deployments require version 2.4 or newer.
- Alpha and snapshot development versions are generally not recommended for production.
Alternatives to Kong Ingress Controller Alternatives to N42 Gateway The whole list
