A · leads
floci
97.9
31,872 stars · MIT
DevOps
floci leads by 4.6 · narrow
A · leads
97.9
31,872 stars · MIT
B
93.3
12,622 stars · Apache-2.0
floci versus infracost 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; infracost is written mainly in Go. The composite score is 97.9 for floci and 93.3 for infracost.
floci has 31,872 GitHub stars to infracost's 12,622, a gap of 19,250 (2.53×). Forks are 3,521 for floci and 702 for infracost. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 80.
Push history: floci was last pushed on 17 November 2026 (0 days ago), and infracost was last pushed on 16 November 2026 (1 day ago). Open issues stand at 215 for floci (0.007 per star) and 4 for infracost (0.000 per star). Issue-health scores are 84 and 96; 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. infracost 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 infracost. This is a procurement signal, not legal advice.
In DevOps, both floci (31,872 stars) and infracost (12,622 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, infracost is open source.
The lead is split. floci is furthest ahead on fork community (100 to 80), while infracost is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
floci finishes ahead at 97.9 against infracost at 93.3, a 4.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 | infracost |
|---|---|---|
| GitHub stars | 31,872 | 12,622 |
| Forks | 3,521 | 702 |
| Open issues | 215 | 4 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 93.3 |
Light, fluffy, and always free - The AWS Local Emulator alternative
Cloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!
floci has more GitHub stars: 31,872 versus 12,622 for infracost. The gap is 19,250 stars.
floci was pushed more recently: 17 November 2026 versus 16 November 2026 for infracost. That is 1 days apart.
Yes. This catalog marks both floci and infracost 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. infracost 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 infracost scores 93.3. This page calls that a narrow lead for floci.