A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 13.2 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
85.9
4,737 stars · Apache-2.0
Coolify versus werf 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; werf is written mainly in Go. The composite score is 99.1 for Coolify and 85.9 for werf.
Coolify has 66,171 GitHub stars to werf's 4,737, a gap of 61,434 (13.97×). Forks are 6,003 for Coolify and 241 for werf. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 63.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and werf was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 10 for werf (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both Coolify and werf are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and werf (4,737 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, werf is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 37 points (100 vs 63), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against werf at 85.9, a 13.2 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 | werf |
|---|---|---|
| GitHub stars | 66,171 | 4,737 |
| Forks | 6,003 | 241 |
| Open issues | 149 | 10 |
| Adoption | 100 | 76 |
| Activity | 100 | 100 |
| Community | 100 | 63 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 85.9 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
Coolify has more GitHub stars: 66,171 versus 4,737 for werf. The gap is 61,434 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and werf 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. werf 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and werf scores 85.9. This page calls that a clear lead for Coolify.