grafanavsissue-status
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| grafana | issue-status | |
|---|---|---|
| Score | 90/100 | 47/100 |
| Rank in category | #1 of 104 in Monitoring & observability | #31 of 51 in Monitoring & observability |
| GitHub stars | 77 569 | 429 |
| Stars, last 30 days | +695 | — |
| Stable releases, 12 months | 53 | 0 |
| Latest release | v13.2.5 · 27 Oct 2026 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | No |
| License | AGPL-3.0 | MIT |
| Main language | Typescript | Typescript |
Which one should you pick?
grafana scores 90/100 against 47/100 for issue-status, so it is the safer default.
grafana ships more often: 53 stable releases in the past year, against 0 for issue-status.
If you want the quickest setup, issue-status is easier to run; grafana needs more configuration.
grafana is growing faster right now (+695 stars in 30 days).
grafana details →issue-status details →
Swap a project
Keep grafana, compare it with
Keep issue-status, compare it with