A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 10.6 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
88.5
17,154 stars · MPL-2.0
Coolify versus wtf 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; wtf is written mainly in Go. The composite score is 99.1 for Coolify and 88.5 for wtf.
Coolify has 66,171 GitHub stars to wtf's 17,154, a gap of 49,017 (3.86×). Forks are 6,003 for Coolify and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 78.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 107 for wtf (0.006 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for Coolify and 78 for wtf. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and wtf (17,154 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, wtf is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is fork community at 22 points (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against wtf at 88.5, a 10.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 | wtf |
|---|---|---|
| GitHub stars | 66,171 | 17,154 |
| Forks | 6,003 | 866 |
| Open issues | 149 | 107 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 96 | 84 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 88.5 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
The personal information dashboard for your terminal
Coolify has more GitHub stars: 66,171 versus 17,154 for wtf. The gap is 49,017 stars.
Coolify was pushed more recently: 17 November 2026 versus 14 November 2026 for wtf. That is 3 days apart.
Yes. This catalog marks both Coolify and wtf 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and wtf scores 88.5. This page calls that a clear lead for Coolify.