A · leads
floci
96.4
31,872 stars · MIT
DevOps
floci leads by 4.1 · narrow
A · leads
96.4
31,872 stars · MIT
B
92.3
26,788 stars · MIT
floci versus jenkins is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Java. The composite score is 96.4 for floci and 92.3 for jenkins.
floci has 31,872 GitHub stars to jenkins's 26,788, a gap of 5,084 (1.19×). Forks are 3,521 for floci and 9,837 for jenkins. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 89 versus 100.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 215 for floci (0.007 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 84 and 34; activity scores are 100 and 100.
Both floci and jenkins are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both floci (31,872 stars) and jenkins (26,788 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, jenkins is open source.
The lead is split. floci is furthest ahead on issue health (84 to 34), while jenkins is furthest ahead on fork community (100 to 89). Choose the dimension a rollout cannot compromise on.
floci finishes ahead at 96.4 against jenkins at 92.3, a 4.1 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 | jenkins |
|---|---|---|
| GitHub stars | 31,872 | 26,788 |
| Forks | 3,521 | 9,837 |
| Open issues | 215 | 3,618 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 89 | 100 |
| Issue health | 84 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.4 | 92.3 |
Light, fluffy, and always free - The AWS Local Emulator alternative
Jenkins automation server
floci has more GitHub stars: 31,872 versus 26,788 for jenkins. The gap is 5,084 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both floci and jenkins 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. jenkins 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 96.4 and jenkins scores 92.3. This page calls that a narrow lead for floci.