Gitea’s current documentation says that 2 CPU cores and 1 GB of RAM are typically sufficient for small teams and projects. Treat that as a starting point for the Gitea service, not a universal server minimum. The operating system, database, reverse proxy, monitoring, repository size and optional Actions workloads also consume resources.
Quick Gitea VPS sizing answer
| Workload | CPU | RAM | Storage approach |
|---|---|---|---|
| Personal repositories and light use | 2 vCPU | 1 to 2 GB | Start from current repository data, then add room for growth and backups |
| Small team with regular web and Git activity | 2 vCPU | 2 GB | Size for repositories, packages, logs and a separate backup copy |
| Larger repositories, packages or several companion services | 2 to 4 vCPU | 4 GB or more | Measure current data and growth instead of relying on a fixed disk minimum |
| Gitea Actions jobs | Size separately | Size separately | Include runner images, caches, logs and artifacts |
The first row stays close to the official Gitea system guidance. The additional RAM in the small-team and larger-workload rows is our operational buffer for the rest of the server stack. It is not an official Gitea minimum.
What changes the requirement
CPU and RAM
Repository browsing and ordinary pushes are light compared with code indexing, package handling and concurrent requests. Start with 2 vCPU for a small team. Add memory before adding unrelated services to the same VPS, and watch actual memory use after importing your repositories.
Do not size the Gitea web service from CI jobs. Gitea Runner executes Actions jobs on a host or in containers, and those jobs can use far more CPU, memory and disk than Gitea itself. A separate runner keeps a busy build from starving Git and web requests.
Storage
Gitea does not publish a universal 10 GB or 20 GB disk requirement. Storage depends on repository history plus attachments, packages, Git LFS objects, Actions logs, artifacts and backups. Check the current data size, estimate growth, and keep backup capacity outside the live data volume.
The official backup documentation covers the database, repositories and application data. A disk that only fits today’s repositories is not enough for a recoverable installation.
Database choice
Gitea’s database documentation supports PostgreSQL, MySQL, MariaDB, SQLite and MSSQL. SQLite is built in and works for a small installation, but the documentation warns that it does not scale. Choose the intended production database before the instance grows because conversion between database types is not a well-tested routine.
| Situation | Practical database choice |
|---|---|
| Personal instance with light use | SQLite can keep the setup simple |
| Growing team or regular production use | PostgreSQL, MySQL or MariaDB |
| Existing Microsoft database environment | MSSQL is supported |
Existing VPS plan examples
The table below preserves the site’s existing plan figures. Confirm current price, region and resources on the provider site before ordering. The 1-vCPU entries are personal or testing candidates, not matches for Gitea’s documented 2-core small-team baseline.
| Provider | Price (monthly) | RAM | CPU Core | Storage |
|---|---|---|---|---|
| Contabo VPS | 5.99 EUR | 4 GB | 2 Core | 200 GB |
| Hetzner Cloud | 5.49 EUR | 4 GB | 2 Cores | 40 GB |
| DigitalOcean | 6 USD | 1 GB | 1 Core | 25 GB |
| Vultr | 5 USD | 1 GB | 1 Core | 25 GB |
| Linode | 5 USD | 2 GB | 1 Core | 25 GB |
For a decision focused on Gitea, compare the best VPS options for Gitea or the lower-cost Gitea shortlist. Once the server is selected, continue with the Gitea VPS installation guide. The broader VPS comparison remains available for other workloads.
Frequently Asked Questions
What is the minimum RAM needed to run Gitea effectively?
Gitea documents 2 CPU cores and 1 GB of RAM as typically sufficient for small teams and projects. A 2 GB VPS gives the operating system, database and reverse proxy more headroom. Measure the imported instance before increasing resources further.
Can Gitea be hosted on a low-cost VPS?
Yes. Match the actual CPU, memory, disk and region to the workload instead of choosing by price alone. A plan with only 1 vCPU falls below the documented small-team baseline even if its memory and storage look sufficient.
What database options can I use with Gitea?
Gitea supports PostgreSQL, MySQL, MariaDB, SQLite and MSSQL. SQLite is the simplest choice for a small instance, but Gitea warns that it does not scale. For a growing installation, select the intended production database from the start.
Requirements checked against current Gitea documentation on September 6, 2026. Provider figures were not changed in this review and should be verified before purchase.