GitHub alternatives Forgejo vs Gitea

~ git remote -v

Forgejo vs Gitea

Two self-hosted forges from one codebase, compared on what has diverged since the fork.

Verified Published

Independent comparison. Not affiliated with the Forgejo project, Codeberg e.V., Gitea Ltd, CommitGo, Inc., GitHub, Inc. or Microsoft Corporation. Where the two projects describe each other, this page attributes the claim to its source. Every figure below was read from the vendor's own page on 9 November 2026 and is linked in the sources list.

Forgejo began as a fork of Gitea in 2022 and became a hard fork in 2024. Both are lightweight Go forges with repositories, pull requests, issues, packages and built-in Actions CI, and both run on a small server. For the first year the difference was mostly governance. Since the hard fork, licence, release schedules, features and upgrade paths have diverged too.

The two projects disagree about parts of their shared history. This page cites each project’s own statements for its own position and leaves out claims that one project makes about the other where the other’s pages say something different.

At a glance

Forgejo and Gitea at a glance. Read from each vendor's pricing page on 9 November 2026. Scroll sideways on small screens.
ForgejoGitea
GovernanceDefined by its contributors, under the umbrella of the non-profit Codeberg e.V., which holds the domainsCommitGo, Inc. leads development and sells commercial products. A six-seat Technical Oversight Committee: three elected, three from the company
LicenceGPL-3.0-or-later from v9.0; v8.0 and earlier are MITMIT
Latest releasev17.0.1, 26 October 2026. LTS: v15.0.11, supported to 15 July 2027v28.3.0, 1 November 2026. The 1. prefix was dropped at 28.0.0
Release scheduleA stable release every quarter. The first release each year is LTS, supported for one year and three monthsA major release about every three to four months. No LTS line documented
ActionsForgejo Actions with Forgejo Runner. Not designed to be compatible with GitHub Actions; workflows should work with minimal changesGitea Actions with Gitea Runner. Designed to be compatible with GitHub Actions, with documented gaps
FederationActivityPub federation in development and marked experimental; federated stars doneNo federation work documented by Gitea
Paid editionNone from the project. Third-party providers listed on a professional-services boardGitea Enterprise, $9.50 per user per month (list price $19), one-year commitment
Hosted serviceCodeberg, a separate non-profit host that runs Forgejo, for free-software projectsGitea Cloud, a managed single-tenant service. gitea.com is free for open source

Editions and hosting side by side

What each project offers, from free self-hosting to managed hosting. Prices in USD as published.
TierForgejoGitea
Self-hosted, freeForgejo, GPL-3.0-or-later, no limitsGitea, MIT, no limits. Audit logging is in the open-source release from 28.0.0
Self-hosted, paidNone from the projectGitea Enterprise, $9.50 per user per month: SAML SSO, dependency scanning, IP allowlist, mandatory 2FA, branch protection inheritance, SLA support
ManagedCodeberg for free-software projects, run by Codeberg e.V.Gitea Cloud, single-tenant in a cloud region you choose; pricing on the vendor page

How the fork happened

On 24 October 2022, Gitea’s Technical Oversight Committee announced a company, Gitea Limited, to fund the project through support, hosting, an enterprise version and training. The post said Gitea would remain open source and a community project, and that the founder had transferred his domains and trademarks to the company.

Forgejo announced itself on 15 December 2022. In its own words, it started in reaction to control of Gitea being taken away from the community by the new company without prior consultation, after an open letter went unanswered. Codeberg moved to Forgejo.

At first Forgejo tracked Gitea closely as a soft fork. On 15 February 2024 it announced a hard fork, saying the two projects’ governance, development models and goals had diverged. Forgejo said it would eventually stop being a drop-in replacement, while trying to keep its API compatible with Gitea’s.

Governance and licence

Forgejo states that its governance is defined collectively by its contributors, under the umbrella of Codeberg e.V., which holds its domains. It has registered no trademarks and is funded by volunteers, grants, donations and employers who delegate staff. From v9.0, released in 2024, Forgejo is licensed GPL-3.0-or-later. Earlier versions stay MIT.

Gitea now names CommitGo, Inc. as the company that leads development and provides its commercial products. Its governance document gives the Technical Oversight Committee six seats, three elected and three appointed from the company. Gitea remains MIT licensed, which allows proprietary forks and redistribution.

The licence is the practical difference for anyone building on the code. GPL requires published modifications when you distribute the software. MIT does not.

Releases and support

Forgejo publishes a stable release every quarter on a fixed schedule. Each stable release has three months of support plus two weeks. The first release of each year is a long-term support release with a year and three months of critical and security fixes. As of this check, v17.0.1 is current and v15.0.11 is the LTS.

Gitea aims for a major release every three to four months and dropped the historical 1. prefix at 28.0.0 in September 2026, so its version numbers jumped from 1.27 to 28. Gitea documents no LTS line. Gitea Enterprise follows its own rolling release policy.

Actions CI

Both include Actions-style CI with a separate runner program: Forgejo Runner and Gitea Runner. Both read workflow files that look like GitHub Actions, and the two projects word compatibility differently.

Forgejo says its Actions are designed to be familiar to GitHub Actions users but not designed to be compatible, and that workflows should work with minimal changes. It lists gaps such as ignored permissions and continue-on-error keys. Gitea says Gitea Actions is designed to be compatible with GitHub Actions and lists its differences, such as missing problem matchers and annotations. Test your own workflows on either before you commit.

Switching between them

Forgejo documents upgrades from Gitea up to and including Gitea 1.22, in two steps: first to Forgejo v10.0, then to any later Forgejo. Upgrades from Gitea 1.23 and later, including the 28.x line, are not documented as supported. Gitea’s upgrade documentation does not cover moving from Forgejo.

If you run Gitea today and might move to Forgejo later, check that path before you upgrade Gitea past 1.22. Both forges can also migrate repositories, issues and pull requests from a running instance through their migration tools, which avoids a database upgrade altogether.

What usually decides it

Teams that want a non-profit, contributor-governed project with a copyleft licence and a yearly LTS release tend to pick Forgejo. Teams that want MIT licensing, a vendor that sells support and an enterprise edition, or SAML through a paid plan tend to pick Gitea. For a small team that only needs Git hosting, CI and issues, both do the job on the same modest hardware.

Frequently asked questions

Is Forgejo a fork of Gitea?

Yes. Forgejo forked from Gitea in 2022 and announced a hard fork on 15 February 2024. It no longer tracks Gitea’s code and will eventually stop being a drop-in replacement, though it aims to keep its API compatible.

What licence do Forgejo and Gitea use?

Gitea is MIT. Forgejo is GPL-3.0-or-later from v9.0; Forgejo v8.0 and earlier remain MIT.

Can I upgrade from Gitea to Forgejo?

Forgejo documents upgrades from Gitea up to version 1.22, first to Forgejo v10.0 and then to any later release. Upgrades from Gitea 1.23 or later are not documented as supported.

Do Forgejo and Gitea run GitHub Actions workflows?

Mostly. Both have Actions CI with workflow files modelled on GitHub Actions. Gitea says it is designed to be compatible, with listed gaps. Forgejo says workflows should work with minimal changes but is not designed to be fully compatible.

Which one does Codeberg use?

Codeberg runs Forgejo. Codeberg e.V. is also the non-profit that hosts the Forgejo project’s domains.

Sources

Checked on 9 November 2026. Prices and limits change without notice. Each link goes to the page the figure came from.

  1. Gitea blog: Open source sustainment and the future of Gitea (24 October 2022)blog.gitea.com
  2. Forgejo: Hello Forgejo (15 December 2022)forgejo.org
  3. Forgejo: Forking forward (February 2024)forgejo.org
  4. Forgejo: licence change to GPL v3+ (August 2024)forgejo.org
  5. Forgejo FAQforgejo.org
  6. Forgejo releasesforgejo.org
  7. Forgejo release scheduleforgejo.org
  8. Forgejo upgrade guideforgejo.org
  9. Forgejo Actions and GitHub Actionsforgejo.org
  10. Forgejo federation roadmapcodeberg.org
  11. Forgejo licence filecodeberg.org
  12. Why Gitea (CommitGo)about.gitea.com
  13. Gitea community governancegithub.com
  14. Gitea release managementgithub.com
  15. Gitea 28.0.0 release notesblog.gitea.com
  16. Gitea Actions compared with GitHub Actionsdocs.gitea.com
  17. Gitea pricingabout.gitea.com
  18. Gitea Enterpriseabout.gitea.com
  19. Gitea licence filegithub.com

All 45 GitHub alternatives, compared