A
git-sim
75.0
4,695 stars · GPL-2.0
DevOps
Grafana leads by 16.2 · decisive
A
75.0
4,695 stars · GPL-2.0
B · leads
91.2
77,962 stars · AGPL-3.0
git-sim versus Grafana is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. git-sim is written mainly in Python; Grafana is written mainly in TypeScript. The composite score is 75.0 for git-sim and 91.2 for Grafana.
Grafana has 77,962 GitHub stars to git-sim's 4,695, a gap of 73,267 (16.61×). Forks are 127 for git-sim and 14,988 for Grafana. On the log scale used inside this pair, adoption is 75 versus 100, and the fork community is 50 versus 100.
Push history: git-sim was last pushed on 12 October 2026 (35 days ago), and Grafana was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for git-sim (0.002 per star) and 3,310 for Grafana (0.042 per star). Issue-health scores are 96 and 70; activity scores are 78 and 100.
git-sim is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for git-sim and 52 for Grafana. This is a procurement signal, not legal advice.
In DevOps, both git-sim (4,695 stars) and Grafana (77,962 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: git-sim is open source, Grafana is freemium.
The lead is split. git-sim is furthest ahead on issue health (96 to 70), while Grafana is furthest ahead on fork community (100 to 50). Choose the dimension a rollout cannot compromise on.
Grafana finishes ahead at 91.2 against git-sim at 75.0, a 16.2 point decisive 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 | git-sim | Grafana |
|---|---|---|
| GitHub stars | 4,695 | 77,962 |
| Forks | 127 | 14,988 |
| Open issues | 11 | 3,310 |
| Adoption | 75 | 100 |
| Activity | 78 | 100 |
| Community | 50 | 100 |
| Issue health | 96 | 70 |
| License | 64 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 75.0 | 91.2 |
The visual layer for Git in your own repos: simulate, record, replay, audit, and share entire Git workflows, wherever you or your agents run them.
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.
Grafana has more GitHub stars: 77,962 versus 4,695 for git-sim. The gap is 73,267 stars.
Grafana was pushed more recently: 17 November 2026 versus 12 October 2026 for git-sim. That is 35 days apart.
Yes. This catalog marks both git-sim and Grafana as self-hostable. Confirm each project's deploy docs before you plan a migration.
git-sim is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Grafana scores 91.2 and git-sim scores 75.0. This page calls that a decisive lead for Grafana.