Forgejo review

Forgejo is software you run as a self-hosted forge, not a library, CLI tool or hosted API. It sits alongside your development workflow as the place to manage software projects and collaborate. The project also points users to Codeberg and other instances, so self-hosting is an option rather than the only way to access Forgejo.

The problem it targets is the need for a GitHub-like environment that an organization can operate itself. The homepage describes a familiar environment for GitHub users, project management features and collaboration tools, with a focus on security, scaling, federation and privacy. It also describes Forgejo as lightweight and easy to maintain, though those are project claims rather than published deployment benchmarks. In a stack, Forgejo is the project and collaboration service your team operates or selects as an instance; it does not replace your source code or the servers and processes needed to run the service.

The homepage describes Forgejo in terms of software project management, collaboration and self-hosting. It does not name an API style, SDKs, supported programming languages, CLI, webhooks or plugin system. The practical integration surface established by the product description is the Forgejo instance and its project-collaboration environment; confirm in Forgejo's documentation whether its API, authentication options and integrations meet your workflow before building against them.

That matters if you need automation for repository creation, issue tracking or release workflows: do not assume a particular SDK or endpoint based on the product category. Forgejo supports federation as a project focus, but the homepage does not give protocol details there. The project invites contributions in code, federation, release management, documentation and other areas. For a team evaluating it, start with the official documentation and verify the exact interfaces, supported versions and maintenance expectations your codebase will rely on.

Forgejo's software is free and the project says it will always be Free and Open Source Software. The pricing page information available for this review lists no monthly or annual plans, commercial tiers, add-ons or starting price. There is no published trial or paid tier to compare, and no usage-based rate, per-seat fee or request allowance is listed.

Free software does not make a self-hosted deployment cost-free to operate. Your organization needs to account for its own server, storage, backups, network and administration, but Forgejo does not publish a hosting calculator or a per-project cost. The homepage describes a low server profile and says Forgejo requires an order of magnitude fewer resources than other forges; it does not provide a workload, configuration or benchmark behind that claim. Codeberg and other instances are alternatives to running your own server, but their pricing and service terms are not specified on Forgejo's homepage. Ask the instance operator about capacity, backups and support before relying on a hosted instance.

Forgejo describes itself as exclusively Free Software and says it will always be Free and Open Source Software. The homepage invites users to download it and self-host their own instance. It does not name a specific license there; a Reddit commenter calls it MIT-licensed, so confirm the current license in the project repository before making a legal or compliance decision.

Self-hosting gives your organization control over where the service runs, but data export and migration procedures are not described on the homepage. Treat migration as a due-diligence item: identify how repositories, issues, users and other project data can be moved, then test the path against your current version. A Reddit user reports a limitation migrating from Gitea after version 1.22. That is a user report, not a universal migration specification, but it makes version compatibility worth checking before switching.

The Forgejo homepage says the project focuses on security, scaling, federation and privacy, and describes the server profile as low. It does not publish specific rate limits, capacity figures, service-level commitments or compliance certifications on the homepage. Before putting a production team on it, verify current release and security practices in the project documentation, decide who owns updates and backups, and test recovery with your own repositories and data.

A Reddit user running Forgejo in a container describes it as easy to maintain; another says installation was easy. Those are individual reports, not operational guarantees. Migration deserves particular attention: a user considering a move from Gitea says Forgejo does not support migrations from Gitea after 1.22. Confirm the relevant version path with the project documentation before planning a cutover. Also check federation behavior, authentication requirements and storage growth against your deployment, since the homepage does not publish production limits for those areas.