Apache APISIX vs AWS API Gateway: Self-Hosted vs Managed (2026)
By API7.ai Team
Last updated: June 2026
Apache APISIX and AWS API Gateway take opposite approaches to API management: one is a self-hosted, open-source gateway you run anywhere, the other a fully managed serverless service inside AWS. This guide compares architecture, pricing, performance, extensibility, and vendor lock-in so you can pick the right fit.
Apache APISIX is a self-hosted, open-source gateway (NGINX + etcd, 100+ plugins) that runs on any cloud with no per-request fees and no lock-in. AWS API Gateway is a fully managed, serverless service that removes all operations but runs only on AWS and bills per request. The choice comes down to control and portability versus zero-ops convenience.
- Multi-cloud, hybrid, or high sustained traffic: Apache APISIX
- Serverless apps on AWS with zero ops: AWS API Gateway
- APISIX performance with enterprise support: API7 Enterprise
Apache APISIX vs AWS API Gateway at a glance
Apache APISIX wins on portability, extensibility, and fixed cost at scale; AWS API Gateway wins on zero operations and tight AWS integration for serverless workloads.
| Dimension | Apache APISIX | AWS API Gateway |
|---|---|---|
| Model | Self-hosted, open source | Fully managed, serverless |
| Core & runtime | NGINX/OpenResty (LuaJIT) + etcd | AWS-managed service (no servers) |
| Deployment | ✓ Any cloud, on-prem, edge, Kubernetes | AWS only |
| Pricing | Infrastructure cost only (fixed per node) | Usage-based, per request + data transfer |
| Plugins / extensibility | 100+ built-in plugins; 6 languages | — No plugins; Lambda + mapping templates |
| Vendor lock-in | ✓ None (Apache 2.0) | High (IAM, Cognito, Lambda, CloudWatch) |
| License | Apache-2.0 (free) | Proprietary managed service |
What is Apache APISIX?
Apache APISIX is a self-hosted, open-source API gateway built on NGINX and etcd, with 100+ built-in plugins and full portability across cloud, on-prem, and edge.
Apache APISIX is a self-hosted, open-source (Apache 2.0) API gateway built on NGINX and etcd. It offers 100+ built-in plugins for authentication, traffic control, and observability, runs on any cloud, on-prem, or edge, and is governed by the Apache Software Foundation.
Architecture
NGINX/OpenResty (LuaJIT) + etcd
License
Apache-2.0 (open source)
Best for
Portable, self-hosted API gateway
Pros
- No vendor lock-in — runs identically on AWS, GCP, Azure, on-prem, and edge
- 100+ built-in plugins; custom plugins in 6 languages, hot-loaded
- APISIX self-reports ~18,000 QPS/core at <0.2 ms added latency
- Fixed infrastructure cost regardless of request volume
Cons
- You provision and operate APISIX nodes plus an etcd cluster
- No managed SLA unless you adopt a commercial distribution
- Requires platform-engineering ownership of upgrades and tuning
- Advanced enterprise features (e.g. FIPS, RBAC, support) come via API7 Enterprise
What is AWS API Gateway?
AWS API Gateway is a fully managed, serverless service for REST, HTTP, and WebSocket APIs, tightly integrated with Lambda, IAM, Cognito, and CloudWatch inside AWS.
AWS API Gateway is a fully managed, serverless service for creating, publishing, and securing REST, HTTP, and WebSocket APIs at any scale. It is tightly integrated with Lambda, IAM, Cognito, and CloudWatch, and removes all infrastructure management for teams already on AWS.
Architecture
Managed serverless (no servers)
Pricing
Usage-based, per request
Best for
Serverless apps on AWS
Pros
- Zero infrastructure to manage — AWS handles scaling, patching, and HA
- Deep AWS integration: Lambda, IAM, Cognito, CloudWatch, X-Ray, WAF
- Pay-as-you-go with a 12-month free tier for new accounts
- Native WebSocket APIs and canary release deployments
Cons
- AWS only — no multi-cloud, hybrid, or on-prem deployment
- Per-request pricing grows with traffic (REST from $3.50/M, US East)
- No plugin system; custom logic needs Lambda and mapping templates
- Default 10,000 RPS Region throttle and 29 s integration timeout
Architecture: self-hosted gateway vs managed service
APISIX is a stateless data plane you operate on your own infrastructure with etcd for configuration; AWS API Gateway is a managed service where AWS owns the entire stack.
Apache APISIX is built on NGINX and LuaJIT, with configuration stored in etcd and pushed to a stateless data plane that hot-reloads changes via an etcd watch. You provision APISIX nodes and an etcd cluster, which means more to operate, but in exchange you keep all logs and data on your own infrastructure and can deploy the exact same gateway on any cloud, on-prem, or at the edge.
AWS API Gateway is fully managed and serverless. AWS runs the data plane, handles scaling and patching, and exposes REST, HTTP, and WebSocket API types. There is nothing to provision, but the gateway lives entirely within AWS — configuration uses AWS formats (CloudFormation/CDK), authorization leans on IAM and Cognito, and observability flows through CloudWatch and X-Ray.
Pricing: usage-based vs fixed infrastructure
AWS API Gateway bills per request, so cost scales with traffic; APISIX is free and open source, so you pay only for the infrastructure you run regardless of volume.
AWS API Gateway is usage-based. Per the AWS pricing page (US East), HTTP APIs start at $1.00 per million requests (dropping to $0.90 above 300 million), REST APIs start at $3.50 per million (tiered down to $2.38), and WebSocket APIs are $1.00 per million messages plus $0.25 per million connection-minutes — all before data transfer. A 12-month free tier covers one million requests per month for new accounts.
Apache APISIX is free under Apache 2.0; your only cost is the compute and etcd you run, which is fixed regardless of request volume. As a result, self-hosting tends to become more economical at sustained high traffic, while managed pricing is often easier to justify at low or spiky volumes. Model both against your real traffic — the crossover depends entirely on your cloud compute costs.
Performance and scaling
APISIX self-reports ~18,000 QPS per core at under 0.2 ms added latency and scales by adding nodes; AWS API Gateway auto-scales but applies a default Region throttle and a 29-second integration timeout.
In its own published benchmarks, Apache APISIX reports single-core throughput of about 18,000 QPS with under 0.2 ms of added latency. You scale horizontally by adding nodes, with no provider-imposed throttle, and configuration changes propagate through etcd in milliseconds. Treat any vendor benchmark as a starting point and measure your own workload.
AWS API Gateway scales automatically, but it does not publish a comparable per-core latency figure, and it applies documented limits: a default account throttle of 10,000 requests per second per Region (adjustable; 2,500 RPS in some Regions) and an integration timeout that defaults to 29 seconds. For latency-sensitive or very high-throughput APIs you have less control over the underlying gateway; for moderate or bursty traffic, automatic scaling is a real convenience.
Apache APISIX vs AWS API Gateway: feature comparison
Across architecture, deployment, pricing, protocols, extensibility, and security, the two trade off control and portability against managed simplicity.
| Feature | Apache APISIX | AWS API Gateway |
|---|---|---|
| Architecture | Self-hosted gateway built on NGINX and etcd (LuaJIT); stateless data plane, config hot-reloaded via etcd watch | Fully managed serverless service; REST, HTTP, and WebSocket API types; no infrastructure to run |
| Deployment | Any cloud, on-prem, hybrid, or edge; bare metal to Kubernetes; identical config everywhere | AWS Regions only; cannot run on GCP, Azure, or on-prem |
| Pricing | Free, open source; you pay only for the compute and etcd you run — fixed regardless of request volume | Usage-based: REST $3.50/M (tiered to $2.38), HTTP $1.00/M (then $0.90), WebSocket $1.00/M msgs + $0.25/M conn-min, plus data transfer (US East) |
| Performance | APISIX self-reports ~18,000 QPS/core at <0.2 ms added latency; scale out by adding nodes; no provider throttle | Auto-scales, but default account throttle is 10,000 RPS per Region (adjustable; 2,500 in some Regions) and integration timeout defaults to 29 s |
| Protocols | HTTP/1.1, HTTP/2, gRPC, gRPC transcoding, WebSocket, TCP/UDP, MQTT, Dubbo | REST, HTTP, and WebSocket APIs; no native gRPC or TCP/UDP proxy |
| Plugins & extensibility | 100+ built-in plugins; custom plugins in Lua, Go, Python, Java, JavaScript, Wasm — hot-loaded, no restart | No plugin system; custom logic via Lambda authorizers, mapping templates, and AWS service integrations |
| Security & auth | JWT, OAuth2/OIDC, key-auth, HMAC, mTLS, CORS, and external authz (e.g. OPA) as plugins | IAM, Amazon Cognito user pools, Lambda authorizers, API keys, resource policies, AWS WAF |
| Observability | Prometheus, OpenTelemetry, SkyWalking, and other open integrations; pick your own stack | CloudWatch metrics and logs, AWS X-Ray tracing; within the AWS ecosystem |
| Service discovery | Kubernetes, Consul, Nacos, Eureka, and DNS-based discovery built in | AWS-native targets (Lambda, VPC Link to ELB/NLB, HTTP endpoints) |
| Configuration | Admin REST API, dashboard, and declarative YAML; etcd-backed, GitOps-friendly | Console, CloudFormation, CDK, Terraform; deployment- and stage-based versioning |
| Operations | You run and upgrade APISIX nodes and etcd; full control over logs, data, and topology | Zero infrastructure management; AWS handles scaling, patching, and HA; less low-level visibility |
| License | Apache-2.0; governed by the Apache Software Foundation | Proprietary AWS managed service |
When to choose Apache APISIX vs AWS API Gateway
Choose Apache APISIX for portability, extensibility, and fixed cost at scale; choose AWS API Gateway for zero-ops serverless APIs that live inside AWS.
Choose Apache APISIX if you…
- Need multi-cloud, hybrid, or on-prem deployment and data sovereignty
- Run sustained high traffic where per-request pricing gets expensive
- Want a rich plugin ecosystem and custom extensions in many languages
- Want zero vendor lock-in under an Apache 2.0 license
Choose AWS API Gateway if you…
- Build serverless apps on AWS with Lambda backends
- Want zero infrastructure management and automatic scaling
- Have low, moderate, or spiky traffic where usage-based pricing fits
- Are committed to the AWS ecosystem (IAM, Cognito, CloudWatch)
Bottom line: if your architecture is all-in on AWS and you want zero operations, AWS API Gateway is the simpler path; if you need multi-cloud portability, a deep plugin ecosystem, or fixed cost at high traffic, Apache APISIX is the stronger fit. Teams that want APISIX's performance and portability with a visual dashboard, fine-grained RBAC, and commercial support can run API7 Enterprise, which is built on Apache APISIX.
Frequently asked questions
Related comparisons
AWS API Gateway vs Kong · Apache APISIX vs Envoy · AWS API Gateway vs Azure API Management · All gateway comparisons
Ready to get started?
For more information about full API lifecycle management, please contact us to Meet with our API Experts.
