Forgejo

Forgejo is a self-hosted, lightweight Git forge — a community-governed fork of Gitea developed under the umbrella of the Codeberg e.V. nonprofit. It ships as a single ~100 MB Go binary, runs on as little as 512 MB of RAM, and gives you a GitHub-style web UI with pull requests, issues, wiki, packages, ActivityPub-based federation and a GitHub Actions-compatible CI runner — all under GPL-3.0+. We rate Forgejo 91/100 — in 2026, it is the safer long-term bet for self-hosted Git over upstream Gitea, and the right pick for individuals, homelabbers, FOSS communities and small-to-mid teams who want a fast, ethically governed GitHub alternative they fully own.

What is Forgejo?

Forgejo is a soft fork of Gitea that was created in December 2022 after Gitea’s lead maintainer transferred trademark and trademark-adjacent rights to a for-profit company (Gitea Ltd) without prior community consultation. A group of contributors and the team behind Codeberg — the largest free public Forgejo instance — forked the project to keep development under nonprofit, democratic governance. Forgejo now lives at codeberg.org/forgejo/forgejo, is licensed GPL-3.0-or-later, and is stewarded by Codeberg e.V., a German nonprofit association.

The project’s 100th release, Forgejo v15.0, shipped on April 16, 2026, with a new web-based registration flow for Forgejo Runner, repo-scoped access tokens, accessibility improvements, and tighter container linking. The previous LTS line, v11.0, is supported with security backports through July 16, 2026.

Key Features of Forgejo

• Single static Go binary, ~100 MB: Forgejo ships as one self-contained binary. It runs comfortably on a Raspberry Pi or a 1 GB VPS, and idles around 200 MB of RAM — an order of magnitude lighter than self-hosted GitLab CE, which Recommends 8 GB RAM and asks for at least 4 cores.
• GitHub-compatible workflow: issues, pull requests, code review, protected branches, merge queues, milestones, wiki, releases, mirrors, LFS and webhooks — all behaving the way developers coming from GitHub already expect.
• Forgejo Actions (GitHub Actions-compatible CI): a built-in runner that consumes workflow.yml files written for GitHub Actions, supports the same actions/checkout and actions/setup-* ecosystem via mirroring, and shipped to stable a full release cycle ahead of upstream Gitea Actions.
• ActivityPub federation (ForgeFed): Forgejo is the only mainstream forge actively shipping federated identity and pull-request federation today. Federated stars, follows, and cross-instance issue references are usable on Codeberg, and federated pull requests landed in the v8/v9 series.
• Built-in package and container registry: Docker/OCI, npm, PyPI, Maven, Cargo, NuGet, Composer, Conan, RubyGems, Helm, Chef, generic blobs — one server, one auth model, no extra container needed.
• Database-flexible: SQLite (default, zero-config, perfect for personal use), MariaDB/MySQL, or PostgreSQL.
• Auth and SSO: LDAP, OAuth2 (GitHub, GitLab, Google, Discord, Keycloak, Authelia, Authentik), SMTP, PAM, SAML 2.0, plus first-class TOTP, WebAuthn and FIDO2 hardware keys.
• Browser and end-to-end tests: unlike upstream Gitea, Forgejo runs full browser-based and upgrade-path tests on every release — including accessibility (WCAG) checks — before stable lands.
• Conservative LTS releases: Forgejo backports security fixes to older release lines on a documented schedule, so you don’t need to track every minor version to stay patched.

What Users Say About Forgejo

On r/selfhosted the highest-voted threads on self-hosted Git in 2026 routinely land on the same conclusion: pick Forgejo unless you specifically depend on Gitea Enterprise. Users praise the “it just keeps working” upgrade story — in-place upgrades from older Gitea installs are usually painless because the database schema and config are still compatible — and the resource footprint, which makes it the default choice for homelabs running on a Raspberry Pi 4 or a single low-end VPS.

The most common complaints are honest and recurring: the documentation, while improving, still trails GitLab’s in depth; some advanced enterprise features (advanced merge trains, large-org SSO claim mapping, native code-search-as-a-service) are simpler than what GitLab Premium ships; and on Hacker News, several developers have noted that ActivityPub federation, while live, is still rough-around-the-edges for federated PRs across instances. On the praise side, Hacker News threads consistently call out Forgejo’s nonprofit governance, transparent decision-making, and the speed at which security advisories ship — all things GitLab and proprietary Gitea cannot offer in the same form.

Forgejo Pricing

Forgejo itself is 100% free and fully open source. There is no commercial “Pro” tier to upsell — every feature is in the GPL-3.0+ binary you download. Your only costs are the server you run it on and (optionally) a donation to Codeberg e.V. via Liberapay.

Way to run Forgejo	Cost	Notes
Self-host (Docker, binary, package)	$0 license + your server	Runs on a $4/mo VPS, a Raspberry Pi, or your homelab. SQLite ships in-binary, no extra services needed.
Codeberg public instance	Free	Codeberg.org is a free public Forgejo for free / libre and open source projects, run by the Codeberg e.V. nonprofit.
Managed Forgejo via third-party	Varies	A handful of MSPs offer managed Forgejo (e.g. as part of broader DevOps hosting). No first-party SaaS.

Who Should Use Forgejo?

Best for: solo developers and homelabbers who want a private GitHub on a Raspberry Pi; FOSS projects that care about license-pure, nonprofit-governed infrastructure; small-to-mid engineering teams (1–200 devs) that need pull requests, CI, and a package registry without a $99/user/year GitLab Premium bill; anyone migrating off Gitea who is uncomfortable with the for-profit governance change.

Not ideal for: large enterprises that need premium features like advanced compliance dashboards, SAML group claim mapping with complex policies, or 24/7 vendor SLA support — that’s still GitLab or GitHub Enterprise territory. Also not ideal if you specifically want managed first-party SaaS with a phone number to call — Forgejo is community-run, not vendor-run.

Pros and Cons

Pros:

• Nonprofit, democratic governance via Codeberg e.V. — no risk of a future re-licensing or trademark grab.
• Lightest mainstream forge: 512 MB RAM and one binary versus GitLab CE’s 8 GB recommendation and ~14 services.
• Federation (ForgeFed/ActivityPub) shipped first — Forgejo is years ahead of Gitea on this.
• GitHub Actions-compatible CI included; no separate runner platform needed.
• Strong security release hygiene: monthly patches and documented LTS backports.
• End-to-end and accessibility browser tests on every release.

Cons:

• No first-party hosted SaaS; managed Forgejo is third-party only.
• Documentation, while improving, is thinner than GitLab’s.
• Federation is real but still maturing — some federated PR flows are rough at edges.
• Community support only — no enterprise SLA you can sign.
• Some advanced enterprise features (compliance dashboards, deep merge-train policies) are simpler than GitLab Premium.

Alternatives to Forgejo

Gitea is the upstream Forgejo forked from — almost identical features, but governed by the for-profit Gitea Ltd. and slower to ship federation. GitLab CE is the heavyweight alternative with deeper enterprise features but ~16× the resource footprint. GitHub remains the dominant managed option, but at a per-seat cost and with no self-hosting outside GitHub Enterprise Server. For ultra-minimal needs, Gogs is even lighter than Forgejo but is functionally frozen and far behind on features.

Verdict: Is Forgejo Worth It?

If you want a self-hosted GitHub-like experience in 2026 and you are not contractually locked to Gitea Enterprise or GitLab Premium, Forgejo is the right default choice. The nonprofit governance fixes the single biggest long-term risk in pure-Gitea adoption (a future trademark or licensing change), the resource footprint is the lowest in the category, and the feature set covers 95% of what 95% of teams actually use day to day. We rate it 91/100 — a few points off the perfect 100 because of the still-thin documentation, third-party-only managed hosting, and federation rough edges, but those are fixable issues on a project that is shipping faster than ever.

Frequently Asked Questions

Is Forgejo free?

Yes. Forgejo is 100% free and open source under the GPL-3.0+ license. There is no paid tier — every feature is included in the binary you self-host. Donations to the Codeberg e.V. nonprofit are accepted via Liberapay.

What platforms does Forgejo support?

Forgejo runs on Linux (x86_64, ARM64, ARMv7), and is provided as Docker images, native packages (Debian/Ubuntu, RPM, Alpine, Arch), and a single static binary. It is primarily server software but works on any Linux box, from a Raspberry Pi to a cloud VM.

How does Forgejo compare to Gitea?

Forgejo is a soft fork of Gitea that started in late 2022 over governance concerns. Day-to-day features are very similar, but Forgejo is governed by the Codeberg e.V. nonprofit, ships ActivityPub federation that Gitea does not, has more conservative releases with stronger security backporting, and runs end-to-end and accessibility tests that Gitea does not. Migrating from Gitea to Forgejo is usually a drop-in binary swap.

Is Forgejo open source?

Yes — Forgejo is licensed under GPL-3.0-or-later. The source code lives at codeberg.org/forgejo/forgejo and the project is committed by its governance to remain 100% Free Software in perpetuity.

Does Forgejo support GitHub Actions?

Yes. Forgejo Actions is GitHub Actions-compatible — you can reuse most workflow.yml files and existing actions, with the runner installable as a separate small binary or container. Forgejo Actions hit stable in v15.0’s ecosystem with a new web-based runner registration flow.

Can I migrate from GitHub or Gitea to Forgejo?

Yes — Forgejo includes a built-in repository migration tool that can pull from GitHub, GitLab, Gitea, Bitbucket, OneDev and Gogs (including issues, PRs, milestones and comments). Migrations from Gitea are particularly painless because the database schema is still compatible.