A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 11.5 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
87.6
5,330 stars · BSD-3-Clause
Coolify versus tsuru 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; tsuru is written mainly in Go. The composite score is 99.1 for Coolify and 87.6 for tsuru.
Coolify has 66,171 GitHub stars to tsuru's 5,330, a gap of 60,841 (12.41×). Forks are 6,003 for Coolify and 554 for tsuru. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 73.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and tsuru was last pushed on 14 November 2026 (3 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 24 for tsuru (0.005 per star). Issue-health scores are 96 and 96; 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. tsuru is listed as BSD-3-Clause, 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 tsuru. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and tsuru (5,330 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, tsuru 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 27 points (100 vs 73), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against tsuru at 87.6, a 11.5 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 | tsuru |
|---|---|---|
| GitHub stars | 66,171 | 5,330 |
| Forks | 6,003 | 554 |
| Open issues | 149 | 24 |
| Adoption | 100 | 77 |
| Activity | 100 | 100 |
| Community | 100 | 73 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 87.6 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Open source and extensible Platform as a Service (PaaS).
Coolify has more GitHub stars: 66,171 versus 5,330 for tsuru. The gap is 60,841 stars.
Coolify was pushed more recently: 17 November 2026 versus 14 November 2026 for tsuru. That is 3 days apart.
Yes. This catalog marks both Coolify and tsuru 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. tsuru is listed as BSD-3-Clause, 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 tsuru scores 87.6. This page calls that a clear lead for Coolify.