The resource and governance divide in Git hosting

Minimal footprints versus monolithic stacks

The resource gap between lightweight forges and monolithic platforms defines the current self-hosting market. Gitea and Forgejo exist as lean, single-binary options for developers. These tools run on minimal hardware that most modern servers handle without effort. You can deploy a Gitea instance on a cheap VPS for very little cost. Most users find that these tools idle at only 40 to 80 MB of RAM. This efficiency makes them ideal for users with strict hardware constraints. The single binary nature of Gitea and Forgejo allows them to run on a five dollar monthly VPS, while a comfortable GitLab CE installation requires forty to eighty dollars per month for a machine with enough resources. GitLab CE is a Ruby on Rails monolith that bundles PostgreSQL, Redis, and Gitaly. It requires at least 4 GB of memory and 1 GB of swap just to install. For a production environment with 200 repositories, users need at least 8 GB of RAM and 4 CPU cores. I find the GitLab requirement for a dedicated machine quite excessive for small teams. While Gitea coexists with other services like Caddy or pgAdmin on a single small VPS, GitLab CE forces you into a much higher monthly spend.

CI/CD and the feature gap

Gitea 1.26.0 and Forgejo 15.0 changed the competitive landscape in April 2026. Gitea 1.26.0 brought workflow concurrency groups and a frontend rewrite using HTMX and Tailwind. This release included 1,528 merged pull requests. Forgejo 15.0, an LTS release, added reusable workflow expansion for Forgejo Actions and improved runner registration. Forgejo 15.0 also added OpenID Connect support. Both tools provide compatibility with GitHub Actions workflows. This means you can move your existing workflows to Gitea or Forgejo with minimal changes to the file paths. GitLab uses its own CI syntax, which requires a total rewrite of your automation. GitLab leads in CI/CD depth with features like Auto DevOps and deployment tracking. However, Gitea supports over 20 package types, including Conda, Chef, and Vagrant, which GitLab CE lacks. Gitea 1.26.0 also introduced Terraform state hosting. Regarding security, GitLab CE has a limitation in its free tier. The community edition does not support mandatory merge request approvals. To enforce code reviews, you must purchase the Premium tier. Gitea allows required reviewers through its branch protection rules in the free version. This makes Gitea a better option for teams that prioritize enforced security without a monthly per-user fee.

Choosing between forks and platforms

Teams often face a choice between the governance of Forgejo and the maturity of GitLab. Forgejo operates under a non-profit charter and does not require contributors to sign copyright assignment agreements. Gitea operates as a for-profit company, Gitea Ltd. You can evaluate the governance of these projects by looking at their underlying organizational structures. Forgejo has 232 contributors, while Gitea has 153. Many users choose Forgejo because it prioritizes open-source values over commercial interests. This preference stems from the 2022 transfer of the Gitea trademark to a for-profit entity. Migration between these systems involves different levels of difficulty. GitLab can import Gitea projects, but it only imports a subset of items. Importing users from Gitea to GitLab can be difficult because the Gitea API does not always provide clear information about blocked users. You also have to handle SSH key issues and potential duplicate fingerprints manually. Will the experimental federation in Forgejo eventually attract enough users to challenge the dominance of centralized platforms?