A · leads
apisix
93.5
17,333 stars · Apache-2.0
DevOps
apisix leads by 4.9 · narrow
A · leads
93.5
17,333 stars · Apache-2.0
B
88.6
38,560 stars · license n/a
apisix versus dokploy is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. apisix is written mainly in Lua; dokploy is written mainly in TypeScript. The composite score is 93.5 for apisix and 88.6 for dokploy.
dokploy has 38,560 GitHub stars to apisix's 17,333, a gap of 21,227 (2.22×). Forks are 3,004 for apisix and 3,180 for dokploy. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 99 versus 100.
Push history: apisix was last pushed on 13 November 2026 (4 days ago), and dokploy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 230 for apisix (0.013 per star) and 833 for dokploy (0.022 per star). Issue-health scores are 84 and 70; activity scores are 92 and 100.
apisix is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for apisix and 30 for dokploy. This is a procurement signal, not legal advice.
In DevOps, both apisix (17,333 stars) and dokploy (38,560 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: apisix is open source, dokploy is unpriced in this catalog.
The lead is split. apisix is furthest ahead on license flexibility (96 to 30), while dokploy is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
apisix finishes ahead at 93.5 against dokploy at 88.6, a 4.9 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | apisix | dokploy |
|---|---|---|
| GitHub stars | 17,333 | 38,560 |
| Forks | 3,004 | 3,180 |
| Open issues | 230 | 833 |
| Adoption | 92 | 100 |
| Activity | 92 | 100 |
| Community | 99 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 93.5 | 88.6 |
The Cloud-Native API Gateway and AI Gateway
Open Source Alternative to Vercel, Netlify and Heroku.
dokploy has more GitHub stars: 38,560 versus 17,333 for apisix. The gap is 21,227 stars.
dokploy was pushed more recently: 17 November 2026 versus 13 November 2026 for apisix. That is 4 days apart.
Yes. This catalog marks both apisix and dokploy as self-hostable. Confirm each project's deploy docs before you plan a migration.
apisix is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
apisix scores 93.5 and dokploy scores 88.6. This page calls that a narrow lead for apisix.