A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 18.7 · decisive
A · leads
99.1
66,171 stars · Apache-2.0
B
80.4
12,222 stars · MIT
Coolify versus webhook 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; webhook is written mainly in Go. The composite score is 99.1 for Coolify and 80.4 for webhook.
Coolify has 66,171 GitHub stars to webhook's 12,222, a gap of 53,949 (5.41×). Forks are 6,003 for Coolify and 884 for webhook. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 78.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and webhook was last pushed on 04 September 2026 (74 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 131 for webhook (0.011 per star). Issue-health scores are 96 and 84; activity scores are 100 and 58.
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. webhook 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 webhook. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and webhook (12,222 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, webhook is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 42 points (100 vs 58), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against webhook at 80.4, a 18.7 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 | webhook |
|---|---|---|
| GitHub stars | 66,171 | 12,222 |
| Forks | 6,003 | 884 |
| Open issues | 149 | 131 |
| Adoption | 100 | 85 |
| Activity | 100 | 58 |
| Community | 100 | 78 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 80.4 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
webhook is a lightweight incoming webhook server to run shell commands
Coolify has more GitHub stars: 66,171 versus 12,222 for webhook. The gap is 53,949 stars.
Coolify was pushed more recently: 17 November 2026 versus 04 September 2026 for webhook. That is 74 days apart.
Yes. This catalog marks both Coolify and webhook 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. webhook 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 webhook scores 80.4. This page calls that a decisive lead for Coolify.