A · leads
Grafana
91.2
77,962 stars · AGPL-3.0
DevOps
Grafana leads by 4.5 · narrow
A · leads
91.2
77,962 stars · AGPL-3.0
B
86.7
9,929 stars · MIT
Grafana versus terragrunt is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Grafana is written mainly in TypeScript; terragrunt is written mainly in Go. The composite score is 91.2 for Grafana and 86.7 for terragrunt.
Grafana has 77,962 GitHub stars to terragrunt's 9,929, a gap of 68,033 (7.85×). Forks are 14,988 for Grafana and 1,251 for terragrunt. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 74.
Push history: Grafana 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 3,310 for Grafana (0.042 per star) and 216 for terragrunt (0.022 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
Grafana is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for Grafana and 96 for terragrunt. This is a procurement signal, not legal advice.
In DevOps, both Grafana (77,962 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: Grafana is freemium, terragrunt is open source.
The lead is split. Grafana is furthest ahead on fork community (100 to 74), while terragrunt is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Grafana finishes ahead at 91.2 against terragrunt at 86.7, a 4.5 point narrow 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 | Grafana | terragrunt |
|---|---|---|
| GitHub stars | 77,962 | 9,929 |
| Forks | 14,988 | 1,251 |
| Open issues | 3,310 | 216 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 70 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 86.7 |
Grafana is the dashboard and visualization layer most teams pair with Prometheus and other metric stores. The open-source server can be self-hosted; Grafana Labs sells a cloud.
Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.
Grafana has more GitHub stars: 77,962 versus 9,929 for terragrunt. The gap is 68,033 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Grafana and terragrunt as self-hostable. Confirm each project's deploy docs before you plan a migration.
Grafana is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.
Grafana scores 91.2 and terragrunt scores 86.7. This page calls that a narrow lead for Grafana.