# Forgejo vs Gitea

> Forgejo and Gitea compared: the 2022 fork and 2024 hard fork, governance, GPL vs MIT licence, release and LTS schedules, Actions compatibility, federation, paid editions and upgrade paths. Each claim cited to the project’s own pages.

- **Source:** https://githubalternatives.com/forgejo-vs-gitea
- **Verified against vendor pages:** 2026-11-09
- **Published:** 2026-11-09
- **Part of:** https://githubalternatives.com/ (45 GitHub alternatives, compared)

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. This is a directory page, not a verdict.

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 | Gitea |
|---|---|---|
| Governance | Defined by its contributors, under the umbrella of the non-profit Codeberg e.V., which holds the domains | CommitGo, Inc. leads development and sells commercial products. A six-seat Technical Oversight Committee: three elected, three from the company |
| Licence | GPL-3.0-or-later from v9.0; v8.0 and earlier are MIT | MIT |
| Latest release | v17.0.1, 26 October 2026. LTS: v15.0.11, supported to 15 July 2027 | v28.3.0, 1 November 2026. The 1. prefix was dropped at 28.0.0 |
| Release schedule | A stable release every quarter. The first release each year is LTS, supported for one year and three months | A major release about every three to four months. No LTS line documented |
| Actions | Forgejo Actions with Forgejo Runner. Not designed to be compatible with GitHub Actions; workflows should work with minimal changes | Gitea Actions with Gitea Runner. Designed to be compatible with GitHub Actions, with documented gaps |
| Federation | ActivityPub federation in development and marked experimental; federated stars done | No federation work documented by Gitea |
| Paid edition | None from the project. Third-party providers listed on a professional-services board | Gitea Enterprise, $9.50 per user per month (list price $19), one-year commitment |
| Hosted service | Codeberg, a separate non-profit host that runs Forgejo, for free-software projects | Gitea Cloud, a managed single-tenant service. gitea.com is free for open source |

## Editions and hosting side by side

| Tier | Forgejo | Gitea |
|---|---|---|
| Self-hosted, free | Forgejo, GPL-3.0-or-later, no limits | Gitea, MIT, no limits. Audit logging is in the open-source release from 28.0.0 |
| Self-hosted, paid | None from the project | Gitea Enterprise, $9.50 per user per month: SAML SSO, dependency scanning, IP allowlist, mandatory 2FA, branch protection inheritance, SLA support |
| Managed | Codeberg 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.

## Related pages

- [Gitea vs GitLab](https://githubalternatives.com/gitea-vs-gitlab): The lightweight forge and the all-in-one platform, side by side for teams that want to run their own.
- [Codeberg vs GitHub](https://githubalternatives.com/codeberg-vs-github): A non-profit forge for free software next to the largest commercial Git host, side by side.
- [Forgejo vs GitLab](https://githubalternatives.com/forgejo-vs-gitlab): A small community forge and an all-in-one company platform, side by side for teams that run their own server.
- [Codeberg vs GitLab](https://githubalternatives.com/codeberg-vs-gitlab): A non-profit host for free software and a company’s hosted DevSecOps platform, side by side.
- [Gogs vs Gitea](https://githubalternatives.com/gogs-vs-gitea): The original lightweight Go forge and the community fork that grew out of it, side by side.
- [GitLab vs GitHub](https://githubalternatives.com/gitlab-vs-github): The two platforms most teams compare first, side by side on price, limits, hosting model and licence.
- [GitLab alternatives](https://githubalternatives.com/gitlab-alternatives): Every platform that can replace GitLab, grouped by how it is run, with the free-tier limits that send people looking.
- [GitHub vs Bitbucket](https://githubalternatives.com/github-vs-bitbucket): Two hosted Git platforms with close per-seat prices and very different ecosystems, side by side.
- [Bitbucket alternatives](https://githubalternatives.com/bitbucket-alternatives): Every platform that can replace Bitbucket, including the self-hosted options now that Data Center is closed to new customers.
- [Azure DevOps vs GitHub](https://githubalternatives.com/azure-devops-vs-github): Two Microsoft developer platforms with different pricing, CI models and roadmaps, side by side.
- [Perforce vs Git](https://githubalternatives.com/perforce-vs-git): A distributed open-source tool and a centralised commercial server, compared on the problems that make teams choose between them.
- [Bitbucket vs GitLab](https://githubalternatives.com/bitbucket-vs-gitlab): Atlassian’s Git host and GitLab side by side: seat prices, CI allowances, Jira, single sign-on and running it yourself.
- [Git hosting pricing compared](https://githubalternatives.com/git-hosting-pricing): What every Git hosting platform charges, per user or per plan, with its free tier, in one place.
- [Hosting for Subversion, Perforce and large binary files](https://githubalternatives.com/svn-perforce-hosting): Every platform in the directory that hosts Subversion, runs Perforce, or handles large binary files with exclusive locking.

## Sources

Checked on 2026-11-09.

- [Gitea blog: Open source sustainment and the future of Gitea (24 October 2022)](https://blog.gitea.com/open-source-sustainment/)
- [Forgejo: Hello Forgejo (15 December 2022)](https://forgejo.org/2022-12-15-hello-forgejo/)
- [Forgejo: Forking forward (February 2024)](https://forgejo.org/2024-02-forking-forward/)
- [Forgejo: licence change to GPL v3+ (August 2024)](https://forgejo.org/2024-08-gpl/)
- [Forgejo FAQ](https://forgejo.org/faq/)
- [Forgejo releases](https://forgejo.org/releases/)
- [Forgejo release schedule](https://forgejo.org/docs/latest/admin/release-schedule/)
- [Forgejo upgrade guide](https://forgejo.org/docs/latest/admin/upgrade/)
- [Forgejo Actions and GitHub Actions](https://forgejo.org/docs/latest/user/actions/github-actions/)
- [Forgejo federation roadmap](https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md)
- [Forgejo licence file](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/LICENSE)
- [Why Gitea (CommitGo)](https://about.gitea.com/about/whygitea/)
- [Gitea community governance](https://github.com/go-gitea/gitea/blob/main/docs/community-governance.md)
- [Gitea release management](https://github.com/go-gitea/gitea/blob/main/docs/release-management.md)
- [Gitea 28.0.0 release notes](https://blog.gitea.com/release-of-28.0.0/)
- [Gitea Actions compared with GitHub Actions](https://docs.gitea.com/usage/actions/comparison/)
- [Gitea pricing](https://about.gitea.com/pricing/)
- [Gitea Enterprise](https://about.gitea.com/products/gitea-enterprise/)
- [Gitea licence file](https://github.com/go-gitea/gitea/blob/main/LICENSE)
