Home›Catalog›⚙️ DevOps & Infrastructure›Forgejo
Screenshot of Forgejo website

// screenshot of forgejo.org ↗

DEVOPS & INFRASTRUCTURE · PRO TIER

Forgejopro

Forgejo is a community-driven fork of Gitea — a lightweight, self-hosted Git platform with code hosting, issue tracking, PRs, CI/CD via Forgejo Actions, container registry. Started in 2022 when Gitea pivoted toward commercial ownership; Forgejo is now Codeberg's preferred platform and the truly community-owned option.

Install via WHMCS → Visit forgejo.org ↗
⚙️ DevOps & Infrastructure Min 512 MB RAM Port 3000 (http) Tier pro
// What it is

A closer look.

Forgejo is a community-driven fork of Gitea — a lightweight, self-hosted Git platform with code hosting, issue tracking, PRs, CI/CD via Forgejo Actions, container registry. Started in 2022 when Gitea pivoted toward commercial ownership; Forgejo is now Codeberg's preferred platform and the truly community-owned option.

For teams who want Git hosting without trusting commercial roadmap pressure.

// Use cases

What it's for.

Concrete scenarios where teams pick Forgejo over the SaaS alternative.

◆

Self-hosted Git

code hosting for internal / private projects

◈

Issue tracking

GitHub Issues equivalent

◇

Pull request workflow

code review on your infrastructure

▣

CI/CD with Forgejo Actions

GitHub Actions-compatible workflow runner

▦

Container registry

push Docker images privately

// Who it's for

Built for these teams.

If your team profile matches one of these, Forgejo is a strong fit out of the box.

Profile A

Engineering teams

wanting self-hosted Git for proprietary code

Profile B

Open-source projects

moving from GitHub (often due to Microsoft concerns)

Profile C

Privacy-bound orgs

keeping code in-network

Profile D

Cost-conscious teams

avoiding GitHub Enterprise per-seat billing

Profile E

Communities

building shared infrastructure (Codeberg model)

// Differentiators

Why teams pick Forgejo.

When evaluating self-hosted options for this category, here are the dimensions on which Forgejo consistently lands above the alternatives.

  • ✓MIT license + community governance — fork of Gitea with explicit community ownership
  • ✓Lightweight — runs comfortably on $5/mo VPS
  • ✓GitHub Actions compatibility — most existing workflows work with Forgejo Actions
  • ✓Active development — strong release cadence by maintainer collective
  • ✓Federation — early support for ActivityPub-based federation
  • ✓No commercial conflict — explicitly non-profit governance
// Integrations

Connects to.

The stack you'll plug Forgejo into — services, protocols, and adjacent apps in the BluixApps catalog.

◇
Git protocols
SSH, HTTPS, git daemon
◈
Authentication
local + LDAP + OAuth (GitHub, GitLab, custom) + SAML
◆
Webhooks
fire on push / PR / issue events
▣
Actions runners
Forgejo Actions for GitHub-compatible CI/CD
▦
Container registry
OCI registry built-in
▩
Package registry
npm, PyPI, Maven, NuGet, Composer
▼
Mirror
push/pull mirror to GitHub, GitLab, Codeberg
// Adoption & deployment

Notable users & community

  • 4k+ GitHub stars (rapidly growing)
  • Codeberg uses Forgejo as primary platform
  • Many OSS projects migrating from Gitea or GitHub
  • Active matrix.org community
  • Backed by Codeberg e.V. (non-profit) — strong governance

What we ship

  • Docker compose: Forgejo + Postgres
  • Pinned codeberg.org/forgejo/forgejo:11.0 (release-tagged LTS)
  • HTTPS via Let's Encrypt
  • Admin user via first-run wizard
  • Persistent volumes for repos + database + attachments
  • SSH server enabled on alternate port
  • Backup hook covers Postgres + repo files + attachments
// Tips & operations

Run it properly.

Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.

// PERFORMANCE
Choose carefully between Forgejo and Gitea
Forgejo for community governance, Gitea for commercial-backed
// SECURITY
Set SECRET_KEY in env
auto-generated but should be preserved across upgrades
// OPERATIONS
Use Postgres for production
default SQLite breaks under multi-user concurrent writes
// RELIABILITY
SSH server config
Forgejo can run its own SSH or use system SSH; pick one
// DEPLOYMENT
Backup is critical
DB + repo files + attachments + LFS = three separate stores
// SCALING
Federation is alpha
useful for personal but not production-ready
512
// min ram (MB)
10
// min disk (GB)
3000
// access port
http
// protocol
pro
// bluixapps tier
3000:3000 · codeberg.org/forgejo/forgejo:11.0.14
// docker image

Project resources

Official siteforgejo.org ↗
GitHubgithub.com ↗
Documentationforgejo.org ↗
Communityforgejo.org ↗
// Alternatives in DevOps & Infrastructure

Compare with

DevOps & Infrastructure
Gitea
Open page →
DevOps & Infrastructure
GitLab CE
Open page →