A
floci
96.2
31,872 stars · MIT
DevOps
kong leads by 1.7 · narrow
A
96.2
31,872 stars · MIT
B · leads
97.9
44,388 stars · Apache-2.0
floci versus kong is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. floci is written mainly in Java; kong is written mainly in Lua. The composite score is 96.2 for floci and 97.9 for kong.
kong has 44,388 GitHub stars to floci's 31,872, a gap of 12,516 (1.39×). Forks are 3,521 for floci and 5,242 for kong. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 95 versus 100.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 215 for floci (0.007 per star) and 233 for kong (0.005 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. kong 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. License scores in this pair are 96 for floci and 96 for kong. This is a procurement signal, not legal advice.
In DevOps, both floci (31,872 stars) and kong (44,388 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: floci is open source, kong is open source.
kong is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 5 points (95 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
kong finishes ahead at 97.9 against floci at 96.2, a 1.7 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 | floci | kong |
|---|---|---|
| GitHub stars | 31,872 | 44,388 |
| Forks | 3,521 | 5,242 |
| Open issues | 215 | 233 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 97.9 |
Light, fluffy, and always free - The AWS Local Emulator alternative
🦍 The API and AI Gateway
kong has more GitHub stars: 44,388 versus 31,872 for floci. The gap is 12,516 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both floci and kong as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. kong 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kong scores 97.9 and floci scores 96.2. This page calls that a narrow lead for kong.