Forgejo vs Gitea vs GlitchTip
Forgejo, Gitea, GlitchTip compared on license, free-edition limits, deployment and project health. Change a project below to compare something else.
| Forgejo | Gitea | GlitchTip | |
|---|---|---|---|
| Category | Developer Tools | Developer Tools | Developer Tools |
| License | GNU General Public License v3.0 or laterOpen source (OSI) | MIT LicenseOpen source (OSI) | MIT LicenseOpen source (OSI) |
| Free edition | Not confirmed | Some features paywalled | Not confirmed |
| Deployment | Self-hosted | Self-hosted · Cloud | Self-hosted · Cloud |
| Self-hosting setup | Not assessed | Single container | Needs a database |
| SSO / SAML | Not confirmed | Paid | Not confirmed |
| Role-based access control | Not confirmed | Free | Not confirmed |
| Audit logs | Not confirmed | Paid | Not confirmed |
| Multi-user / teams | Free | Free | Free |
| Backups and restore | Free | Free | Not confirmed |
| API access | Free | Free | Not confirmed |
| Support SLA | Not confirmed | Paid | Paid |
| GitHub stars | – | 58k | – |
| Last release | – | Oct 6, 2026 | – |
| Alternative to | GitHub, GitLab | GitLab, GitHub | Sentry |
In short
- Forgejo is licensed GNU General Public License v3.0 or later (open source (osi)). Free edition: not confirmed.
- Gitea is licensed MIT License (open source (osi)). Free edition: some features paywalled.
- GlitchTip is licensed MIT License (open source (osi)). Free edition: not confirmed.
Each project page lists the official sources behind these answers. Where the official pages do not say, the table shows “Not confirmed”.