A
cds
84.4
4,848 stars · BSD-3-Clause
DevOps
Coolify leads by 14.7 · clear
A
84.4
4,848 stars · BSD-3-Clause
B · leads
99.1
66,171 stars · Apache-2.0
cds versus Coolify is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cds is written mainly in Go; Coolify is written mainly in PHP. The composite score is 84.4 for cds and 99.1 for Coolify.
Coolify has 66,171 GitHub stars to cds's 4,848, a gap of 61,323 (13.65×). Forks are 459 for cds and 6,003 for Coolify. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 70 versus 100.
Push history: cds was last pushed on 17 November 2026 (0 days ago), and Coolify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 168 for cds (0.035 per star) and 149 for Coolify (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
cds 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. 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. License scores in this pair are 96 for cds and 96 for Coolify. This is a procurement signal, not legal advice.
In DevOps, both cds (4,848 stars) and Coolify (66,171 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: cds is open source, Coolify 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 30 points (70 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against cds at 84.4, a 14.7 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 | cds | Coolify |
|---|---|---|
| GitHub stars | 4,848 | 66,171 |
| Forks | 459 | 6,003 |
| Open issues | 168 | 149 |
| Adoption | 76 | 100 |
| Activity | 100 | 100 |
| Community | 70 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.4 | 99.1 |
Enterprise-Grade Continuous Delivery & DevOps Automation Open Source Platform
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Coolify has more GitHub stars: 66,171 versus 4,848 for cds. The gap is 61,323 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cds and Coolify as self-hostable. Confirm each project's deploy docs before you plan a migration.
cds 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and cds scores 84.4. This page calls that a clear lead for Coolify.