A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 13.7 · clear
A · leads
96.5
59,134 stars · MIT
B
82.8
11,723 stars · AGPL-3.0
Gitea versus pyroscope is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 96.5 for Gitea and 82.8 for pyroscope.
Gitea has 59,134 GitHub stars to pyroscope's 11,723, a gap of 47,411 (5.04×). Forks are 7,414 for Gitea and 838 for pyroscope. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 76.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and pyroscope was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 376 for pyroscope (0.032 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
Gitea 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. pyroscope 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 96 for Gitea and 52 for pyroscope. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and pyroscope (11,723 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: Gitea is open source, pyroscope is open source.
Gitea is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against pyroscope at 82.8, a 13.7 point clear 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 | Gitea | pyroscope |
|---|---|---|
| GitHub stars | 59,134 | 11,723 |
| Forks | 7,414 | 838 |
| Open issues | 2,172 | 376 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 70 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 82.8 |
Gitea is a lightweight self-hosted Git service with issues, pull requests, and actions. It is the usual choice when a team wants a small forge they can run themselves.
Continuous Profiling Platform. Debug performance issues down to a single line of code
Gitea has more GitHub stars: 59,134 versus 11,723 for pyroscope. The gap is 47,411 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and pyroscope as self-hostable. Confirm each project's deploy docs before you plan a migration.
Gitea 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. pyroscope 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.
Gitea scores 96.5 and pyroscope scores 82.8. This page calls that a clear lead for Gitea.