A · leads
floci
97.9
31,872 stars · MIT
DevOps
floci leads by 31.0 · decisive
A · leads
97.9
31,872 stars · MIT
B
66.9
17,080 stars · license n/a
floci versus kubesphere 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; kubesphere is written mainly in Go. The composite score is 97.9 for floci and 66.9 for kubesphere.
floci has 31,872 GitHub stars to kubesphere's 17,080, a gap of 14,792 (1.87×). Forks are 3,521 for floci and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 97.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and kubesphere was last pushed on 15 July 2026 (125 days ago). Open issues stand at 215 for floci (0.007 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 84 and 70; activity scores are 100 and 36.
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. kubesphere 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 floci and 30 for kubesphere. This is a procurement signal, not legal advice.
Only floci is marked self-hostable here (31,872 stars, deploy score 100). kubesphere is not (17,080 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: floci is open source, kubesphere is unpriced in this catalog.
floci is ahead on every scored dimension that is not level. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is fork community at 3 points (100 vs 97).
floci finishes ahead at 97.9 against kubesphere at 66.9, a 31.0 point decisive 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 | kubesphere |
|---|---|---|
| GitHub stars | 31,872 | 17,080 |
| Forks | 3,521 | 2,752 |
| Open issues | 215 | 350 |
| Adoption | 100 | 94 |
| Activity | 100 | 36 |
| Community | 100 | 97 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.9 | 66.9 |
Light, fluffy, and always free - The AWS Local Emulator alternative
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
floci has more GitHub stars: 31,872 versus 17,080 for kubesphere. The gap is 14,792 stars.
floci was pushed more recently: 17 November 2026 versus 15 July 2026 for kubesphere. That is 125 days apart.
Only floci is marked self-hostable. kubesphere is not.
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. kubesphere 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.
floci scores 97.9 and kubesphere scores 66.9. This page calls that a decisive lead for floci.