# Forgejo vs GitLab

> Forgejo and self-managed GitLab compared on licence, governance, hardware needs, CI runners, features, release support and GitLab-to-Forgejo migration. Every claim cited and dated.

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

Not affiliated with the Forgejo project, Codeberg e.V., GitLab Inc., GitHub, Inc. or Microsoft Corporation. This is a directory page, not a verdict.

Forgejo and GitLab both run on your own server and both include Git hosting, merge or pull requests, issues, package registries and built-in CI. They differ in who controls them, which licence applies, how much hardware they need and how much they include beyond the repository.

This page compares self-managed GitLab with self-hosted Forgejo. It is a directory entry, not a verdict. Each claim comes from the project’s own documentation or source code.

## At a glance

| | GitLab | Forgejo |
|---|---|---|
| Owner | GitLab Inc. | Defined by its contributors, under the umbrella of the non-profit Codeberg e.V., which holds the domains |
| Licence | Open core: code outside the ee/ directories is MIT Expat; ee/ is under the GitLab Enterprise Edition licence | GPL-3.0-or-later from v9.0; v8.0 and earlier are MIT |
| Hardware | 8 vCPU and 16 GB of memory is the single-node baseline; it can run with at least 8 GB of memory | No published minimum. The install guide says SQLite is good enough for at least 10 users |
| Databases | PostgreSQL only | PostgreSQL, MySQL, MariaDB, SQLite |
| CI/CD | GitLab CI/CD in .gitlab-ci.yml, jobs run by GitLab Runner | Forgejo Actions in .forgejo/workflows, jobs run by Forgejo Runner |
| Release schedule | Minor release monthly on the third Thursday. Security fixes for the current and two previous minor releases. No LTS documented | Stable release every quarter, about three months of support. One LTS release a year, about 15 months of support |
| Latest release | 19.5 is the current stable release | v17.0.1, 26 October 2026. LTS: v15.0.11, supported to 15 July 2027 |
| Paid edition | Premium, $29 per user per month billed annually. Ultimate on custom pricing | None |

## Self-managed editions side by side

| Tier | GitLab | Forgejo |
|---|---|---|
| Free | Free, $0. Bring your own storage and runners. The 5-user limit applies only to GitLab.com | Free, no paid edition. GPL-3.0-or-later, no user or repository limits |
| Paid | Premium, $29 per user per month billed annually | No paid edition |
| Top | Ultimate, custom pricing. Contact sales | No paid edition |

## Licence and governance

GitLab is open core. Its repository licence file puts everything under the ee/ directories under the GitLab Enterprise Edition licence, and everything else under MIT Expat. GitLab publishes a read-only mirror with the proprietary code removed, which it calls GitLab FOSS. GitLab says the Enterprise Edition package can run with Free features without a paid subscription.

Forgejo is GPL-3.0-or-later from v9.0. Versions up to v8.0 stay MIT. Forgejo says its governance is defined collectively by its contributors, and that its domains are in the custody of the non-profit Codeberg e.V. It names volunteers, grants, donations and employers who delegate staff as its funding.

GitLab Inc. sets GitLab’s roadmap and sells its paid tiers. Forgejo has no paid edition from the project.

## Hardware and operations

GitLab documents 8 vCPU and 16 GB of memory as the baseline for a single-node install. Where memory is tight, it says GitLab can run with at least 8 GB. Application nodes need at least 40 GB of disk, and PostgreSQL is the only supported database. GitLab 19.x needs PostgreSQL 17 or later.

Forgejo’s documentation publishes no CPU or memory minimum. It ships as one binary per CPU architecture and supports PostgreSQL 14 or later, MySQL 8.4 or later, MariaDB 10.6 or later and SQLite. The binary install guide says SQLite is good enough for at least 10 users.

## CI/CD

Both products leave job execution to a separate runner program. GitLab CI/CD reads .gitlab-ci.yml and sends jobs to GitLab Runner. On self-managed GitLab you bring your own runners.

Forgejo Actions reads YAML workflows from .forgejo/workflows, and falls back to .github/workflows if that directory is missing. Jobs go to Forgejo Runner, which Forgejo installs and configures separately. Forgejo says Actions is designed to be familiar to GitHub Actions users but not designed to be compatible, and that workflows usually need minor changes. Its admin guide warns that the runner performs remote code execution and points to a page on securing it.

Neither reads the other’s CI format, so moving between them means rewriting pipelines.

## What GitLab documents that Forgejo does not

GitLab documents SAST scanning in every tier, including Free, with advanced SAST and vulnerability management in Ultimate. It documents GitLab Pages static site hosting in every tier, and SAML sign-in for self-managed instances in every tier.

Forgejo’s documentation has no section on built-in security scanning or static site hosting. Its authentication pages cover LDAP and PAM and include a page on OpenID Connect group mappings; they do not mention SAML. Forgejo does document a package registry with 23 formats, including Container, npm, Maven, PyPI and Cargo, plus project boards, a wiki and code search.

## Moving from GitLab to Forgejo

Forgejo’s migration tool has a GitLab source. Its GitLab downloader reads repository details, topics, milestones, labels, releases, issues, comments, merge requests and reviews. Reactions on issues and merge requests come across; reactions on comments do not, according to a note in the code. Codeberg’s guide, which uses the same Forgejo tool, says an access token is needed to migrate metadata or non-public repositories.

In the other direction, GitLab’s Gitea importer brings repository data, issues, pull requests, milestones and labels. Its documentation does not mention Forgejo. For code only, a mirror push works in either direction.

```sh
git clone --mirror https://gitlab.example.com/group/repo.git
cd repo.git
git remote set-url --push origin https://forgejo.example.com/org/repo.git
git push --mirror
```

## Frequently asked questions

### Is Forgejo lighter than GitLab?

GitLab documents 8 vCPU and 16 GB of memory as its single-node baseline, and at least 8 GB where memory is tight. Forgejo publishes no minimum; its install guide says SQLite alone is good enough for at least 10 users.

### Is Forgejo or GitLab open source?

Forgejo is GPL-3.0-or-later from v9.0, with no proprietary edition. GitLab is open core: code outside its ee/ directories is MIT, and the ee/ code is under the GitLab Enterprise Edition licence.

### Can Forgejo import from GitLab?

Yes. Forgejo’s GitLab migrator reads issues, merge requests, reviews, comments, labels, milestones and releases. You need a GitLab access token to bring metadata or private repositories.

### Does Forgejo have CI like GitLab CI?

Yes. Forgejo Actions runs YAML workflows on a separate Forgejo Runner. The format is modelled on GitHub Actions, not on .gitlab-ci.yml, so GitLab pipelines need rewriting.

### Does Forgejo have a long-term support release?

Yes. The first Forgejo release each year is LTS, with about 15 months of support; v15.0.11 is supported to 15 July 2027. GitLab’s maintenance policy describes no LTS: security fixes go to the current and two previous monthly releases.

## Related pages

- [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.
- [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.
- [Forgejo vs Gitea](https://githubalternatives.com/forgejo-vs-gitea): Two self-hosted forges from one codebase, compared on what has diverged since the fork.
- [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.
- [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.
- [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.
- [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.
- [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-15.

- [GitLab installation requirements](https://docs.gitlab.com/install/requirements/)
- [GitLab maintenance policy](https://docs.gitlab.com/policy/maintenance/)
- [GitLab licence file](https://gitlab.com/gitlab-org/gitlab/-/blob/master/LICENSE)
- [GitLab Community Edition](https://about.gitlab.com/gitlab-community-edition/)
- [GitLab pricing](https://about.gitlab.com/pricing/)
- [GitLab SAST](https://docs.gitlab.com/user/application_security/sast/)
- [GitLab Pages](https://docs.gitlab.com/user/project/pages/)
- [GitLab SAML for self-managed](https://docs.gitlab.com/integration/saml/)
- [GitLab: migrate from Gitea](https://docs.gitlab.com/user/import/gitea/)
- [Forgejo FAQ](https://forgejo.org/faq/)
- [Forgejo releases](https://forgejo.org/releases/)
- [Forgejo release schedule](https://forgejo.org/docs/latest/admin/release-schedule/)
- [Forgejo database preparation](https://forgejo.org/docs/latest/admin/installation/database-preparation/)
- [Forgejo installation from binary](https://forgejo.org/docs/latest/admin/installation/binary/)
- [Forgejo Actions overview](https://forgejo.org/docs/latest/user/actions/overview/)
- [Forgejo Actions administrator guide](https://forgejo.org/docs/latest/admin/actions/)
- [Forgejo authentication](https://forgejo.org/docs/latest/admin/setup/authentication/)
- [Forgejo documentation index](https://forgejo.org/docs/latest/)
- [Forgejo GitLab migrator source](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/services/migrations/gitlab.go)
- [Codeberg: migrating repositories](https://docs.codeberg.org/advanced/migrating-repos/)
