A · leads
Coolify
98.4
66,171 stars · Apache-2.0
DevOps
Coolify leads by 8.2 · clear
A · leads
98.4
66,171 stars · Apache-2.0
B
90.2
26,788 stars · MIT
Coolify versus jenkins 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; jenkins is written mainly in Java. The composite score is 98.4 for Coolify and 90.2 for jenkins.
Coolify has 66,171 GitHub stars to jenkins's 26,788, a gap of 39,383 (2.47×). Forks are 6,003 for Coolify and 9,837 for jenkins. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 95 versus 100.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 96 and 34; 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. jenkins 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 jenkins. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and jenkins (26,788 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, jenkins is open source.
The lead is split. Coolify is furthest ahead on issue health (96 to 34), while jenkins is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.
Coolify finishes ahead at 98.4 against jenkins at 90.2, a 8.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 | jenkins |
|---|---|---|
| GitHub stars | 66,171 | 26,788 |
| Forks | 6,003 | 9,837 |
| Open issues | 149 | 3,618 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 96 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.4 | 90.2 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Jenkins automation server
Coolify has more GitHub stars: 66,171 versus 26,788 for jenkins. The gap is 39,383 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and jenkins 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. jenkins 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 98.4 and jenkins scores 90.2. This page calls that a clear lead for Coolify.