Forgejo review

Forgejo is a self-hosted software forge: a place to manage software projects and collaborate on development, running on a server you control. Its homepage describes it as easy to install and maintain, with a low server profile and a focus on security, privacy, federation and scaling. Those are project claims, not a guarantee that every installation will be simple to operate.

For developers moving from GitHub, Forgejo aims to offer a familiar environment without handing control of the forge to a hosted platform. Its federation focus is intended to support decentralized collaboration, though the published material does not spell out specific federation capabilities or limits.

Forgejo says it will always remain Free and Open Source Software. That describes the software’s stated commitment; it does not mean Forgejo publishes a paid hosted plan. The published pricing information lists no commercial plans or monthly or annual billing.

The clearest reason to choose Forgejo is control. You host the forge yourself, so your organization chooses where it runs and manages the server rather than relying on a third-party hosted service. That can suit personal repositories, small teams or volunteer groups that want to keep their development platform in their own hands.

The homepage presents Forgejo as lightweight and easy to maintain, and says it uses fewer resources than other forges. Treat that as the project’s positioning; the published material provides no measurements or hardware requirements to compare. Still, a low server profile is a sensible selling point for people running a modest self-hosted setup.

The free-software commitment also gives switchers a clear distinction to weigh against alternatives. In one Reddit thread, a Forgejo user said they switched because of Gitea’s commercial stance and found Forgejo easy to maintain. Another commenter said installing it and beginning a migration was easy. Those are individual reports, not a promise that every migration will be smooth.

The pricing information lists no paid plans, add-ons or recurring billing. That makes the software’s published price straightforward, but running the server remains your responsibility.

Forgejo is self-hosted, so choosing it means taking responsibility for the server and its upkeep. The homepage calls it easy to install and maintain, but the published material does not specify a managed hosting option, service-level commitments, support tiers or support prices. There are no published plan caps to compare; the pricing information lists no commercial plans or monthly or annual billing.

Migration deserves particular care. In one Reddit thread, a user said Forgejo does not support migrations from Gitea versions after 1.22 and described being stuck on Gitea 1.25. That is a report from a user discussion, not a complete migration policy, but it is a concrete warning: check the current migration path and your backup before switching, especially if your source is newer than 1.22.

The published material also does not provide specific server requirements or measured resource comparisons. Forgejo’s homepage says it has a low server profile, but that claim alone is not enough to size a server for your workload. If you want a hosted service with published tiers and someone else handling operations, the available information does not establish that Forgejo offers one.

The available pricing record, marked low confidence, lists no Forgejo commercial plans, monthly or annual billing, or add-ons. It also lists no starting price. So there is no published tier jump to compare, and no plan caps or paid features to price out. The record says Forgejo has a free plan, while the project describes the software as Free Software; that does not establish the cost of running it.

Forgejo is self-hosted, so your practical costs depend on the server and the work of maintaining it. The published sources do not give hosting prices, support-plan prices, or a cost estimate. They also do not describe billing gotchas such as annual discounts or usage fees. We would treat the listed $0 commercial price as “no published commercial pricing,” not as a promise that operating a Forgejo server costs nothing. Confirm hosting and support needs before comparing it with a managed service.

Forgejo is a self-hosted forge, so switching means taking responsibility for hosting and server management rather than choosing a managed Forgejo plan. The published material gives no migration guide, time estimate, supported import or export formats, or data-export instructions. It also flags a Gitea migration as unverified, so we would verify compatibility and make a backup before planning that move.

The brief identifies teams seeking managed hosting or published support plans as a poor fit, but it provides no Reddit posts or comments. We therefore can’t responsibly say what tends to make people leave based on Reddit. The same evidence gap applies to claims about common migration failures or lock-in. Before switching, confirm how your repositories, issues, project data and user accounts can be moved; those details are not published on the vendor's site. If you need an operator to run the service or a defined support plan, Forgejo may not fit.