Gitea Hosting: Where Low-RAM Dev VPS Land in Our Chart
Gitea's footprint is tiny—512 MB minimum, well under typical entry-tier VPS. Our chart ranks providers by effective cost to host a lightweight Git server, showing where each option lands on spec-to-price ratio for lean deployments.
Hetzner runs Gitea under $3.50/mo
At $3.29/mo for 2 GB RAM + 2 vCPU + 40 GB NVMe, Hetzner gives you the lowest entry price in our chart—enough to comfortably host Gitea for teams up to 50 members.
Get Hetzner VPS →Gitea — Ultra-Low RAM Requirements
Gitea needs just 512 MB RAM to start; typical deployments with 20–50 users consume 200–400 MB resident. This means even the cheapest tier in our chart (Hetzner at $3.29/mo with 2 GB) leaves you overhead for CI jobs or concurrent users. GitLab by contrast needs 4–8 GB minimum, making Gitea the clear choice for budget-conscious teams.
Repository storage grows over time (one active repo = 100 MB–1 GB). The binding constraint is disk, not CPU or RAM. Pick a plan with at least 40 GB NVMe and you'll have room to scale to hundreds of repos without resizing.
Our chart reflects this: Gitea pages work on nearly any tier. The real differentiation is price-per-provider and storage allocation. Even the $3.29 entry point on Hetzner suits small-to-medium teams indefinitely.
Minimum Server Requirements for Gitea
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 512 MB | 2 GB |
| CPU | 1 vCPU | 2+ vCPUs |
| Storage | 10 GB | 40+ GB NVMe |
| OS | Ubuntu 22.04+ | Ubuntu 24.04 LTS |
Top 5 VPS Providers for Gitea Compared
We deployed Gitea on each provider and measured startup time, response latency, and resource usage. Here are the results:
Pros
- Unbeatable price-to-performance ratio
- European data centers with strong privacy
- NVMe storage on all plans
Cons
- No US data centers
- Control panel less polished than competitors
All Hetzner Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| CX22 | 2 vCPU | 4 GB | 40 GB NVMe | $4.15/mo | Get Plan → |
| CX32 | 4 vCPU | 8 GB | 80 GB NVMe | $7.49/mo | Get Plan → |
| CX42 | 8 vCPU | 16 GB | 160 GB NVMe | $14.49/mo | Get Plan → |
| CX52 | 16 vCPU | 32 GB | 320 GB NVMe | $28.49/mo | Get Plan → |
Pros
- Very beginner-friendly control panel
- Competitive pricing with frequent deals
- 24/7 customer support
Cons
- Renewal prices are higher
- Limited advanced configuration options
All Hostinger Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| KVM 1 | 1 vCPU | 4 GB | 50 GB NVMe | $4.99/mo | Get Plan → |
| KVM 2 | 2 vCPU | 8 GB | 100 GB NVMe | $6.99/mo | Get Plan → |
| KVM 4 | 4 vCPU | 16 GB | 200 GB NVMe | $12.99/mo | Get Plan → |
| KVM 8 | 8 vCPU | 32 GB | 400 GB NVMe | $19.99/mo | Get Plan → |
Pros
- Excellent documentation and tutorials
- $200 free credit for new accounts
- Strong developer ecosystem
Cons
- Higher pricing than budget providers
- No phone support available
All DigitalOcean Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| Basic | 1 vCPU | 2 GB | 50 GB SSD | $12.00/mo | Get Plan → |
| Regular | 2 vCPU | 4 GB | 80 GB SSD | $24.00/mo | Get Plan → |
| CPU-Optimized | 2 vCPU | 4 GB | 25 GB SSD | $42.00/mo | Get Plan → |
| Memory-Opt | 2 vCPU | 16 GB | 50 GB SSD | $84.00/mo | Get Plan → |
Pros
- 32 data center locations worldwide
- Hourly billing with no lock-in
- High-performance NVMe storage
Cons
- Interface can be overwhelming for beginners
- Support response times vary
All Vultr Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| Cloud Compute | 1 vCPU | 2 GB | 50 GB SSD | $10.00/mo | Get Plan → |
| Cloud Compute | 2 vCPU | 4 GB | 80 GB SSD | $20.00/mo | Get Plan → |
| High Frequency | 2 vCPU | 4 GB | 64 GB NVMe | $24.00/mo | Get Plan → |
| Bare Metal | E-2286G | 32 GB | 2x 480GB SSD | $120.00/mo | Get Plan → |
Pros
- One-click deploys from Git
- Auto-scaling based on usage
- No server management needed
Cons
- Can get expensive at scale
- Less control over infrastructure
All Railway Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| Hobby | Shared 8 vCPU | 8 GB | 100 GB | $5.00/mo | Get Plan → |
| Pro | Shared 32 vCPU | 32 GB | 250 GB | $20.00/mo | Get Plan → |
| Enterprise | Custom | Custom | Custom | Custom | Get Plan → |
Architecture Overview
A typical Gitea deployment on a VPS uses Docker for easy management and Nginx as a reverse proxy:
Gitea Deployment Architecture
How to Set Up Gitea on a VPS
Step 1: Provision a small VPS
Choose your VPS provider (we recommend Hetzner for the best value), select an Ubuntu 24.04 LTS image, and configure your SSH keys. Most providers have this ready in under 2 minutes.
Step 2: Deploy Gitea with Docker
SSH into your server, install Docker and Docker Compose, and pull the Gitea container image. Configure your environment variables and Docker Compose file according to the official documentation.
Step 3: Configure SSH, domain, and user access
Set up Nginx as a reverse proxy with SSL certificates from Let's Encrypt. Point your domain to the server IP, and your Gitea instance will be accessible via HTTPS.
Frequently Asked Questions
How much RAM does Gitea actually use?
Typical deployments: 100–400 MB resident. Even with concurrent users and CI jobs, Gitea stays under 512 MB. This is why entry-tier VPS plans are sufficient.
Can Gitea run on the cheapest VPS tier?
Yes. Gitea fits comfortably on 1–2 GB plans. The bottleneck is usually storage (repos grow over time) and bandwidth, not RAM or CPU.
Does Gitea include CI/CD?
Yes. Gitea Actions is GitHub Actions-compatible and runs inside the Gitea container. No separate CI infrastructure needed.
What about backups and uptime?
A single VPS running Gitea has a single point of failure. Mitigate via automated database backups (hourly/daily) and redundant storage where feasible.
How do I migrate from GitHub or GitLab?
Gitea has a built-in importer for repos, issues, and pull requests. Select the source provider and paste a token; Gitea handles the rest in-app.