Apache APISIX vs Emissary-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?
FeatureApache APISIXEmissary-ingress
CategoryReverse Proxy & GatewaysReverse Proxy & Gateways
LicenseApache-2.0Apache-2.0
LanguageLuaPython
Setup difficultyMediumMedium
Min. RAM512 MB512 MB
Deploymentdocker, kubernetes, helmkubernetes, helm
GitHub stars★ 16,968★ 4,518
First released20192017
ReplacesKong, AWS API GatewayAWS API Gateway, Kong

Why pick each one

Choose Apache APISIX if…

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

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
Emissary-ingress details

Frequently asked questions

Is Apache APISIX or Emissary-ingress better?

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

Are Apache APISIX and Emissary-ingress free and open-source?

Yes. Apache APISIX is licensed under Apache-2.0 and Emissary-ingress under Apache-2.0. Both can be self-hosted at no software cost.

Can I run Apache APISIX and Emissary-ingress with Docker?

Apache APISIX: yes. Emissary-ingress: check the project docs for container support.

Related comparisons