Contour vs HAProxy Kubernetes Ingress

A side-by-side comparison of two self-hosted reverse proxy & gateways options — licensing, setup difficulty, resource needs, and what each one replaces.

Not the right match-up?
FeatureContourHAProxy Kubernetes Ingress
CategoryReverse Proxy & GatewaysReverse Proxy & Gateways
LicenseApache-2.0Apache-2.0
LanguageHTMLGo
Setup difficultyMediumMedium
Min. RAM256 MB256 MB
Deploymentkubernetes, helmkubernetes, helm
GitHub stars★ 3,944★ 862
First released20172019
ReplacesAWS ALB IngressAWS ALB Ingress

Why pick each one

Choose Contour if…

  • Released under the Apache-2.0 license
  • Kubernetes-ready with Helm charts available
  • Active community (3.9k GitHub stars)
  • Written in HTML
Contour details

Choose HAProxy Kubernetes Ingress if…

  • Released under the Apache-2.0 license
  • Kubernetes-ready with Helm charts available
  • Written in Go
  • Tiny footprint — runs in 256 MB RAM
HAProxy Kubernetes Ingress details

Frequently asked questions

Is Contour or HAProxy Kubernetes Ingress better?

Neither is universally better. Contour has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.

Are Contour and HAProxy Kubernetes Ingress free and open-source?

Yes. Contour is licensed under Apache-2.0 and HAProxy Kubernetes Ingress under Apache-2.0. Both can be self-hosted at no software cost.

Can I run Contour and HAProxy Kubernetes Ingress with Docker?

Contour: check the project docs for container support. HAProxy Kubernetes Ingress: check the project docs for container support.

Related comparisons