A · leads
floci
97.9
31,872 stars · MIT
DevOps
floci leads by 6.6 · narrow
A · leads
97.9
31,872 stars · MIT
B
91.3
17,154 stars · MPL-2.0
floci versus wtf 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; wtf is written mainly in Go. The composite score is 97.9 for floci and 91.3 for wtf.
floci has 31,872 GitHub stars to wtf's 17,154, a gap of 14,718 (1.86×). Forks are 3,521 for floci and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 83.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 215 for floci (0.007 per star) and 107 for wtf (0.006 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for floci and 78 for wtf. This is a procurement signal, not legal advice.
In DevOps, both floci (31,872 stars) and wtf (17,154 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, wtf is open source.
floci is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 18 points (96 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
floci finishes ahead at 97.9 against wtf at 91.3, a 6.6 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 | wtf |
|---|---|---|
| GitHub stars | 31,872 | 17,154 |
| Forks | 3,521 | 866 |
| Open issues | 215 | 107 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 84 | 84 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 91.3 |
Light, fluffy, and always free - The AWS Local Emulator alternative
The personal information dashboard for your terminal
floci has more GitHub stars: 31,872 versus 17,154 for wtf. The gap is 14,718 stars.
floci was pushed more recently: 17 November 2026 versus 14 November 2026 for wtf. That is 3 days apart.
Yes. This catalog marks both floci and wtf 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
floci scores 97.9 and wtf scores 91.3. This page calls that a narrow lead for floci.