A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 16.3 · decisive
A · leads
99.1
66,171 stars · Apache-2.0
B
82.8
11,723 stars · AGPL-3.0
Coolify versus pyroscope 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; pyroscope is written mainly in Go. The composite score is 99.1 for Coolify and 82.8 for pyroscope.
Coolify has 66,171 GitHub stars to pyroscope's 11,723, a gap of 54,448 (5.64×). Forks are 6,003 for Coolify and 838 for pyroscope. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 77.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and pyroscope was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 376 for pyroscope (0.032 per star). Issue-health scores are 96 and 70; 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. pyroscope is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for Coolify and 52 for pyroscope. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and pyroscope (11,723 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, pyroscope is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against pyroscope at 82.8, a 16.3 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 | pyroscope |
|---|---|---|
| GitHub stars | 66,171 | 11,723 |
| Forks | 6,003 | 838 |
| Open issues | 149 | 376 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 77 |
| Issue health | 96 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 82.8 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Continuous Profiling Platform. Debug performance issues down to a single line of code
Coolify has more GitHub stars: 66,171 versus 11,723 for pyroscope. The gap is 54,448 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and pyroscope 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. pyroscope is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and pyroscope scores 82.8. This page calls that a decisive lead for Coolify.