Emissary-ingress vs Kong Gateway
Emissary-ingress
emissary-ingress.devKong Gateway
konghq.comSide by side
| Figure | Emissary-ingress | Kong Gateway |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 7 |
| Spec score · API Gateway Software | 7.7 (#17) | 7.8 (#12) |
| Protocol support | Emissary supports gRPC and HTTP/2 routing. | Konnect Plus lists support for REST, HTTP, LLMs, Kafka, WebSockets, gRPC, and GraphQL. |
Plans
Kong Gateway
- Free trialFree
- PlusPriced on request
- EnterprisePriced on request
- Kong Gateway Open SourceFree
- Konnect Free trialFree
- Konnect EnterprisePriced on request
- Konnect PlusPrice not published
In their own words
Emissary-ingress
Emissary-ingress is a free, open-source Kubernetes API gateway, Layer 7 load balancer, and Ingress built on Envoy Proxy. It handles HTTP, HTTPS, HTTP proxy, HTTPS proxy, TCP, TLS, gRPC, and HTTP/3 traffic. Developers can add, remove, merge, or separate services through Kubernetes resources or annotations, and use annotations to control traffic shares for canary deployments. Emissary stores state in Kubernetes rather than requiring a separate database, with Envoy handling routing and proxying. It can check requests through an external authentication service and a third-party rate limit service, and supports request transformation and client certificate validation, including mutual TLS. A diagnostics service helps investigate configuration issues. Emissary can act as an Istio edge proxy and supports Consul service discovery. It is self-hosted on Linux; Helm is the recommended installation method, with Kubernetes YAML also documented. The project is intended for cloud-native organizations where developers operate their services, as well as developers and operators.
Kong Gateway
Kong Gateway has no write-up on Specifiction yet; its figures are above.