Envoy 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.

Not the right match-up?
FeatureEnvoyIngress-NGINX
CategoryReverse Proxy & GatewaysReverse Proxy & Gateways
LicenseApache-2.0Apache-2.0
LanguageC++Go
Setup difficultyHardMedium
Min. RAM512 MB256 MB
Deploymentdocker, kubernetes, binarykubernetes, helm
GitHub stars★ 28,735★ 19,485
First released20162016
ReplacesNginx, HAProxyAWS ALB Ingress

Why pick each one

Choose Envoy if…

  • Released under the Apache-2.0 license
  • First-class Docker support for quick deployment
  • Kubernetes-ready with Helm charts available
  • Mature project with 28.7k GitHub stars
Envoy details

Choose Ingress-NGINX if…

  • Released under the Apache-2.0 license
  • Kubernetes-ready with Helm charts available
  • Mature project with 19.5k GitHub stars
  • Written in Go
Ingress-NGINX details

Frequently asked questions

Is Envoy or Ingress-NGINX better?

Neither is universally better. Envoy has the larger community, while Ingress-NGINX is simpler to set up (medium difficulty). Choose based on the comparison table above and your own setup.

Are Envoy and Ingress-NGINX free and open-source?

Yes. Envoy 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 Envoy and Ingress-NGINX with Docker?

Envoy: yes. Ingress-NGINX: check the project docs for container support.

Related comparisons