Host Forgejo without installing anything
A complete Git forge in a single binary: repositories, issues, pull requests, code review and a package registry, on an address that belongs to you.
Starting at €8.99/month
Introduction
Forgejo installed, updated and backed up by us, on a machine in France. Your complete, lightweight Git forge: repositories, issues, pull requests, wiki and package registry. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Confort at €8.99/month incl. VAT — 4 GB of memory. At rest Forgejo fits in a few hundred megabytes: it is a Go binary. What matters is the spikes — a large git push triggers a repack of the objects, the code indexer walks the repositories to feed search, and the package registry handles whole archives. Four gigabytes is the headroom that keeps a three-hundred-megabyte push from making the whole team wait.
Coming over from GitHub or GitLab is not limited to the code: given an access token, the migration tool also imports issues, pull requests, comments, labels, milestones, releases and the wiki. And because Forgejo speaks plain Git, a simple git clone is always enough to leave again: no proprietary format is holding your repositories.
What Forgejo can do
Code review and protected branches
Line-by-line comments on a pull request, a required number of approvals before merging, branches closed to direct pushes. The rules apply per repository and per team.
Built-in package registry
npm, PyPI, Maven, NuGet, Composer, Cargo, OCI containers, Debian and RPM packages: your internal libraries are published in the same place as the code that produces them, with no external registry account to open.
Mirrors and assisted migration
A remote repository can be mirrored, in either direction. That is the gentlest way to leave GitHub: keep both in step while habits move across.
Forgejo Actions
Continuous integration reads workflow files in GitHub Actions syntax. You have to attach a runner — a separate process that picks up jobs and executes them — otherwise nothing gets built.
What people actually use it for
An agency hosting its clients' code
One private repository per client, teams that only reach their own, and no invoice climbing with every developer added. A client can be invited as a reader on their project alone.
Supervised student work
A teacher creates one organisation per cohort and one repository per pair. Under-age students do not have to open an account with an American provider to hand in their project.
Keeping a European copy of public repositories
A freelancer leaves the projects visible on GitHub as a shop window, but keeps a mirror at home. If the account is suspended or the terms change, the work is already elsewhere.
Publishing internal packages
A team of three developers publishes its in-house library as a private npm package, versioned next to its source code, without opening an account on a commercial registry.
Documenting a business application in one place
The wiki, the issues and the release binaries live in the software's own repository. Whoever takes over the job later finds everything in one place rather than spread across three tools.
Hosted in France
In our own infrastructure in Nouvelle-Aquitaine, which we operate ourselves. Your source code and your configuration secrets stay on French soil.
Frequently asked questions
Nothing. You choose the application, fill in the fields it asks for — often an email address and a name — and it goes online. Access arrives by email with the address and the credentials.
Yes. Paste a personal access token into the migration assistant and Forgejo pulls in the Git history, but also the issues and their comments, the pull requests, labels, milestones, releases and the wiki. That is precisely what a plain git clone does not do, and it is what makes the move bearable when a project has three years of discussion behind it.
Forgejo grew out of a fork of Gitea, carried by the non-profit Codeberg e.V. The kinship is direct: the screens look alike, the concepts are the same, and moving between the two requires no data conversion. The real difference is governance — a non-profit on one side, a company on the other.
Yes, with one caveat worth knowing: Forgejo Actions reads workflow files in GitHub Actions format, but running them requires a runner, a process that receives jobs and executes them. Without one, repositories, issues and merges work perfectly, but no build ever starts.
Yes, they are part of the service. A self-hosted application left un-updated is a security risk, not a saving.