Apache APISIX is a self-hosted, open-source API gateway governed by the Apache Software Foundation. Built on OpenResty and NGINX with etcd for configuration, it routes client traffic to upstream services and applies authentication, rate limiting, transformations, and observability through plugins. Teams run it as a general API gateway, a Kubernetes Ingress controller, and an LLM proxy.[1][2]
Quick verdict
Apache APISIX is a self-hosted Apache 2.0 API gateway that routes microservice, Kubernetes, and LLM traffic through a plugin model. Operators manage it by Admin API, declarative files, or dashboard, with etcd under the hood. It suits teams wanting gateway control, not teams seeking a managed service.[1][2]
Capabilities
Dynamic routing Routes requests to upstream services with host, path, and method matching, with route changes applied without restarts according to the official getting-started guide.[1][2]
Plugin system Extends gateway behavior through plugins covering authentication, authorization, rate limiting, transformations, canary releases, and logging.[1][2]
Authentication options Supports key authentication, JWT, and OpenID Connect flows so consumer login can delegate to external identity providers.[1][2]
Traffic controls Applies rate limiting, request and response rewriting, and canary routing for staged rollouts.[1][2]
Observability exports Exports metrics and traces for Prometheus, Jaeger, Zipkin, and SkyWalking integrations.[1]
Kubernetes ingress Serves as a Kubernetes Ingress controller with Ingress and Gateway API support for container platforms.[1]
Management surfaces Managed through an Admin API with token authentication, declarative configuration files, Terraform, or a visual dashboard.[1][2]
AI gateway proxying Proxies LLM providers with load balancing, retries, fallbacks, and prompt guards for AI traffic.[1]
Who will love it
Microservice routing Platform teams that want one self-hosted gateway for routing microservice API traffic with plugin-based policy enforcement.[1][2]
Kubernetes ingress Operators standardizing Kubernetes ingress on Gateway API resources while keeping gateway configuration declarative.[1]
LLM traffic governance Teams governing LLM and AI API calls that need provider load balancing with retries and fallbacks.[1][2]
Who should avoid it
etcd dependency Production setups require etcd or a compatible store plus container or Kubernetes know-how, which adds operational overhead compared with managed gateways.[1][2]
Operational learning curve Independent evaluation notes the gateway is configured dynamically rather than through a Spring-style application framework, so teams should budget time to learn routes, upstreams, and plugin semantics.[1][2]
Commercial support is separate Enterprise support and the hardened commercial distribution come from API7.ai rather than the free Apache-licensed software itself.[1]
How people experience it
One inspected independent evaluation report comparing Apache APISIX routing with Spring Cloud Gateway.
1 cited community source. Single-report sample; it supports an attributed experience, not prevalence or satisfaction scores.
Active 3.x line The project publishes an active 3.x release line, with the 3.17 notes describing current gateway capabilities and fixes.[1]
Independent evaluation An independent evaluator found dynamic routing worked without restarts and judged the gateway a credible option next to Spring Cloud Gateway for non-JVM routing.[1]
Compatibility
Questions worth asking
What is a less technical alternative to Apache APISIX?
If APISIX feels too operational, consider a managed API gateway or the commercial API7 Enterprise distribution, which adds a hardened control plane and support on top of the same gateway core. Choose managed when you want to avoid running etcd and the control plane yourself; choose APISIX when you need self-hosted control and Apache 2.0 licensing.[1][2]
Can I use Apache APISIX without writing code?
Partly. Operators can manage routes, upstreams, and plugins through a visual dashboard or declarative files instead of writing Lua code. You still need API and infrastructure concepts such as routes, upstreams, TLS, and etcd, so it is low-code for operators rather than a general no-code builder.[1][2]
How much does Apache APISIX cost per month?
The Apache APISIX software itself is free under Apache 2.0, so there is no per-month license fee for the open-source gateway. Your monthly cost is infrastructure for the gateway and etcd plus operations time; paid support or the commercial API7 distribution is an optional extra with its own quote.[1][2]
Can I self-host Apache APISIX?
Sources and editorial review
Source research. Reviewed on October 7, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
One inspected independent evaluation report comparing Apache APISIX routing with Spring Cloud Gateway. Single-report sample; it supports an attributed experience, not prevalence or satisfaction scores.
- Apache APISIX official homepage
official · Observed October 7, 2026
Official project homepage describing the dynamic API gateway, plugin system, ingress, AI gateway, and observability integrations.
- Apache APISIX getting started guide
official · Observed October 7, 2026
Official quickstart showing Docker-based gateway and etcd setup, Admin API token use, and route creation.
- Release Apache APISIX 3.17.0
official · Observed October 7, 2026 · Published June 15, 2026
Official release notes for the current 3.x gateway line.
- API7 Enterprise versus Apache APISIX
official · Observed October 7, 2026
Vendor comparison describing the free Apache-licensed gateway versus the paid API7 Enterprise distribution and support.
- Evaluating Apache APISIX versus Spring Cloud Gateway
community · Observed October 7, 2026
Independent evaluator testing dynamic routing against Spring Cloud Gateway.