Best VPS for GitLab in 2026

GitLab is an all-in-one DevOps platform — Git hosting, CI/CD pipelines, container registry, issue tracking, and more. Self-hosting gives you full control over your code and costs a fraction of GitLab SaaS.

Why Self-Host GitLab?

Factor	GitLab Premium (SaaS)	Self-Hosted VPS
5 users	$145/mo	~$15/mo
20 users	$580/mo	~$30/mo
Storage	50GB per project	Your disk
CI minutes	10,000/mo	Unlimited
Data location	GitLab’s servers	Your choice
Features	Plan-gated	All CE features free

Self-hosting GitLab saves 80-90% and gives you unlimited CI/CD minutes, full data sovereignty, and no per-seat pricing.

VPS Requirements for GitLab

GitLab is a heavy application. It bundles PostgreSQL, Redis, Puma, Sidekiq, Gitaly, and more. Don’t undersize it.

RAM (Critical)

• Absolute minimum: 4GB (will swap, not recommended)
• Small team (1-10 users): 8GB RAM
• Medium team (10-50 users): 16GB RAM
• Large team (50+ users): 32GB+ RAM
• GitLab officially recommends 8GB minimum for production

CPU

• Minimum: 4 vCPU
• Recommended: 4-8 vCPU for smooth CI/CD
• Sidekiq workers and Puma threads both need CPU
• CI runners should ideally run on separate VPS instances (see our Jenkins CI/CD guide for comparison)

Storage

• Minimum: 50GB SSD
• Recommended: 100GB+ NVMe SSD
• Git repos, container registry images, CI artifacts, and LFS objects add up fast
• NVMe matters — Git operations are I/O heavy

Network

• Good bandwidth for git clone/push operations
• Low latency for developer experience
• 1Gbps+ recommended for teams

Top VPS Providers for GitLab

1. Hetzner — Best Overall Value

Hetzner gives you the most resources per dollar, which matters for a RAM-hungry app like GitLab.

Plan	CPU	RAM	Storage	Price
CPX31	4 vCPU	8GB	160GB NVMe	€12.49/mo
CPX41	8 vCPU	16GB	240GB NVMe	€22.49/mo
CPX51	16 vCPU	32GB	360GB NVMe	€42.49/mo

Why Hetzner for GitLab:

• Unbeatable price-to-RAM ratio
• Fast NVMe storage across all plans
• EU data centers (great for GDPR compliance)
• Volumes for expanding storage as repos grow

2. Hostinger — Best for Small Teams

Hostinger offers excellent entry-level plans that work well for small-team GitLab setups.

Plan	CPU	RAM	Storage	Price
KVM 4	4 vCPU	16GB	200GB NVMe	$12.99/mo
KVM 8	8 vCPU	32GB	400GB NVMe	$19.99/mo

Why Hostinger for GitLab:

• Competitive pricing with generous RAM
• NVMe storage standard
• Simple management panel
• Weekly backups included

3. Contabo — Best for Large Repos

Contabo offers massive storage allocations, perfect if you have large repositories, LFS assets, or container images.

Plan	CPU	RAM	Storage	Price
VPS M	6 vCPU	16GB	400GB NVMe	€13.99/mo
VPS L	8 vCPU	30GB	800GB NVMe	€19.99/mo
VPS XL	10 vCPU	60GB	1.6TB NVMe	€34.99/mo

Why Contabo for GitLab:

• Huge storage included
• Most RAM per dollar at higher tiers
• Good for teams with large binary assets

4. DigitalOcean — Best Developer Experience

DigitalOcean offers a polished experience with excellent documentation and one-click marketplace images.

Plan	CPU	RAM	Storage	Price
Premium	4 vCPU	8GB	160GB NVMe	$56/mo
Premium	8 vCPU	16GB	320GB NVMe	$112/mo

Why DigitalOcean for GitLab:

• GitLab marketplace one-click install
• Premium CPU (dedicated) for consistent CI performance
• Managed databases to offload PostgreSQL
• Spaces for offloading object storage (LFS, artifacts)

5. Vultr — Best Global Reach

Vultr has 32+ locations worldwide, giving you the flexibility to place GitLab close to your dev team.

Plan	CPU	RAM	Storage	Price
Cloud Compute	4 vCPU	8GB	200GB SSD	$48/mo
Cloud Compute	8 vCPU	16GB	400GB SSD	$96/mo

Why Vultr for GitLab:

• Widest datacenter selection
• Hourly billing
• Block storage add-ons for growing repos
• API for automation

Provider Comparison Table

Provider	8GB Plan	16GB Plan	Storage	Best For
Hetzner	€12.49/mo	€22.49/mo	NVMe	Overall value
Hostinger	—	$12.99/mo	NVMe	Small teams
Contabo	—	€13.99/mo	NVMe	Large repos
DigitalOcean	$56/mo	$112/mo	NVMe	Dev experience
Vultr	$48/mo	$96/mo	SSD	Global teams

How to Install GitLab on a VPS

Quick Install (Ubuntu 24.04)

# Update system
sudo apt update && sudo apt upgrade -y

# Install dependencies
sudo apt install -y curl openssh-server ca-certificates postfix

# Add GitLab repository
curl -fsSL https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash

# Install GitLab CE
sudo EXTERNAL_URL="https://gitlab.example.com" apt install gitlab-ce

# GitLab configures itself — grab the initial root password
sudo cat /etc/gitlab/initial_root_password

Docker Compose Install (Recommended)

version: "3.8"
services:
  gitlab:
    image: gitlab/gitlab-ce:latest
    container_name: gitlab
    hostname: gitlab.example.com
    restart: unless-stopped
    environment:
      GITLAB_OMNIBUS_CONFIG: |
        external_url 'https://gitlab.example.com'
        gitlab_rails['gitlab_shell_ssh_port'] = 2222
        # Reduce memory usage for small VPS
        puma['worker_processes'] = 2
        sidekiq['concurrency'] = 5
        postgresql['shared_buffers'] = '256MB'
        prometheus_monitoring['enable'] = false
    ports:
      - "80:80"
      - "443:443"
      - "2222:22"
    volumes:
      - gitlab_config:/etc/gitlab
      - gitlab_logs:/var/log/gitlab
      - gitlab_data:/var/opt/gitlab
    shm_size: "256m"

volumes:
  gitlab_config:
  gitlab_logs:
  gitlab_data:

docker compose up -d

Performance Tuning for VPS

Reduce Memory Usage (8GB VPS)

Edit /etc/gitlab/gitlab.rb:

# Reduce Puma workers (default: auto based on CPU)
puma['worker_processes'] = 2

# Reduce Sidekiq concurrency
sidekiq['concurrency'] = 5

# Tune PostgreSQL
postgresql['shared_buffers'] = '256MB'
postgresql['max_worker_processes'] = 4

# Disable monitoring if not needed
prometheus_monitoring['enable'] = false
grafana['enable'] = false

# Disable features you don't use
registry['enable'] = false  # if not using container registry
pages_external_url nil       # if not using GitLab Pages

Then reconfigure:

sudo gitlab-ctl reconfigure

Swap Space

Even with 8GB RAM, add swap as a safety net:

sudo fallocate -l 4G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

Separate CI Runners

Run GitLab Runner on a separate VPS to avoid resource contention:

# On a separate VPS
curl -L "https://packages.gitlab.com/install/repositories/runner/gitlab-runner/script.deb.sh" | sudo bash
sudo apt install gitlab-runner

# Register the runner
sudo gitlab-runner register \
  --url https://gitlab.example.com \
  --token YOUR_REGISTRATION_TOKEN

This keeps your GitLab server responsive while CI jobs run elsewhere.

Backup Strategy

GitLab includes a built-in backup tool:

# Create a full backup
sudo gitlab-backup create

# Automate with cron (daily at 2 AM)
echo "0 2 * * * /opt/gitlab/bin/gitlab-backup create CRON=1" | sudo crontab -

Store backups on a separate volume or object storage. Never keep backups only on the same VPS. See our VPS backup guide for best practices.

GitLab CE vs EE

GitLab Community Edition (CE) is free and includes:

• Unlimited users and repos
• Built-in CI/CD with pipelines
• Container registry
• Issue tracking and boards
• Wiki and snippets
• Merge requests with code review

GitLab Enterprise Edition (EE) adds features like SAML SSO, advanced security scanning, and compliance tools. For most teams, CE covers everything you need.

Our Recommendation

For most teams self-hosting GitLab:

1. Best value: Hetzner CPX41 (8 vCPU, 16GB RAM, €22.49/mo) — handles 10-30 users comfortably
2. Budget pick: Hostinger KVM 4 (4 vCPU, 16GB RAM, $12.99/mo) — solid for small teams
3. Large teams: Contabo VPS XL (10 vCPU, 60GB, €34.99/mo) — massive resources at a low price

Start with 8GB RAM minimum, add a separate runner VPS for CI/CD, and scale up as your team grows. At these prices, you’ll save thousands compared to GitLab SaaS or GitHub Enterprise.

FAQ

How much RAM does GitLab actually need?

GitLab officially recommends 8GB minimum. With memory tuning (reducing Puma workers, disabling Prometheus), you can run on 4GB but expect slowness. For a smooth experience with CI/CD, target 16GB.

Can I migrate from GitLab.com to self-hosted?

Yes. Use GitLab’s project export/import feature. Export projects from GitLab.com, then import them into your self-hosted instance. Groups, issues, merge requests, and CI configs all transfer.

Should I run CI runners on the same VPS?

For small teams with light CI usage, yes. For anything serious, run runners on a separate VPS. CI jobs can spike CPU and memory, making your GitLab UI unresponsive if they share resources.

How do I set up HTTPS?

GitLab uses Let’s Encrypt automatically. Set external_url 'https://gitlab.example.com' in gitlab.rb and GitLab handles certificate provisioning and renewal.

Is GitLab CE enough or do I need EE?

CE covers 95% of teams. You only need EE for enterprise features like SAML/SCIM, advanced security scanning, compliance frameworks, or custom approval rules. Start with CE — you can upgrade later without data loss.