Forgejo
Compare VPS plans to self-host Forgejo. providers advertising 0.5GB+ RAM from $2/mo. Forgejo server hosting comparison.
Find the best and cheapest VPS plans to self-host Forgejo.
Minimum Requirements
These VPS plans meet the minimum requirements to run Forgejo. Suitable for testing or light usage.
Recommended Requirements
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
Source: self-hosted-tools.json
Forgejo VPS Sizing: Storage, Sync, and Scale
Forgejo turns a VPS into a self-hosted Git forge that feels close to Gitea in day-to-day operation, but the hosting decision also reflects a governance choice. It exists for operators who want a lightweight forge and prefer a community-driven fork over the original project path.
Resource Profile Classification
The primary resource profile is Mixed. self-hosted-tools.json lists Forgejo at 0.5 GB minimum and 1 GB production RAM, which makes it even lighter than Gitea on paper, but the important distinction is why it exists: Forgejo forked from Gitea after the Gitea domains and trademark were transferred to a for-profit company, and the Forgejo community wanted a public-interest, community-driven governance model.
Forgejo keeps the light Go-based forge footprint of early Gitea-style deployments, but federation ambitions, repository growth, and runner usage can move the bottleneck beyond the tiny application baseline.
Storage and Network Interpretation
From an infrastructure perspective, Forgejo behaves much like a lightweight Go forge: repositories, pull requests, SSH or HTTPS Git traffic, backups, and optional Actions runners define the real sizing. Federation-related features can add some overhead, but the bigger buying choice is whether you want Gitea-like efficiency with community governance. As with any Git host, We recommend verifying the latest uplink specs directly on the provider's SLA due to regional variation.
Minimum vs Production vs Scale
| Stage | Source | CPU | RAM | Storage | Interpretation |
|---|---|---|---|---|---|
| Minimum | requirements.minimum |
1 Core | 0.5 GB | 10 GB | The 1-core, 0.5 GB, and 10 GB floor is enough for testing, personal use, or a tiny forge where repository activity stays light. |
| Production | requirements.recommended |
2 Cores | 1 GB | 50 GB | The 2-core, 1 GB, and 50 GB production tier is the live baseline for a small Forgejo deployment with real repositories, pull requests, backups, and modest team activity. |
| Scale | editorial interpretation |
Add steadier CPU when repository indexing, diffs, syntax highlighting, or runner-adjacent tasks become frequent. | Add RAM for database cache, more users, reverse proxy overhead, and any federation-related services before the host starts swapping. | Plan storage around repository growth, snapshots, backups, and optional Git LFS data rather than the application binary. | At scale, Forgejo follows the same pattern as other lightweight Git forges: the base app remains small, but the surrounding developer workflow grows first. The next step is better storage discipline and runner separation, not jumping straight to a GitLab-sized node. |
Anti-Patterns
- Do not describe Forgejo as just renamed Gitea; the key difference is the fork history and community-driven governance.
- Do not ignore why the fork happened: governance and project control changed after Gitea moved domains and trademark to a for-profit company.
- Do not treat the 0.5 GB minimum as a team-ready forever spec when repositories, backups, and runners grow.
- Do not assume federation, Actions runners, or larger repository sets stay free of CPU, RAM, and storage consequences just because the base app is light.
Who It Fits
For: Good fit for individuals, nonprofits, and small teams that want a very lightweight Git forge, care about community-led governance, and do not need the full resource footprint of GitLab CE.
Not for: Avoid an entry-level VPS if you expect heavy CI, many active developers, large repositories, or you mainly need enterprise-style all-in-one DevOps features rather than a lean forge.
FAQ
How is Forgejo different from Gitea?
Forgejo started as a fork of Gitea, keeps a similar lightweight Go-based operating model, but is community-driven and was created after governance concerns around Gitea moving domains and trademark to a for-profit company.
Is Forgejo lighter than GitLab CE?
Yes. self-hosted-tools.json lists Forgejo at 0.5 GB minimum and 1 GB production RAM, while GitLab CE starts at 4 GB minimum and 8 GB production RAM.
What should I check before buying?
Check repository storage growth, backup options, renewal pricing, whether runners live elsewhere, and uplink terms for Git traffic before choosing the cheapest VPS.
Quality Checks
- Engineering-Check: Yes, the page names the first bottleneck and its failure mode.
- Trade-off-Check: Yes, it states who should avoid an entry-level VPS.
- Renewal-Price-Check: Yes, buyers are warned that low first-term prices can distort VPS selection.
- Keyword-Anchor-Check: Yes, internal anchors on the page use VPS and self-hosting terms instead of generic labels.
- Data-Link-Check: Yes, Minimum and Production values map to
self-hosted-tools.json. - Uniqueness-Check: Yes, the analysis is tied to Forgejo bottlenecks rather than a name-swap template.
What is Forgejo?
Forgejo is a GPL-licensed fork of Gitea maintained by a community instead of a commercial entity, with Git hosting, issue tracking, pull requests, CI/CD via Forgejo Actions, and ActivityPub federation for cross-instance collaboration. Teams use it when they want Gitea compatibility with stronger open-source governance and no per-seat licensing. The trade-off against Gitea is a smaller community and fewer third-party integrations.
Why Server Specs Matter
Forgejo shares Gitea's efficient Go-based architecture, maintaining similar resource requirements. The server handles Git operations, web interface, and background tasks with minimal overhead. Memory scales with users and repositories. CPU handles Git processing and syntax highlighting. Database (SQLite or PostgreSQL) stores metadata and issues. Federation features, when enabled, add modest additional overhead.
Problems with Undersized Servers
Like Gitea, undersized Forgejo instances experience slower Git operations and web interface. Large repositories take longer to browse. Syntax highlighting may fail on large files. Actions runners need additional resources. However, Forgejo remains functional at lower resource levels than many alternatives - it degrades gracefully rather than failing completely.
Our Recommendation
Personal instances run well on 512MB-1GB RAM. Small teams should use 2GB RAM. SQLite works for single users; use PostgreSQL for teams. Storage depends on repository sizes - plan 10-50GB minimum. Forgejo's efficiency makes it suitable for VPS alongside other services. Enable SSH for Git operations. Federation features are experimental - monitor resource usage if enabled. Consider Actions runners on separate infrastructure.
Minimum Requirements - VPS Plans
These VPS plans meet the minimum requirements to run Forgejo. Suitable for testing or light usage.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Recommended Requirements - VPS Plans
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Some links on this page are affiliate links. If you make a purchase through these links, we may earn a small commission at no extra cost to you. This helps us keep the site running and provide free comparison tools.