Contour vs Ingress-NGINX
A side-by-side comparison of two self-hosted reverse proxy & gateways options — licensing, setup difficulty, resource needs, and what each one replaces.
| Feature | Contour | Ingress-NGINX |
|---|---|---|
| Deploy effort | Read-the-docs project | Read-the-docs project |
| Health score | 89 · Excellent | 15 · At risk |
| Status | Actively maintained | Archived |
| Category | Reverse Proxy & Gateways | Reverse Proxy & Gateways |
| License | Apache-2.0 | Apache-2.0 |
| Language | HTML | Go |
| Setup difficulty | Medium | Medium |
| Min. RAM | 256 MB | 256 MB |
| Deployment | kubernetes, helm | kubernetes, helm |
| GitHub stars | ★ 3,951 | ★ 19,468 |
| First released | 2017 | 2016 |
| Replaces | AWS ALB Ingress | AWS ALB Ingress |
What are Contour and Ingress-NGINX?
Contour
Contour is a Kubernetes ingress controller that uses the Envoy proxy as its data plane. It provides advanced routing through its HTTPProxy custom resource.
- Envoy-powered ingress
- HTTPProxy CRD
- Dynamic configuration
- TLS and delegation
Ingress-NGINX
Ingress-NGINX is the community-maintained Kubernetes ingress controller built on NGINX. It routes external HTTP and HTTPS traffic to services inside a cluster using ingress resources.
- NGINX-based ingress
- TLS termination
- Path and host routing
- Annotations for fine control
Contour vs Ingress-NGINX: key differences
The biggest difference is maintenance: Ingress-NGINX's repository is archived and no longer developed, while Contour is actively maintained. Contour is written in HTML, while Ingress-NGINX is built with Go. Ingress-NGINX has the considerably larger community, at 19,468 GitHub stars versus 3,951.
Why pick each one
Choose Contour if…
- Released under the Apache-2.0 license
- Kubernetes-ready with Helm charts available
- Active community (4k GitHub stars)
- Written in HTML
Choose Ingress-NGINX if…
- Battle-tested at scale
- Wide community adoption
- Flexible annotation system
Watch out for
- Upstream development stopped
- Annotation config sprawl
Frequently asked questions
Is Contour or Ingress-NGINX better?
Neither is universally better. Ingress-NGINX has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are Contour and Ingress-NGINX free and open-source?
Yes. Contour is licensed under Apache-2.0 and Ingress-NGINX under Apache-2.0. Both can be self-hosted at no software cost.
Can I run Contour and Ingress-NGINX with Docker?
Contour: check the project docs for container support. Ingress-NGINX: check the project docs for container support.