A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 25.0 · decisive
A · leads
99.1
66,171 stars · Apache-2.0
B
74.1
5,641 stars · license n/a
Coolify versus liquibase 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; liquibase is written mainly in Java. The composite score is 99.1 for Coolify and 74.1 for liquibase.
Coolify has 66,171 GitHub stars to liquibase's 5,641, a gap of 60,530 (11.73×). Forks are 6,003 for Coolify and 1,984 for liquibase. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 87.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and liquibase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 275 for liquibase (0.049 per star). Issue-health scores are 96 and 70; 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. liquibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Coolify and 30 for liquibase. This is a procurement signal, not legal advice.
Only Coolify is marked self-hostable here (66,171 stars, deploy score 100). liquibase is not (5,641 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Coolify is open source, liquibase is unpriced in this catalog.
Coolify is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against liquibase at 74.1, a 25.0 point decisive 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 | liquibase |
|---|---|---|
| GitHub stars | 66,171 | 5,641 |
| Forks | 6,003 | 1,984 |
| Open issues | 149 | 275 |
| Adoption | 100 | 78 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 96 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 99.1 | 74.1 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Main Liquibase Source
Coolify has more GitHub stars: 66,171 versus 5,641 for liquibase. The gap is 60,530 stars.
Both were last pushed on 17 November 2026.
Only Coolify is marked self-hostable. liquibase is not.
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. liquibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and liquibase scores 74.1. This page calls that a decisive lead for Coolify.