A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 5.9 · narrow
A · leads
96.5
59,134 stars · MIT
B
90.6
12,622 stars · Apache-2.0
Gitea versus infracost 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 90.6 for infracost.
Gitea has 59,134 GitHub stars to infracost's 12,622, a gap of 46,512 (4.68×). Forks are 7,414 for Gitea and 702 for infracost. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 74.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and infracost was last pushed on 16 November 2026 (1 day ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 4 for infracost (0.000 per star). Issue-health scores are 70 and 96; 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. infracost 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 96 for Gitea and 96 for infracost. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and infracost (12,622 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, infracost is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 74), while infracost is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against infracost at 90.6, a 5.9 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 | Gitea | infracost |
|---|---|---|
| GitHub stars | 59,134 | 12,622 |
| Forks | 7,414 | 702 |
| Open issues | 2,172 | 4 |
| Adoption | 100 | 86 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 90.6 |
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.
Cloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!
Gitea has more GitHub stars: 59,134 versus 12,622 for infracost. The gap is 46,512 stars.
Gitea was pushed more recently: 17 November 2026 versus 16 November 2026 for infracost. That is 1 days apart.
Yes. This catalog marks both Gitea and infracost 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. infracost 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.
Gitea scores 96.5 and infracost scores 90.6. This page calls that a narrow lead for Gitea.