Best VPS for Gitea in 2026
Updated Aug 2026 · 8 plans benchmarked
Gitea is a single Go binary that idles in a couple of hundred megabytes — the server choice is almost never about CPU or RAM, it's about disk. Repositories, LFS objects, container images and CI artifacts accumulate quietly, and the day you turn on Actions runners the box stops being small.
- Gitea itself is tiny — the Go binary with SQLite runs happily under 512 MB. Give it 2 GB so a Postgres backend, a reverse proxy and the occasional large clone all fit without swapping.
- Disk is the real sizing question: repos, Git LFS objects and the package registry grow far faster than anyone plans for, so start with more NVMe than you think and check that the provider lets you add storage later.
- CI changes everything. A Gitea Actions runner on the same box turns an idle service into a build machine — budget 4 GB and 4 cores minimum, or put runners on a separate server.
- SSH on port 22 is the sticking point: you either move the host's sshd or map Git SSH to another port, so pick a provider whose firewall and console let you fix a locked-out box.
The picks
The value pick: a CX22 (2 vCPU / 4 GB / 40 GB NVMe) runs Gitea and Postgres at single-digit utilization, and the generous included traffic absorbs clone-heavy days. Stepping up to the CX32 buys the headroom Actions runners want.
Buys the most disk per dollar of the group — its entry Cloud VPS ships enough NVMe to hold years of repositories, LFS objects and package-registry blobs without a storage upgrade, which is exactly what Gitea eats.
Custom sizing is the answer to Gitea's lopsided profile — you can buy modest RAM but a large NVMe volume for repos and LFS instead of paying for a fixed plan's CPU. Hourly billing also makes a disposable CI runner cheap.
The lowest-friction path: clear docs, a straightforward firewall UI for the Git SSH port question, and block storage you can attach as the repo directory fills. You pay a premium over Hetzner for that polish.
The picks, side by side
Prices verified Aug 2026 · How we benchmark →
Common questions
How much RAM does Gitea need?
Less than almost anything else you'll self-host — the Go binary with SQLite is comfortable in 512 MB. 2 GB is the sensible floor once you add Postgres and a reverse proxy, and 4 GB is the number to reach for if you plan to run Gitea Actions runners alongside it.
How much disk space should I give Gitea?
Take the size of your repositories and multiply generously. Git LFS objects, the container and package registries, and CI artifacts are what actually fill the disk, and none of them shrink on their own. Prefer a provider that lets you attach more storage rather than one where growth means rebuilding the server.
Can I run Gitea and its CI on the same VPS?
For light use, yes — but understand the trade. An Actions runner executes arbitrary build jobs on the same machine that serves your Git repos: it competes for CPU and disk, and it's a much larger attack surface. On anything busier than a personal instance, run the runner on a separate box.