A
Grafana
91.2
77,962 stars · AGPL-3.0
DevOps
kong leads by 3.5 · narrow
A
91.2
77,962 stars · AGPL-3.0
B · leads
94.7
44,388 stars · Apache-2.0
Grafana versus kong 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; kong is written mainly in Lua. The composite score is 91.2 for Grafana and 94.7 for kong.
Grafana has 77,962 GitHub stars to kong's 44,388, a gap of 33,574 (1.76×). Forks are 14,988 for Grafana and 5,242 for kong. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 89.
Push history: Grafana was last pushed on 17 November 2026 (0 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,310 for Grafana (0.042 per star) and 233 for kong (0.005 per star). Issue-health scores are 70 and 84; 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. kong 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 kong. This is a procurement signal, not legal advice.
In DevOps, both Grafana (77,962 stars) and kong (44,388 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, kong is open source.
The lead is split. Grafana is furthest ahead on fork community (100 to 89), while kong is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
kong finishes ahead at 94.7 against Grafana at 91.2, a 3.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 | kong |
|---|---|---|
| GitHub stars | 77,962 | 44,388 |
| Forks | 14,988 | 5,242 |
| Open issues | 3,310 | 233 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 70 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 94.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.
🦍 The API and AI Gateway
Grafana has more GitHub stars: 77,962 versus 44,388 for kong. The gap is 33,574 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Grafana and kong 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. kong 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.
kong scores 94.7 and Grafana scores 91.2. This page calls that a narrow lead for kong.