apisix-docker
apisix-docker provides Docker containers for Apache APISIX, a dynamic, real-time API Gateway that handles traffic management, load balancing, and service routing. It supports both standalone mode (file-based config) and distributed setup with etcd as configuration center.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | apache/apisix-docker |
| Owner | apache |
| Primary language | Dockerfile |
| License | Apache-2.0 — OSI-approved |
| Stars | 865 |
| Forks | 494 |
| Open issues | 7 |
| Latest release | v1.x (2020-12-01) |
| Last updated | 2026-06-30 |
| Source | https://github.com/apache/apisix-docker |
What apisix-docker is
This repository packages Apache APISIX as Docker images, enabling rapid deployment of an API Gateway with features including dynamic upstream routing, canary releases, circuit breaking, authentication, and observability. Deployment modes include standalone (apisix.yaml) and etcd-backed clustering for production workloads.
Get the apisix-docker source
Clone the repository and explore it locally.
git clone https://github.com/apache/apisix-docker.gitcd apisix-docker# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Decide between standalone mode (file-based, simpler, lower scalability) and etcd mode (distributed, requires additional infrastructure and operational knowledge).
- Allocate ports: default 9080 (proxy), 9443 (HTTPS), 9180 (admin), 2379 (etcd). Verify no conflicts with existing workloads.
- Plan for etcd cluster management if using distributed mode; production deployments should include backup, monitoring, and failover strategies.
- Test configuration reload workflow (`apisix reload`) in staging to ensure zero-downtime updates are viable for your traffic patterns.
- Set up observability early (metrics, logs, tracing) to diagnose routing or plugin issues in production.
When to avoid it — and what to weigh
- Production without operational readiness — APISIX requires etcd or careful standalone configuration. Organizations without experience in distributed systems or Kubernetes should assess operational overhead before adoption.
- Latest release urgency — Latest tagged release (v1.x) is from December 2020. Code may have been pushed recently, but release cadence appears slow; verify if current version meets your requirements.
- Minimal configuration requirements — Setup requires explicit Docker networking, etcd orchestration, or file-based config management. Simple reverse-proxy use cases may be over-engineered for this tool.
- Proprietary security tooling integration — If your stack depends on proprietary or uncommon security integrations (SIEM, HSM, etc.), verify plugin availability before committing.
License & commercial use
Licensed under Apache License 2.0 (Apache-2.0). This is a permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions.
Apache 2.0 permits commercial use, including in proprietary products and services. No commercial license fees or seat restrictions are imposed by the license. However, derivative works or modifications must comply with Apache 2.0 attribution and liability terms. Consult legal review for specific deployment scenarios, though the license itself imposes no operational restrictions.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Default API key (edd1c9f034335f136f87ad84b625c8f1) and admin endpoint are documented in plaintext examples; production must override and restrict access via allow_admin CIDR rules and network policies. etcd communication should be secured (TLS recommended). No mention of built-in RBAC, audit logging, or compliance features in the Docker documentation; verify against your security requirements.
Alternatives to consider
Kong
Established API Gateway with broader plugin ecosystem and commercial support. More mature release cycle but potentially higher operational cost.
Traefik
Lighter-weight reverse proxy with simpler Kubernetes integration (CRDs). Better for smaller deployments; lacks advanced API management features (circuit breaking, canary release).
Envoy Proxy
Lower-level data plane with powerful filtering and routing. Steeper learning curve; typically paired with Istio or Consul for control plane, adding operational complexity.
Build on apisix-docker with DEV.co software developers
Start with apisix-docker standalone mode today. For production deployments or integration with your existing infrastructure, our DevOps team can help you architect etcd clustering, Kubernetes ingress controllers, and observability stack.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
apisix-docker FAQ
Can I run APISIX without etcd?
How do I secure the admin API endpoint?
What is the difference between this repo and the main apisix repo?
Does APISIX support zero-downtime config updates?
Software developers & web developers for hire
From first prototype to production, DEV.co delivers software development services around tools like apisix-docker. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source devops and beyond.
Ready to containerize your API Gateway?
Start with apisix-docker standalone mode today. For production deployments or integration with your existing infrastructure, our DevOps team can help you architect etcd clustering, Kubernetes ingress controllers, and observability stack.