Emissary-ingress vs Kong Gateway
A side-by-side comparison of two self-hosted reverse proxy & gateways options — licensing, setup difficulty, resource needs, and what each one replaces.
| Feature | Emissary-ingress | Kong Gateway |
|---|---|---|
| Deploy effort | Read-the-docs project | Under-an-hour setup |
| Health score | 88 · Excellent | 99 · Excellent |
| Category | Reverse Proxy & Gateways | Reverse Proxy & Gateways |
| License | Apache-2.0 | Apache-2.0 |
| Language | Python | Lua |
| Setup difficulty | Medium | Medium |
| Min. RAM | 512 MB | 512 MB |
| Deployment | kubernetes, helm | docker, kubernetes, helm |
| GitHub stars | ★ 4,523 | ★ 44,186 |
| First released | 2017 | 2015 |
| Replaces | AWS API Gateway, Kong | AWS API Gateway, Apigee |
What are Emissary-ingress and Kong Gateway?
Emissary-ingress
Emissary-ingress is an open-source, Kubernetes-native API gateway and ingress controller built on Envoy Proxy. It manages traffic, rate limiting, and authentication for cluster workloads.
- Kubernetes-native API gateway
- Envoy data plane
- Rate limiting and auth
- Declarative configuration
Kong Gateway
Kong Gateway is an open-source API gateway built on Nginx that manages, secures, and observes API traffic with a rich plugin ecosystem. It scales from single nodes to large clusters.
- Plugin-driven API management
- Rate limiting and auth
- Kubernetes ingress controller
- Declarative config
Emissary-ingress vs Kong Gateway: key differences
Emissary-ingress is written in Python, while Kong Gateway is built with Lua. Kong Gateway is the more established project (first released 2015), while Emissary-ingress arrived in 2017. Kong Gateway has the considerably larger community, at 44,186 GitHub stars versus 4,523. Kong Gateway lists first-class Docker deployment; Emissary-ingress does not.
Why pick each one
Choose Emissary-ingress if…
- Released under the Apache-2.0 license
- Kubernetes-ready with Helm charts available
- Active community (4.5k GitHub stars)
- Written in Python
Choose Kong Gateway if…
- Rich plugin ecosystem
- Scales to clusters
- Built on proven Nginx
Watch out for
- Postgres typically required
- Steep configuration curve
- Some plugins enterprise-only
Frequently asked questions
Is Emissary-ingress or Kong Gateway better?
Neither is universally better. Kong Gateway has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are Emissary-ingress and Kong Gateway free and open-source?
Yes. Emissary-ingress is licensed under Apache-2.0 and Kong Gateway under Apache-2.0. Both can be self-hosted at no software cost.
Can I run Emissary-ingress and Kong Gateway with Docker?
Emissary-ingress: check the project docs for container support. Kong Gateway: yes.