Best VPS for GitLab in 2026
Updated Oct 2026 · 8 plans compared
GitLab CE is not a small install: it bundles PostgreSQL, Redis, Gitaly, Puma, Sidekiq and NGINX behind one Omnibus package, and upstream's own single-node requirements reflect that — 16 GB RAM and 8 vCPU as the baseline, with 8 GB workable only in a memory-constrained setup. That makes GitLab the one workload on this site where recommending a genuinely large VPS is the honest call, not an upsell: the picks below are all providers whose 20 GB+ tiers actually clear GitLab's documented footprint, not their cheapest boxes.
- Take GitLab's own numbers at face value: 16 GB RAM and 8 vCPU is the documented baseline for a single-node install, and the 8 GB figure it also publishes is explicitly a memory-constrained fallback, not a target to plan around.
- Omnibus runs PostgreSQL, Redis, Gitaly, Puma, Sidekiq and NGINX as one bundle on the same box — there's no lightweight mode. Undersizing shows up as slow CI pipelines and Sidekiq job backlogs first, then OOM kills.
- Budget storage like a real Git host, not like a small app: repositories, LFS objects, the container and package registries, and CI artifacts all accumulate on top of the RAM requirement, so favor a plan with generous NVMe over one that's merely RAM-heavy.
- First boot is slow — give the box time on initial setup, whichever install path you take, and grab the initial root password from `/etc/gitlab/initial_root_password` before it's deleted on the first restart after 24 hours.
The picks
CPX52 (12 vCPU / 24 GB / 480 GB NVMe, $119.59/mo) is the Hetzner box you can order today — the cheaper CX53 has been out of stock since 2026-09 — and its vCPU count gives CI pipeline concurrency and Sidekiq job throughput room to grow before the next resize.
The Cloud VPS 8 (8 vCPU / 24 GB / 300 GB NVMe, $13.44/mo) is the cheapest plan in this lineup that actually clears GitLab's documented 16 GB baseline with real headroom, and Contabo's storage-heavy pricing means the 300 GB NVMe absorbs repos, the container registry and CI artifacts without a second upgrade.
VPS-4 (8 vCPU / 24 GB / 200 GB NVMe, $23.37/mo) matches GitLab's 8 vCPU baseline exactly, with unlimited traffic and daily backups included — useful given how much Omnibus writes to disk on a busy instance.
The picks, side by side
Prices verified Oct 2026 · How we benchmark →
Common questions
How much RAM does self-hosted GitLab actually need?
GitLab's own single-node requirements list 16 GB RAM and 8 vCPU as the baseline, and say it can run in a memory-constrained environment with as little as 8 GB — but that's a fallback, not a plan. Size for the 16 GB baseline and you avoid the slow CI pipelines and Sidekiq backlogs that show up first when GitLab is starved of memory.
Why does GitLab need so much more than Gitea or Gogs?
Omnibus is one bundle running PostgreSQL, Redis, Gitaly, Puma, Sidekiq and NGINX together, not a single Go binary. Gitea covers the same core Git-hosting use case in a few hundred megabytes; GitLab trades that efficiency for the built-in CI/CD runner fleet, container and package registries, and Pages that Gitea doesn't ship.
Can I run GitLab on a smaller VPS and upgrade later?
Technically yes on the 8 GB memory-constrained minimum, but expect it to feel undersized immediately — GitLab's background workers (Sidekiq) and CI runners compete for the same RAM as the web process. It's cheaper in practice to start at the 16 GB baseline than to resize a live instance mid-project.