A · level
Grafana
91.2
77,962 stars · AGPL-3.0
DevOps
Too close to call · 91.2 to 91.6
A · level
91.2
77,962 stars · AGPL-3.0
B · level
91.6
30,249 stars · Apache-2.0
Grafana versus kestra 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; kestra is written mainly in Java. The composite score is 91.2 for Grafana and 91.6 for kestra.
Grafana has 77,962 GitHub stars to kestra's 30,249, a gap of 47,713 (2.58×). Forks are 14,988 for Grafana and 3,538 for kestra. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 85.
Push history: Grafana was last pushed on 17 November 2026 (0 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,310 for Grafana (0.042 per star) and 651 for kestra (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. kestra 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 52 for Grafana and 96 for kestra. This is a procurement signal, not legal advice.
In DevOps, both Grafana (77,962 stars) and kestra (30,249 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, kestra is open source.
The lead is split. Grafana is furthest ahead on fork community (100 to 85), while kestra is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: Grafana 91.2, kestra 91.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | kestra |
|---|---|---|
| GitHub stars | 77,962 | 30,249 |
| Forks | 14,988 | 3,538 |
| Open issues | 3,310 | 651 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 70 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 91.6 |
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.
Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.
Grafana has more GitHub stars: 77,962 versus 30,249 for kestra. The gap is 47,713 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Grafana and kestra 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. kestra 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.
Neither tool clears a one-point margin. Grafana scores 91.2 and kestra scores 91.6.