A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 4.3 · narrow
A · leads
99.1
66,171 stars · Apache-2.0
B
94.8
31,872 stars · MIT
Coolify versus floci is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Coolify is written mainly in PHP; floci is written mainly in Java. The composite score is 99.1 for Coolify and 94.8 for floci.
Coolify has 66,171 GitHub stars to floci's 31,872, a gap of 34,299 (2.08×). Forks are 6,003 for Coolify and 3,521 for floci. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 94.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and floci was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 215 for floci (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Coolify 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. 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. License scores in this pair are 96 for Coolify and 96 for floci. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and floci (31,872 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: Coolify is open source, floci is open source.
Coolify 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 12 points (96 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against floci at 94.8, a 4.3 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 | Coolify | floci |
|---|---|---|
| GitHub stars | 66,171 | 31,872 |
| Forks | 6,003 | 3,521 |
| Open issues | 149 | 215 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 94.8 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Light, fluffy, and always free - The AWS Local Emulator alternative
Coolify has more GitHub stars: 66,171 versus 31,872 for floci. The gap is 34,299 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and floci as self-hostable. Confirm each project's deploy docs before you plan a migration.
Coolify 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and floci scores 94.8. This page calls that a narrow lead for Coolify.