A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 8.4 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
90.7
16,362 stars · MIT
Coolify versus task 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; task is written mainly in Go. The composite score is 99.1 for Coolify and 90.7 for task.
Coolify has 66,171 GitHub stars to task's 16,362, a gap of 49,809 (4.04×). Forks are 6,003 for Coolify and 945 for task. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 79.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and task was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 195 for task (0.012 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. task 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 task. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and task (16,362 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, task 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 21 points (100 vs 79), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against task at 90.7, a 8.4 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 | task |
|---|---|---|
| GitHub stars | 66,171 | 16,362 |
| Forks | 6,003 | 945 |
| Open issues | 149 | 195 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 90.7 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
A fast, cross-platform build tool inspired by Make, designed for modern workflows.
Coolify has more GitHub stars: 66,171 versus 16,362 for task. The gap is 49,809 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and task 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. task 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 task scores 90.7. This page calls that a clear lead for Coolify.