A · leads
floci
97.9
31,872 stars · MIT
DevOps
floci leads by 1.5 · narrow
A · leads
97.9
31,872 stars · MIT
B
96.4
30,249 stars · Apache-2.0
floci versus kestra 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 97.9 for floci and 96.4 for kestra.
floci has 31,872 GitHub stars to kestra's 30,249, a gap of 1,623 (1.05×). Forks are 3,521 for floci and 3,538 for kestra. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 100.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 215 for floci (0.007 per star) and 651 for kestra (0.022 per star). Issue-health scores are 84 and 70; 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. kestra 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 kestra. This is a procurement signal, not legal advice.
In DevOps, both floci (31,872 stars) and kestra (30,249 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, kestra is open source.
The lead is split. floci is furthest ahead on issue health (84 to 70), while kestra is furthest ahead on fork community (100 to 100). Choose the dimension a rollout cannot compromise on.
floci finishes ahead at 97.9 against kestra at 96.4, a 1.5 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 | kestra |
|---|---|---|
| GitHub stars | 31,872 | 30,249 |
| Forks | 3,521 | 3,538 |
| Open issues | 215 | 651 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 96.4 |
Light, fluffy, and always free - The AWS Local Emulator alternative
Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.
floci has more GitHub stars: 31,872 versus 30,249 for kestra. The gap is 1,623 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both floci and kestra 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. kestra 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.
floci scores 97.9 and kestra scores 96.4. This page calls that a narrow lead for floci.