Forgejo

Codeberg e.V. and independent contributors launched Forgejo in late 2022 to maintain a community-directed Git forge free from commercial takeover. Built as a single compiled Go binary, it provides repository hosting, code reviews, and CI automation without tiered licensing. Today it offers engineering teams an independent platform operating entirely under non-profit governance.

Why Forgejo instead of GitHub Enterprise

GitHub Enterprise Server runs as a heavyweight virtual appliance requiring multiple vCPUs and tens of gigabytes of RAM to power its background services, search indexing, and databases. Forgejo compiles to a lean Go binary that idles below 200 megabytes of memory on basic virtual servers or edge hardware. Git pushes, code browsing, and web navigation return with low latency, avoiding the infrastructure overhead of enterprise appliances. For continuous integration, Forgejo Actions runs GitHub Actions YAML syntax through companion runners, executing containerized builds locally without cloud queuing.

GitHub Enterprise retains deeper compliance suites, including automated secret scanning networks, enterprise audit log streaming, and native merge queues for busy branches. Migrating repositories, issues, and workflows to Forgejo is straightforward, though DevOps engineers must manage storage backups, runner fleets, and network security themselves. Swapping GitHub Enterprise for Forgejo trades proprietary compliance appliances and per-seat subscription invoices for fast page loads on hardware that costs a fraction of the price.

What it does well

• Single Go binary with a low memory footprint that runs on low-cost virtual private servers or single-board computers.
• Direct execution of GitHub Actions workflow YAML files via Forgejo Actions and local runner daemons.
• Integrated package registry hosting OCI container images, npm modules, PyPI packages, and Maven artifacts alongside code.
• Flexible identity integration supporting LDAP directories, OAuth2 providers, and reverse proxy headers for team authentication.
• Pluggable database support covering SQLite for single nodes alongside PostgreSQL and MySQL for replicated deployments.
• Built-in pull request reviews, branch protections, issue milestones, and Kanban boards that coordinate daily engineering work.

Limitations