Git Hosting

Gitea58.2k★

Gitea is the lightest full-featured Git forge you can self-host. One Go binary gives you repositories, issues, pull requests, code review, wikis, packages, a container registry, and Gitea Actions, which runs GitHub Actions workflows without rewriting them. MIT licensed, no seat limits. Deployment is a binary or a Docker image pointed at a database. SQLite works for small teams, Postgres for anything real, and it runs fine on a $5 a month VPS. Recent releases have been mostly CI work: 1.27 made reusable workflows first-class jobs and added org-wide shared workflows, alongside a large batch of security fixes. Stay current. The paid line is now clearly drawn. Gitea Enterprise runs $19 per user per month, or $9.50 on a one year commitment, and that is where SAML SSO, audit logs, dependency scanning and Kubernetes autoscaling runners live. Solo and small teams self-host the free edition and never think about it. Larger teams with a compliance checklist should price Enterprise against GitLab first. The catch is that SAML SSO is not in the open source build. LDAP and OAuth2 are, and that covers most teams, but if your security team wrote SAML into the requirements you are paying per seat again, which is what you left GitHub to avoid. Forgejo (forgejo/forgejo) is the community fork.

Forgejo0★

Forgejo is a self-hosted Git platform forked from Gitea in 2022 after a governance dispute over the parent project moving to a private company. The fork is run by Codeberg eV, a nonprofit, with a community-controlled governance model. GPLv3 from version 9.0 forward, MIT before that. Feature-wise, it is what Gitea is: repos, issues, pull requests, wiki, releases, package registry (Docker, npm, Maven, container registry, more), and Forgejo Actions, which is a fork of Gitea Actions and accepts GitHub Actions workflow files directly. Single Go binary or Docker container. Runs comfortably on a Raspberry Pi and scales to teams of thousands. Solo developers and small teams: install via Docker Compose, point your DNS at it, done. Larger teams: Forgejo is the safer long-term pick over Gitea because of the governance model. If you are starting fresh in 2026, choose Forgejo first. The catch is mindshare. Gitea has more users, more community plugins, and is what most tutorials reference. Migrating between Gitea and Forgejo is straightforward (database-compatible up through specific versions), so this is not a one-way door. Also worth noting: the source lives on Codeberg, not GitHub. Star counts and issue activity look quiet on GitHub mirrors because the real project is elsewhere.