HAProxy Ingress vs Higress
HAProxy Ingress
haproxy-ingress.github.io
Higress
higress.ioSide by side
| Figure | HAProxy Ingress | Higress |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 5 |
| Spec score · Kubernetes Ingress Controllers | 7.6 (#13) | 8.6 (#4) |
| Deployment | The controller is installed and configured with a Helm chart, and the instructions require Helm version 3. | A Docker all-in-one deployment exposes the console on port 8001, HTTP gateway on 8080 and HTTPS gateway on 8443. |
| Security | The getting-started guide says HAProxy Ingress uses TLS SNI and the Host header to associate requests with ingress hosts. | Listed protections include prompt-attack detection, sensitive-content identification, data privacy protection, and output-content filtering. |
| Support | The project lists a Kubernetes Slack channel, a users mailing list, and Stack Overflow for community discussion and questions. | The community edition includes community support and documentation; the dedicated commercial edition lists ticket, DingTalk group, and offline support. |
Plans
Higress
- Alibaba Cloud AI Gateway Serverless StandardPriced on request
- Higress CommunityFree
- Higress Community EditionFree
- Alibaba Cloud AI Gateway Serverless EnterprisePriced on request
- Feitian Exclusive EditionPriced on request
In their own words
HAProxy Ingress
HAProxy Ingress is a free, self-hosted controller that configures HAProxy to route external requests to applications in a Kubernetes cluster. It applies changes made in the cluster to HAProxy without requiring a separate update process. The project supports Ingress and Gateway API resources and describes more than 200 configuration options. Gateway API support is partial: the documented implementation covers GatewayClass, Gateway, TCPRoute, and HTTPRoute, but not HTTPRoute filters or resource status updates. Installation uses a Helm chart and requires Helm 3, a running Kubernetes cluster, and administrative privileges in that cluster. Version 0.16 requires Kubernetes 1.21 or newer. Local cluster options named by the project include minikube, kind, k3s, k3d, and colima. It associates requests with ingress hosts using TLS SNI and the Host header. Metrics can be collected with Prometheus and Grafana using Prometheus Operator. The project uses the Apache-2.0 license and lists community channels including Slack, a users mailing list, and Stack Overflow.
Higress
Higress is an open-source API gateway for governing AI services and cloud-native traffic, built on Istio and Envoy. Its AI Gateway provides centralized access to model APIs and MCP servers, with unified routing, protocol conversion, load balancing, and fallback. Higress says it supports more than 100 mainstream large language models. It can convert HTTP to MCP and proxy native MCP services. Traffic controls include token-based quotas and rate limits, API key pool rotation, and consumer authentication. Caching can reuse inference results precisely or semantically to reduce token use and latency for similar or repeated questions. Listed security measures cover prompt attacks, sensitive content, data privacy, and output filtering. The wider API gateway combines traffic, microservice, and security gateway functions with service exposure and API lifecycle management. It supports HTTP, HTTP2, HTTPS, GRPC, GRPCS, TCP, and Dubbo, along with Kubernetes Ingress and Gateway API. Custom Wasm plugins can be written in Go, Rust, or JavaScript, with sandbox isolation and hot updates. The self-hosted Community Edition is free; the site also lists a managed Alibaba Cloud plan billed by actual usage, starting at ¥0.