A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 12.3 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
86.8
8,208 stars · Apache-2.0
Coolify versus woodpecker 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; woodpecker is written mainly in Go. The composite score is 99.1 for Coolify and 86.8 for woodpecker.
Coolify has 66,171 GitHub stars to woodpecker's 8,208, a gap of 57,963 (8.06×). Forks are 6,003 for Coolify and 750 for woodpecker. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 76.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and woodpecker was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 376 for woodpecker (0.046 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
Both Coolify and woodpecker 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 woodpecker (8,208 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, woodpecker 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 issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against woodpecker at 86.8, a 12.3 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 | woodpecker |
|---|---|---|
| GitHub stars | 66,171 | 8,208 |
| Forks | 6,003 | 750 |
| Open issues | 149 | 376 |
| Adoption | 100 | 81 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 86.8 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.
Coolify has more GitHub stars: 66,171 versus 8,208 for woodpecker. The gap is 57,963 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and woodpecker 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. woodpecker 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 woodpecker scores 86.8. This page calls that a clear lead for Coolify.