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

Hostinger

Hostinger KVM 8 VPS

8vCPU
32 GBRAM
400 GBStorage
32 TBTransfer
  • 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.
OVHcloud

OVHcloud VPS-1 (US)

2vCPU
4 GBRAM
40 GBStorage
—Transfer
  • Virtual Core
  • 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.
OVHcloud

OVHcloud VPS-2 (US)

4vCPU
8 GBRAM
75 GBStorage
—Transfer
  • Virtual Core
  • 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.
OVHcloud

OVHcloud VPS-3 (US)

6vCPU
12 GBRAM
100 GBStorage
—Transfer
  • Virtual Core
  • 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.
OVHcloud

OVHcloud VPS-4 (US)

8vCPU
24 GBRAM
200 GBStorage
—Transfer
  • Virtual Core
  • 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.
Scaleway

Scaleway DEV1-S (Paris)

2vCPU
2 GBRAM
—Storage
—Transfer
  • Shared vCPU (AMD EPYC)
  • Dynamic Local SSD or Block (bi...
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.
SiteGround

SiteGround Jump Start Managed Cloud VPS

4vCPU
8 GBRAM
40 GBStorage
5 TBTransfer
  • Dedicated CPU (Google Cloud)
  • 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.
SiteGround

SiteGround StartUp Managed WordPress

—vCPU
—RAM
10 GBStorage
—Transfer
  • SSD
Compatibility unclear from published plan data

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 plan does not publish this runtime or configuration detail.
  • At least 8 GB memory for constrained single-node installationsThe plan does not publish this runtime or configuration detail.
Vultr

Vultr Cloud Compute · 1 vCPU / 0.5 GB

1vCPU
0.5 GBRAM
10 GBStorage
500 GBTransfer
  • Shared vCPU (previous-generati...
  • 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.
Vultr

Vultr Cloud Compute · 1 vCPU / 1 GB

1vCPU
1 GBRAM
25 GBStorage
1 TBTransfer
  • Shared vCPU
  • Standard 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.
Vultr

Vultr Cloud Compute · 1 vCPU / 2 GB

1vCPU
2 GBRAM
55 GBStorage
2 TBTransfer
  • Shared vCPU (previous-generati...
  • 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.
Vultr

Vultr Cloud Compute · 16 vCPU / 64 GB

16vCPU
64 GBRAM
1,280 GBStorage
10 TBTransfer
  • Shared vCPU (previous-generati...
  • 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.

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