Forgejo
Community soft-fork of Gitea focused on free software governance
Review status: Research backlog. Research candidate with incomplete checks; not a vetted recommendation.
Official Website · Source Code
oss-osi-approved planned guideOverview
Forgejo is a Git forge soft-fork. Teams preferring its governance model use it similarly to Gitea for private code and docs.
At a glance
| Field | Value |
|---|---|
| Categories | developer-platform |
| Deployment | self-hosted |
| License class | oss-osi-approved (GPL-3.0-or-later) |
| Cost model | free-self-hosted |
| Implementation difficulty | easy |
| Maintenance burden | medium |
| Maturity | stable |
| Freshness status | partially-verified (2026-07-17) |
| Completeness | partial |
| Confidence | low |
| Directory tier | research-backlog |
Cost reality
Free software with self-host costs.
Pricing and free-tier limits change frequently; re-check official pricing before budget decisions.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Self-hosted git forge
- Lightweight CI integrations
Human oversight still needed
- Fork differences vs Gitea
- Backup
Manual process this can replace
Structured task-fit review has not been completed for this tool. Treat the free-text examples above as evaluation prompts, not replacement claims.
Data held
-
repositories
-
users
-
issues
-
Personal data: yes
-
Payment data: no / not primary
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Evaluate export formats and API completeness before deep customization. |
| Security | Apply updates promptly; restrict admin access; enable TLS. |
| Compliance | Operator remains responsible for privacy and local regulatory obligations. |
| Licensing | Confirm license fits commercial coworking use. |
| Operational | Plan backups, monitoring, and a restore drill before production use. |
Coworking fit
Roles: technical-operator
Workflows: multi-site-rollout, backup-restore-drill
Problems: self-host-for-data-control, centralize-knowledge
Smallest useful experiment
Migrate one internal repo and compare admin UX to your current forge.
Initial planning estimate (unverified): 1–3 days
Links
Implementation guide
No implementation guide is published yet.
Verification
- Status:
partially-verified - Completeness:
partial - Confidence:
low - Tier:
research-backlog - Last reviewed:
2026-07-17 - Sources:
Seed entry compiled from official project sites and repositories. Re-verify pricing, license text, and feature claims before production decisions. Star counts and free-tier numeric limits intentionally omitted unless verified at review time.