Gitea
Compare VPS plans to self-host Gitea. providers advertising 1GB+ RAM from $2/mo. Gitea server hosting comparison.
Find the best and cheapest VPS plans to self-host Gitea.
Minimum Requirements
These VPS plans meet the minimum requirements to run Gitea. 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
Gitea VPS Sizing: Storage, Sync, and Scale
Gitea turns a VPS into a private Git forge with repositories, pull requests, issues, and optional CI/CD through Gitea Actions. The hosting decision affects whether Git pushes stay snappy, whether large clones queue up, and whether a small control-plane app remains small once teams add runners, Git LFS, and more repositories.
Resource Profile Classification
The primary resource profile is Mixed. self-hosted-tools.json lists a 1 GB minimum and 2 GB production target, which fits a lightweight Go-based forge, but the first production bottleneck changes with usage: the web UI itself is light, while Git activity, repository storage, Actions workloads, and database choice create the real infrastructure pressure.
Gitea is written in Go and stays light for the application itself, but repository growth, Git operations, Actions runners, and attached databases move the bottleneck depending on how teams actually use it.
Storage and Network Interpretation
Treat Gitea as light compared with GitLab CE, not as cost-free infrastructure. The application benefits from Go efficiency and can stay comfortable on a small VPS, but Git repository growth, Git LFS objects, backups, and clone or fetch bursts still make storage quality relevant. SSH and HTTPS Git traffic also need predictable network behavior; 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 | 1 GB | 10 GB | The 1-core, 1 GB, and 10 GB floor is enough for a personal forge, testing, or a very small team with light repository activity. |
| Production | requirements.recommended |
2 Cores | 2 GB | 50 GB | The 2-core, 2 GB, and 50 GB production tier is the small live baseline for Gitea where multiple repositories, pull requests, backups, and steady Git activity need headroom. |
| Scale | editorial interpretation |
Add steadier CPU when repository indexing, diffs, syntax highlighting, and runner-adjacent workloads become frequent. | Add RAM for PostgreSQL or MySQL cache, more concurrent Git requests, and any co-located reverse proxy, backup, or monitoring services. | Plan storage around repository growth, Git LFS objects, snapshots, and backups rather than the small application binary. | At scale, Gitea stops being limited by its lightweight Go core and starts being limited by the developer workflow around it. The next step is usually cleaner storage, more database headroom, and moving runners or other CI jobs off the same low-end VPS. |
Anti-Patterns
- Do not describe Gitea as zero-cost just because it is lightweight and written in Go.
- Do not confuse Gitea Actions with free CI capacity on the same tiny VPS; runners need their own CPU and RAM plan.
- Do not size only for the web UI while ignoring Git LFS growth, repository backups, and database responsiveness.
- Do not assume Gitea and Forgejo are identical pages with a name swap; Gitea is the original lightweight Go forge, while Forgejo is the community-driven fork with different governance priorities.
Who It Fits
For: Good fit for individuals or small teams that want a lightweight Go-based Git forge, modest repository growth, and a simple self-hosted alternative to heavier all-in-one DevOps suites.
Not for: Avoid an entry-level VPS if CI runners, large monorepos, heavy Git LFS use, many concurrent developers, or attached registry-like workloads are part of the plan.
FAQ
Is Gitea really lightweight?
Yes. Gitea is written in Go and self-hosted-tools.json lists a 1 GB minimum and 2 GB production RAM target, which is far lighter than GitLab CE.
What is the main scaling risk?
The risk is treating the light web UI as the whole workload. Repositories, Git LFS, backups, and Actions runners can outgrow a small VPS long before the Go application itself does.
What should I check before buying?
Check storage quality for repositories and backups, renewal pricing, whether runners will live elsewhere, and uplink terms for Git clone and fetch traffic.
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 Gitea bottlenecks rather than a name-swap template.
What is Gitea?
Gitea is a self-hosted Git service written in Go, single-binary with no external dependencies, providing Git hosting, code review, issue tracking, wiki, and CI/CD via Gitea Actions. Teams adopt it when they want GitHub feature parity without GitHub's pricing or infrastructure complexity. The limit is the single-binary model - for larger teams needing horizontal scaling or advanced DevSecOps, GitLab CE is the next step up.
Why Server Specs Matter
Gitea is remarkably efficient due to its Go implementation and embedded SQLite support. The server handles Git operations (push, pull, clone), web interface, issue tracking, and background tasks. Memory usage scales with active users and repository count. CPU is used for Git operations, syntax highlighting, and diff generation. Larger repositories and heavy Git activity increase resource needs. The database stores repository metadata, issues, and user data.
Problems with Undersized Servers
With limited resources, Git operations become slow - clones and pushes take longer. The web interface becomes sluggish when viewing large files or repositories. Syntax highlighting may fail on large files. Search across repositories times out. Multiple simultaneous Git operations queue up. The application remains functional but noticeably slower. Actions/CI runners need their own resources.
Our Recommendation
For personal use, 1GB RAM and 1 CPU core run Gitea smoothly. Small teams should use 2GB RAM. Use SQLite for single-user instances, PostgreSQL for teams. Plan storage based on repository sizes - 10-50GB for small teams, more for larger codebases. Git LFS requires additional storage planning. Enable SSH for better Git push/pull performance. Consider Actions runners on separate machines for CI/CD workloads.
Minimum Requirements - VPS Plans
These VPS plans meet the minimum requirements to run Gitea. 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.