A
apisix
93.9
17,333 stars · Apache-2.0
DevOps
floci leads by 4.0 · narrow
A
93.9
17,333 stars · Apache-2.0
B · leads
97.9
31,872 stars · MIT
apisix versus floci 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; floci is written mainly in Java. The composite score is 93.9 for apisix and 97.9 for floci.
floci has 31,872 GitHub stars to apisix's 17,333, a gap of 14,539 (1.84×). Forks are 3,004 for apisix and 3,521 for floci. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 98 versus 100.
Push history: apisix was last pushed on 13 November 2026 (4 days ago), and floci was last pushed on 17 November 2026 (0 days ago). Open issues stand at 230 for apisix (0.013 per star) and 215 for floci (0.007 per star). Issue-health scores are 84 and 84; 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. floci is listed as MIT, 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. License scores in this pair are 96 for apisix and 96 for floci. This is a procurement signal, not legal advice.
In DevOps, both apisix (17,333 stars) and floci (31,872 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, floci is open source.
floci is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 8 points (92 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
floci finishes ahead at 97.9 against apisix at 93.9, a 4.0 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 | floci |
|---|---|---|
| GitHub stars | 17,333 | 31,872 |
| Forks | 3,004 | 3,521 |
| Open issues | 230 | 215 |
| Adoption | 94 | 100 |
| Activity | 92 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.9 | 97.9 |
The Cloud-Native API Gateway and AI Gateway
Light, fluffy, and always free - The AWS Local Emulator alternative
floci has more GitHub stars: 31,872 versus 17,333 for apisix. The gap is 14,539 stars.
floci 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 floci 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. floci is listed as MIT, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
floci scores 97.9 and apisix scores 93.9. This page calls that a narrow lead for floci.