A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 9.6 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
89.5
10,527 stars · BSD-3-Clause
Coolify versus healthchecks 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; healthchecks is written mainly in Python. The composite score is 99.1 for Coolify and 89.5 for healthchecks.
Coolify has 66,171 GitHub stars to healthchecks's 10,527, a gap of 55,644 (6.29×). Forks are 6,003 for Coolify and 1,047 for healthchecks. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 80.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and healthchecks was last pushed on 16 November 2026 (1 day ago). Open issues stand at 149 for Coolify (0.002 per star) and 56 for healthchecks (0.005 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. healthchecks is listed as BSD-3-Clause, 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 healthchecks. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and healthchecks (10,527 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, healthchecks 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 fork community at 20 points (100 vs 80), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against healthchecks at 89.5, a 9.6 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 | Coolify | healthchecks |
|---|---|---|
| GitHub stars | 66,171 | 10,527 |
| Forks | 6,003 | 1,047 |
| Open issues | 149 | 56 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 89.5 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Open-source cron job and background task monitoring service, written in Python & Django
Coolify has more GitHub stars: 66,171 versus 10,527 for healthchecks. The gap is 55,644 stars.
Coolify was pushed more recently: 17 November 2026 versus 16 November 2026 for healthchecks. That is 1 days apart.
Yes. This catalog marks both Coolify and healthchecks 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. healthchecks is listed as BSD-3-Clause, 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 healthchecks scores 89.5. This page calls that a clear lead for Coolify.