Tool
Forgejo
A lightweight self-hosted software forge — issues, PRs, packages, and Git hosting you run yourself — stewarded by a non-profit community (Codeberg e.V.) rather than a venture-backed SaaS.
What it is
Forgejo is a Free Software forge for collaborative coding: repositories, pull/merge requests, issues, wiki, CI hooks, and related project tooling. Official install paths include binary and Docker; third-party packages exist but are less thoroughly tested against every release. The project publishes a stable release every three months, an LTS yearly, and more frequent patches for bugs and security. It is a soft fork of Gitea with an explicit focus on remaining exclusively Free Software, federation, and privacy. You can migrate from Gitea while keeping data — see the project’s migration docs.
What it replaces
It replaces “all our code lives only on GitHub/GitLab.com” when you want the familiar forge shape on hardware you control — small teams, classrooms, community instances, or a personal private forge beside the rest of a homelab.
It does not replace a full DevOps platform out of the box (you still wire CI runners, backups, auth, and exposure yourself). It is not a hosted SaaS with someone else doing ops. Federation and advanced features evolve on the project’s timeline — don’t assume parity with every proprietary forge feature on day one.
License
Forgejo versions from v9.0 onward are released under the GNU GPL v3 or later, verified from the project’s August 2024 license announcement and Free Software Directory listing. Earlier Forgejo versions (v8.0 / v7.0 patch lines) remain under MIT. Official binaries and container images are meant to be compliant out of the box; if you redistribute modified binaries you must provide corresponding source under the same GPL terms. The forge still depends on Git (GPL-2), which you use alongside it.
Where it falls over
- You own ops: upgrades, backups, runner capacity, and disk for repos — a forge without backups is a time bomb.
- Exposing it to the public internet without reverse-proxy TLS, auth hardening, and update cadence is the usual foot-gun.
- Third-party OS packages may lag or break across releases; prefer official binary/Docker paths unless you know the packager.
- License is GPL-3.0+ from v9 — fine for self-host and most hosting businesses that pass freedoms along; redistribution of modified binaries has source obligations.
- Soft-fork history with Gitea means you should follow Forgejo’s own release notes and LTS calendar, not assume Gitea timing.
- CI is integration, not magic: Actions/runners still need machines, secrets hygiene, and resource limits.
Who it's for
Individuals and teams who want a GitHub-shaped forge on their own VPS or NAS, and communities that care about Free Software stewardship (Codeberg-style). Not a substitute for learning Git, writing backups, or sizing disk for growing repos.
Related in this cluster
- Coolify — self-hosted PaaS if you also want deploy plumbing
- Docker — common install path for the forge
- Caddy / Nginx Proxy Manager — reverse proxy + TLS in front
- Tailscale — private access without hanging the forge naked on the internet
- Self-hosting hub — more open replacements and plumbing
Verdict
Use Forgejo when you want a GPL-3.0+ (v9+) lightweight forge for repos you control, with a non-profit Free Software story. Install from official binary or Docker, put TLS and access control in front, schedule backups before the first real project lands, and treat runners as part of the job.
← Tools · Self-hosting · Home · forgejo.org · Codeberg