ForgejovsGitea
Two self-hosted Code Hosting projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Forgejo | Gitea | |
|---|---|---|
| Score | 58/100 | 89/100 |
| Rank in category | #9 of 15 in Code Hosting | #1 of 15 in Code Hosting |
| GitHub stars | — | 58 949 |
| Stars, last 30 days | — | +665 |
| Stable releases, 12 months | 0 | 17 |
| Latest release | — | v28.3.0 · 1 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | GPL-3.0-or-later | MIT |
| Main language | — | Go |
Which one should you pick?
Gitea scores 89/100 against 58/100 for Forgejo, so it is the safer default.
Gitea ships more often: 17 stable releases in the past year, against 0 for Forgejo.
If you want the quickest setup, Forgejo is easier to run; Gitea needs more configuration.
Gitea is growing faster right now (+665 stars in 30 days).
Key differences
- License: Forgejo is GPL-3.0-or-later, Gitea is MIT.
- Platforms only Forgejo lists: Podman.
- Platforms only Gitea lists: Docker, FreeBSD, Kubernetes, macOS and 1 more.
- Features only Forgejo lists: Built-in CI (Forgejo Actions), Code search, Commit signing, Forge federation (ActivityPub) and 7 more.
- Features only Gitea lists: CI/CD (Gitea Actions), Code Review, Container Registry, Git Hosting and 7 more.
- Both offer: Issue Tracking, Package Registry, Webhooks.
Forgejo details →Gitea details →All Code Hosting projects →