Media & apps
Gitea vs Forgejo: which git server?
Gitea vs Forgejo: which self-hosted git server should I use?
Short answer
Gitea vs Forgejo: which self-hosted git server should I use?
For a new install, pick Forgejo — it's a community-governed fork of Gitea, functionally the same today, and it's the one I'd bet on staying independent. If you already run Gitea and it's working, there's no urgent reason to switch; migration is a clean drop-in whenever you feel like it, not a fire drill.
Both are lightweight, self-hosted GitHub-style git servers — repositories, issues, pull requests, a web UI — that run happily on modest hardware. Forgejo is a fork of Gitea, created and governed by a non-profit community after Gitea moved under a for-profit company; day to day they look and work almost identically.
- Drop-inGitea → Forgejo migration (same data layout)our own migration
- CommunityForgejo's governance (non-profit) vs Gitea's company
- LowRAM either needs — both run comfortably on a small box
They’re the same tool with different stewards
This is an unusual comparison because, feature for feature, there’s very little daylight between them today. Forgejo began as a fork of Gitea, and for now it tracks closely — you’d struggle to tell them apart from the UI. So the decision isn’t really technical. It’s which project’s governance you’d rather support, and which you think will stay healthy longest.
How to actually choose
- Starting fresh? Pick Forgejo. You get the same software with community governance, and you’re not betting on anything you’ll regret.
- Already on Gitea and happy? Stay. There’s no feature you’re missing and no cliff coming. Migrate on your own schedule, or don’t — it’s a clean move whenever.
The honest non-answer
If you were hoping for a decisive “X crushes Y,” there isn’t one, and pretending otherwise would be dishonest. These are two good, light, self-hosted git servers that are near-identical in daily use. Choose on governance and vibe, run either without worry, and know that whichever you pick, moving to the other later is about as painless as software migrations get.
| Factor | Gitea | Forgejo |
|---|---|---|
| What it is | The original | Community fork of it |
| Governance | For-profit company | Non-profit community |
| Features today | Effectively the same | Effectively the same |
| Migration | — | Drop-in from Gitea |
I moved from Gitea to Forgejo and it was a clean drop-in — same data, nothing to relearn. I'd rather back the community-governed fork, so that's where I landed.
Common questions
Will my Gitea data and workflow carry over to Forgejo?
Yes — Forgejo forked from Gitea and kept the same data layout, so migrating is essentially pointing Forgejo at your existing data. Your repos, issues, and users come across, and the UI is familiar enough that there's nothing to relearn.
Is one meaningfully faster or lighter?
Not in any way you'd notice at home. Both are written in Go, ship as a single binary plus a database, and run comfortably on a small mini PC or even a Pi. The choice is about governance and direction, not performance.
Why did Forgejo exist in the first place?
Gitea moved under a for-profit company, and part of the community preferred a project governed by a non-profit. Forgejo is that project. Whether that matters to you is the actual deciding factor — the software itself is nearly the same.