Dedicated servers for GitLab™
Self-managed GitLab and CI/CD runners on bare metal
Run GitLab Self-Managed on a dedicated server with NVMe storage, and move CI/CD jobs to separate runner servers connected over a private VLAN. The same runner servers work for GitLab Runner and GitHub Actions self-hosted runners.
GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions.
-
NVMe storage for repositories
-
High-frequency CPUs for CI builds
-
Private VLAN at 10–25 Gbit/s
-
Root access and IP-KVM
GitLab and GitLab Runner hardware requirements
The baseline for a single-node GitLab instance is 8 vCPU and 16 GB of memory – a 4–6-core CPU with 8–12 threads on a dedicated server. Swap under load slows GitLab down, so 32 GB leaves room for background jobs and growth.
Plan 40 GB for the system and PostgreSQL plus the full size of all repositories. Gitaly, the repository service, is I/O-intensive and needs SSD storage rather than network file systems, so two NVMe drives in RAID 1 are the standard layout.
Burstable cloud instances and disks are a poor fit for GitLab: their speed drops once a usage quota runs out. A dedicated server has no quotas and no neighbors on the same hardware, so its cores and NVMe drives are never throttled by a provider.
CI/CD jobs are best run on a separate server rather than on the GitLab instance. A heavy build then cannot slow down Git, the web interface or code reviews, and pipeline code never runs next to your repositories.
Compilers, tests and image builds lean on single-core speed, so a high clock shortens every job, and cores set how many jobs run in parallel. Each job needs its own memory, and Docker layers and caches live on the runner's NVMe.
Runners pull code, images and artifacts from the instance over a private VLAN at up to 25 Gbit/s – a full Docker image arrives in seconds, not minutes. The public port stays free for your team: Git pushes, merge requests and the web interface never wait behind a pipeline.
Dedicated server pricing for GitLab and runners
View all configurations
Rent a dedicated server for GitLab
from INTROSERV
How to order a dedicated server
Select a configuration, add NVMe drives, choose the OS, wait until the server is ready and install GitLab.
Read the documentationInstall and secure a single-node GitLab instance
Step-by-step installation of GitLab Self-Managed from the official Linux package, with HTTPS and the first sign-in.
Read the tutorialServers and infrastructure for GitLab from one provider
-
1
Install GitLab on the instance server
Install GitLab Self-Managed from the official Linux package on NVMe storage, with the bundled PostgreSQL and Redis. Then set up HTTPS, outgoing email and the container registry.
-
2
Connect runner servers over the VLAN
Order runner servers in the same data center and join them to a private VLAN at up to 25 Gbit/s. Jobs pull code, images and artifacts over the VLAN, not the public port.
-
3
Register the runners
Install GitLab Runner with the Docker executor and register it with your instance. For repositories on GitHub, the same servers run GitHub Actions self-hosted runners.
-
4
Back up with the INTROSERV Backup Service
Back up the whole instance server with the INTROSERV Backup Service – NAKIVO software and storage in one ready-made service. Restore the entire server or a single file when needed.
GitLab licensing and support
Licensing
GitLab Enterprise Edition is the recommended install: without a license it runs on the free tier, and Premium or Ultimate unlock later with an activation code, with no reinstall. Community Edition is the open source alternative under the MIT license, with the same free features. Subscriptions are sold by GitLab Inc. or its partners, not by INTROSERV.
Support
Support for GitLab itself comes from the GitLab forum and documentation, or from GitLab Inc. with a paid subscription. INTROSERV takes care of the Linux servers GitLab runs on: monitoring, security, OS updates and incident fixes with a server management plan, and one-time tasks as hourly system administration.
FAQ
-
How fast is the server delivered?
Instant configurations are ready within 3-6 hours of payment; custom builds usually take up to 24 hours. The delivery time is shown on each configuration in the catalog.
-
Can the server be tested first?
Yes. A paid test period of up to 5 days is available, enough to install GitLab, push a repository and run the first pipeline.
-
Which operating system should I choose?
A Linux distribution supported by the official GitLab package, such as Ubuntu LTS or Debian. The package bundles PostgreSQL, Redis and the web server, so the system needs nothing else installed.
-
Can I use my own domain and HTTPS certificate?
Yes. Point a DNS record at the server, and the GitLab package can request and renew a Let's Encrypt certificate on its own. A certificate from another authority can be installed instead.
-
Can GitLab Pages run on the same server?
Yes. Pages runs as a separate service and needs a wildcard DNS record. Custom domains for Pages also need a second IP address, which can be added to the server.
-
What happens when an NVMe drive fails?
With two drives in RAID 1, GitLab keeps running on the remaining drive. You open a support ticket, INTROSERV replaces the drive in the data center, and the array rebuilds.
-
Can more runner servers be added later?
Yes. Order another runner server in the same data center, add it to the existing VLAN and register it with your instance. Pipelines start using it as soon as it is online.
-
Can storage be expanded later?
On DC1, DC2 and DC3 configurations, yes: drives for free slots are added by a support ticket, and the monthly price changes accordingly. For other configurations, it is best to choose the drive layout with some headroom at order time.