Head-to-head · 2026

Forgejo vs GitHub

Forgejo is a European alternative to GitHub: same developer tools use case, headquartered in Germany and operating under GDPR by default, while GitHub (Microsoft) is based in the United States.

By the EU Alternatives team Last updated

European alternative
Forgejo logo
Forgejo
Germany

Self-host Git repositories, issue tracking, CI/CD, and package registries on a lightweight open-source forge governed by a non-profit — with no corporate lock-in.

Jurisdiction
EU / EEA
GDPR by default
Yes
US CLOUD Act exposure
No
Open source
Yes
Free tier
Yes
See full Forgejo profile
Non-EU
GitHub logo
GitHub
Microsoft · US

GitHub hosts most of the world's open source code and a great deal of private code too, wrapping git in pull requests, issues and CI. Free accounts include unlimited repositories, with paid tiers for teams and enterprises. Microsoft, headquartered in Redmond, Washington, has owned GitHub since 2018.

Jurisdiction
US
GDPR by default
Requires DPA + TIA
US CLOUD Act exposure
Yes
All European alternatives to GitHub

Forgejo vs GitHub at a glance

Forgejo GitHub
Headquarters Germany US
Data jurisdiction EU / EEA US law applies
GDPR by default Yes Requires DPA + transfer assessment
US CLOUD Act exposure No Yes
Open source Yes
Free tier Yes
Best for Teams that need developer tools with EU data residency Teams already invested in the Microsoft ecosystem

Choose Forgejo if…

  • You want your data to stay under EU law without extra legal paperwork
  • GDPR compliance or public-sector requirements apply to you
  • You want to start free and scale up later
  • Open-source code and self-hosting matter to you
  • You'd rather back the European tech ecosystem

Stick with GitHub if…

  • You depend on integrations only available in the Microsoft ecosystem
  • Your organisation has no EU data-residency constraints
  • Migration costs outweigh the jurisdiction benefits for now

About Forgejo

Forgejo is an open-source self-hosted software forge for Git repositories, issue tracking, pull requests, CI/CD pipelines, and package registries, governed by Codeberg e.V., a German democratic non-profit. Forked from Gitea in 2022 over governance concerns, it uses an order of magnitude fewer server resources than comparable forges and can run on a Raspberry Pi or minimal VPS.

Installation takes minutes on any Linux server or container host. ActivityPub federation is in active development to enable cross-instance interactions such as following repositories and commenting on issues across independent Forgejo servers. A GitHub-compatible interface and API simplify migration from proprietary platforms without workflow disruption.

Key benefits:

  • Full Git hosting covering repositories, branches, tags, and LFS with a familiar web interface
  • Issue tracking and PRs with labels, milestones, projects, and code review workflows
  • Forgejo Actions for built-in CI/CD compatible with GitHub Actions workflow syntax
  • Package registry for Docker, npm, PyPI, Maven, Cargo, and other formats
  • ActivityPub federation for cross-instance interactions across the Fediverse
  • Minimal resource footprint that runs comfortably on a Raspberry Pi or 1-vCPU VPS
  • MIT licensed and governed by Codeberg e.V., a non-profit with no corporate investors

Forgejo is maintained by Codeberg e.V., a democratic non-profit registered in Berlin, Germany, under German law and GDPR. The project uses only Free Software for its own development and is hosted on Codeberg, not GitHub. Self-hosted deployments keep all code, issues, and CI data on infrastructure you control, with no telemetry by default.

The upstream project behind Codeberg, Europe's largest community-run Git platform, and the default forge for teams requiring full infrastructure ownership.

Why choose Forgejo over GitHub?

The decisive argument is data jurisdiction. GitHub is headquartered in US, which means personal data processed through it can be subject to non-EU legal regimes: the US CLOUD Act, FISA 702, or similar laws depending on the provider. After the 2020 Schrems II ruling, EU organisations must carry out a transfer impact assessment for every such data flow.

Forgejo removes that overhead. As a Germany-based provider, it operates natively under GDPR, and data stays inside the EU/EEA by default. For regulated sectors such as health, public administration, and finance, that's not a nice-to-have but a requirement. For everyone else, it's concentration-risk insurance: you avoid depending on a single non-EU jurisdiction that can change the rules without warning.

Frequently asked questions

Is Forgejo a good alternative to GitHub?
Yes. Forgejo is one of the top-ranked European alternatives to GitHub in our directory, covering the same developer tools use case. It is headquartered in Germany, keeping your data under EU law by default.
What's the main difference between Forgejo and GitHub?
The biggest difference is jurisdiction: Forgejo is based in Germany and operates under GDPR and EU data-protection law, while GitHub is headquartered in US and may transfer data outside the EU. For regulated industries or organisations following Schrems II guidance, this difference is decisive.
Is Forgejo GDPR-compliant?
Forgejo is a European company based in Germany, so GDPR compliance is the default operating model rather than a bolt-on. No transfer impact assessment is required for EU customers, unlike when using GitHub.
How do I migrate from GitHub to Forgejo?
Start by exporting your data from GitHub (most providers offer an export in their settings). Then import into Forgejo using its native import tool or migration guide. Running both in parallel for a week catches any feature or workflow gaps before you fully switch.

Other European alternatives to GitHub