A · leads
floci
97.9
31,872 stars · MIT
DevOps
floci leads by 7.4 · clear
A · leads
97.9
31,872 stars · MIT
B
90.5
14,420 stars · MIT
floci versus semaphore 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; semaphore is written mainly in Go. The composite score is 97.9 for floci and 90.5 for semaphore.
floci has 31,872 GitHub stars to semaphore's 14,420, a gap of 17,452 (2.21×). Forks are 3,521 for floci and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 88.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 215 for floci (0.007 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
Both floci and semaphore 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 semaphore (14,420 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, semaphore is open source.
floci is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
floci finishes ahead at 97.9 against semaphore at 90.5, a 7.4 point clear 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 | semaphore |
|---|---|---|
| GitHub stars | 31,872 | 14,420 |
| Forks | 3,521 | 1,353 |
| Open issues | 215 | 1,075 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 90.5 |
Light, fluffy, and always free - The AWS Local Emulator alternative
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
floci has more GitHub stars: 31,872 versus 14,420 for semaphore. The gap is 17,452 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both floci and semaphore 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. semaphore 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 semaphore scores 90.5. This page calls that a clear lead for floci.