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
6,504 stars · MIT
Coolify versus server-survival 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; server-survival is written mainly in JavaScript. The composite score is 99.1 for Coolify and 86.8 for server-survival.
Coolify has 66,171 GitHub stars to server-survival's 6,504, a gap of 59,667 (10.17×). Forks are 6,003 for Coolify and 720 for server-survival. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 76.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and server-survival was last pushed on 04 November 2026 (13 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 21 for server-survival (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
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. server-survival 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 server-survival. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and server-survival (6,504 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, server-survival is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 24 points (100 vs 76), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against server-survival 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 | server-survival |
|---|---|---|
| GitHub stars | 66,171 | 6,504 |
| Forks | 6,003 | 720 |
| Open issues | 149 | 21 |
| Adoption | 100 | 79 |
| Activity | 100 | 92 |
| Community | 100 | 76 |
| Issue health | 96 | 96 |
| 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.
Tower defense game that teaches cloud architecture. Build infrastructure, survive traffic, learn scaling.
Coolify has more GitHub stars: 66,171 versus 6,504 for server-survival. The gap is 59,667 stars.
Coolify was pushed more recently: 17 November 2026 versus 04 November 2026 for server-survival. That is 13 days apart.
Yes. This catalog marks both Coolify and server-survival 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. server-survival 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 99.1 and server-survival scores 86.8. This page calls that a clear lead for Coolify.