Application hosting

Hosting GitLab Self-Managed

GitLab Self-Managed combines repositories, CI/CD, registry and project tools. Its current single-node guidance uses an 8-vCPU baseline and at least 8 GB memory in constrained installations.

Min vCPU
8
Min memory
8 GiB
Min storage
Depends on workload

Must have

Hard prerequisites

  • 8 vCPU single-node baseline
  • At least 8 GB memory for constrained single-node installations

Recommended

Documented guidance

No further general recommendations are published for this version.

Published starting requirements

GitLab documents a smaller tuned exception for tiny teams. The baseline here is for a standard single-node installation; CI runners, registries and repository growth add capacity needs.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Official Linux package
  • Official Docker image
  • Helm chart for Kubernetes

The host must provide

Runtime

Operating system
A supported Linux distribution for the chosen installation method
Storage
Persistent repository, database, uploads, artifacts and registry storage as enabled

Storage

Persistent data

No universal disk size fits every installation. Repositories, CI artifacts, container images, packages and backup archives may dominate storage.

Step by step

GitLab deployment outline

  1. Size the single node

    Use the installation requirements for the intended workload and account for runners separately.

    Official instructions
  2. Install a supported release

    Follow the official package, Docker or Helm path and configure HTTPS and a stable hostname.

    Official instructions
  3. Plan full recovery

    Back up all enabled data stores and test restoration on a matching GitLab version.

    Official instructions

Security

Before you go public

  • Protect administrator and runner credentials.
  • Use HTTPS and keep GitLab updated.
  • Test a complete backup and restore.

Cost

Beyond the server price

  • Account for large persistent storage and backup retention.
  • CI runners, container registry and high availability can require separate infrastructure.

Matching plans

Plans with published evidence

DigitalOcean

CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB

2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
  • Dedicated CPU
  • SSD
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value does not satisfy this requirement.
DigitalOcean

General Purpose Droplet · 2 Dedicated vCPU / 8 GB

2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
  • Dedicated vCPU (100% allocatio...
  • NVMe SSD
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Google Cloud

Compute Engine e2-medium · 2 vCPU / 4 GB

2vCPU
4 GBRAM
—Storage
—Transfer
  • Shared vCPU (1.00 sustained)
  • Persistent Disk (billed separa...
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value does not satisfy this requirement.
Google Cloud

Compute Engine e2-small · 2 vCPU / 2 GB

2vCPU
2 GBRAM
—Storage
—Transfer
  • Shared vCPU (0.50 sustained)
  • Persistent Disk (billed separa...
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value does not satisfy this requirement.
Hetzner Cloud

Hetzner Cloud CCX13 (Germany and Finland)

2vCPU
8 GBRAM
80 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CCX23 (Germany and Finland)

4vCPU
16 GBRAM
160 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CCX33 (Germany and Finland)

8vCPU
32 GBRAM
240 GBStorage
30 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value satisfies this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CCX43 (Germany and Finland)

16vCPU
64 GBRAM
360 GBStorage
40 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value satisfies this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CCX53 (Germany and Finland)

32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value satisfies this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CCX63 (Germany and Finland)

48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Meets the documented hard prerequisites

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value satisfies this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value satisfies this requirement.
Hetzner Cloud

Hetzner Cloud CPX11 (US locations)

2vCPU
2 GBRAM
40 GBStorage
1 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value does not satisfy this requirement.
Hetzner Cloud

Hetzner Cloud CPX12 (Germany and Finland)

1vCPU
2 GBRAM
40 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Does not meet a documented hard prerequisite

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • 8 vCPU single-node baselineThe published plan value does not satisfy this requirement.
  • At least 8 GB memory for constrained single-node installationsThe published plan value does not satisfy this requirement.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.