A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 14.3 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
84.8
5,620 stars · Apache-2.0
Coolify versus uncloud 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; uncloud is written mainly in Go. The composite score is 99.1 for Coolify and 84.8 for uncloud.
Coolify has 66,171 GitHub stars to uncloud's 5,620, a gap of 60,551 (11.77×). Forks are 6,003 for Coolify and 184 for uncloud. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 60.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and uncloud was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 92 for uncloud (0.016 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both Coolify and uncloud 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 uncloud (5,620 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, uncloud 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 fork community at 40 points (100 vs 60), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against uncloud at 84.8, a 14.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 | uncloud |
|---|---|---|
| GitHub stars | 66,171 | 5,620 |
| Forks | 6,003 | 184 |
| Open issues | 149 | 92 |
| Adoption | 100 | 78 |
| Activity | 100 | 100 |
| Community | 100 | 60 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 84.8 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨
Coolify has more GitHub stars: 66,171 versus 5,620 for uncloud. The gap is 60,551 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and uncloud 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. uncloud 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 uncloud scores 84.8. This page calls that a clear lead for Coolify.