A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 10.9 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
88.2
9,929 stars · MIT
Coolify versus terragrunt 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; terragrunt is written mainly in Go. The composite score is 99.1 for Coolify and 88.2 for terragrunt.
Coolify has 66,171 GitHub stars to terragrunt's 9,929, a gap of 56,242 (6.66×). Forks are 6,003 for Coolify and 1,251 for terragrunt. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 82.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and terragrunt was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 216 for terragrunt (0.022 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. terragrunt 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 terragrunt. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and terragrunt (9,929 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, terragrunt 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 issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against terragrunt at 88.2, a 10.9 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 | terragrunt |
|---|---|---|
| GitHub stars | 66,171 | 9,929 |
| Forks | 6,003 | 1,251 |
| Open issues | 149 | 216 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 88.2 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.
Coolify has more GitHub stars: 66,171 versus 9,929 for terragrunt. The gap is 56,242 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and terragrunt 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. terragrunt 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 terragrunt scores 88.2. This page calls that a clear lead for Coolify.