Forgejo vs Gogs
Both are alternatives to GitHub. Here's how they stack up — verified facts, no spin.
Also searched as Gogs vs Forgejo — same comparison, one verdict.
Forgejo and Gogs are closely matched on ownership (99 vs 96) — this one comes down to pricing and to which trade-offs below you can live with.
Forgejo
TOP PICKCommunity-governed, copyleft self-hosted Git forge.
Forgejo is a lightweight, self-hosted Git forge stewarded by the non-profit Codeberg e.V. It is a soft fork of Gitea and stays close to it in features, offering repositories, pull requests, code review, issue tracking, a package registry, and GitHub-Actions-compatible CI via Forgejo Actions. Its draw is governance and durability: a non-profit steward plus a copyleft license aimed at keeping the software free for users over the long term. A good fit for teams that want a modern forge with independent, community-first governance.
Gogs
Ultra-lightweight, painless self-hosted Git service.
Gogs is a minimal, self-hosted Git service written in Go and released under the MIT license — the project Gitea was originally forked from. Its goal is to be the simplest and most resource-frugal way to run your own Git server, shipping as a single binary that runs on almost anything, including low-power ARM devices. It covers the essentials (repositories, issues, pull requests, webhooks) but moves more slowly and offers fewer features than Gitea, Forgejo, or GitLab.
Side by side
10 points of comparison, every one read from a verified field. Green marks the side that wins a row outright. A dash means we do not hold that fact — never that it is zero.
| Forgejo | Gogs | |
|---|---|---|
| Sovereignty ScoreOur transparent 0–100 composite for data ownership and exit cost. | 99 | 96 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first data | Yes | Yes |
| License | GPL-3.0-or-later | MIT |
| Pricing | Free / self-host | Free / self-host |
| RAM to run it wellThe figure that actually matters, not the vendor's minimum. | 2 GB for Forgejo plus PostgreSQL on one box for a 5–20 person team. CI builds need their own machine | 1 GB for Gogs plus a database. The README says memory use stays low as teams grow |
| Realistic running costWhat the box costs each month if you run it yourself. | $6–12/mo for a 5–20 user instance on a 2 GB VPS, plus a separate runner box if you use Actions | $5–6/mo for a 5–20 user instance on a 1 GB VPS |
| Setup timeHonest first-install estimate, not the marketing quickstart. | 30 minutes with docker compose; an afternoon once you add SSH, TLS and an Actions runner | 20 minutes with Docker or the binary and the first-run web installer |
| Ongoing maintenanceThe part nobody budgets for. | A new major version every quarter. Stable majors get about three and a half months of fixes; the yearly LTS gets 15 months (v15 LTS runs to 15 July 2027). The docs require a full backup before each stable upgrade. | There were no releases from February 2023 to December 2024. Since then releases have come as batches of security fixes (0.13.2 Dec 2024, 0.13.3 Jun 2025, 0.13.4 Jan 2026, 0.14.x Feb–Jun 2026). Watch the advisories and patch the same week. |
Forgejo is Macrostack's recommended GitHub alternative, so it's our pick here.
Weighing both against staying on GitHub? Is GitHub free? What it actually costs →
Forgejo
Strengths
- +Non-profit governance (Codeberg e.V.) reduces the risk of future vendor capture
- +Copyleft GPL-3.0+ license (since v9.0) is designed to keep modified versions open
- +Lightweight — runs comfortably on a small VPS or a Raspberry Pi
- +GitHub-Actions-compatible CI via Forgejo Actions; supports OAuth, LDAP, and a package registry
Trade-offs
- −Younger project with a smaller community and third-party ecosystem than Gitea or GitHub
- −As a soft fork of Gitea, its independent identity and long-term divergence are still maturing
- −You own all operations: backups, upgrades, and security patching are your responsibility
- −GPL-3.0+ copyleft terms may not suit organizations that want a permissive license
Gogs
Strengths
- +Extremely lightweight — runs on minimal hardware, including a Raspberry Pi or ARM board
- +Permissive MIT license and a simple single-binary install
- +Low maintenance footprint for small teams and personal use
- +Standard Git under the hood keeps code and history fully portable
Trade-offs
- −Slower release cadence and a smaller maintainer team than Gitea or Forgejo
- −Fewer features (no built-in Actions-style CI; lighter package/registry support)
- −Smaller community and integration ecosystem
- −Self-hosting responsibilities (backups, upgrades, security) rest with you
Which one fits you
The trade-offs above, turned into a decision. Find the line that describes your team.
Choose Forgejo
if a lower exit cost matters more to you than any single feature, and non-profit governance (Codeberg e.V.) reduces the risk of future vendor capture.
Choose Gogs
if extremely lightweight — runs on minimal hardware, including a Raspberry Pi or ARM board.
Neither, yet
if both carry a real cost you should weigh first — younger project with a smaller community and third-party ecosystem than Gitea or GitHub, and slower release cadence and a smaller maintainer team than Gitea or Forgejo. If either of those is a dealbreaker for your team, the shortlist is wrong rather than the choice.
What it takes to run these yourself
Real requirements and honest running costs, not the vendor quickstart.
Self-hosting Forgejo
2 GB for Forgejo plus PostgreSQL on one box for a 5–20 person team. CI builds need their own machine RAM · 30 minutes with docker compose; an afternoon once you add SSH, TLS and an Actions runner
$6–12/mo for a 5–20 user instance on a 2 GB VPS, plus a separate runner box if you use Actions
Self-hosting Gogs
1 GB for Gogs plus a database. The README says memory use stays low as teams grow RAM · 20 minutes with Docker or the binary and the first-run web installer
$5–6/mo for a 5–20 user instance on a 1 GB VPS
Forgejo vs Gogs — common questions
Is Forgejo a better fit than Gogs for code hosting & git forges?
It depends on what you are optimising for, and the honest split is this: Forgejo scores 99 to Gogs's 96 on data ownership and exit cost, so it is the safer choice if you care about being able to leave. Gogs earns its place on a different axis — extremely lightweight — runs on minimal hardware, including a Raspberry Pi or ARM board. Neither is a wrong answer for every team; the table above is the actual comparison.
What happens if we want to switch later?
Forgejo keeps its data local or in open formats, so leaving is an export rather than a negotiation. Gogs is still self-hostable, so the files stay on your server either way — but it is not local-first by design, so check what its export produces before you rely on it.
Can I self-host Forgejo or Gogs?
Both can be self-hosted. The difference is what it costs you in time rather than whether it is possible — see the setup and maintenance rows above.
Are Forgejo and Gogs both alternatives to GitHub?
Yes — both appear in our GitHub comparison, which is why they are worth putting side by side. People usually arrive here already having decided to move off GitHub and now choosing between the two replacements, which is a narrower and much easier question.
Related alternative guides
Facts verified 2026-07-07. Licenses and pricing change — spotted something out of date? That's a correction we want.