EUR
european

EUR

usa

USD

Ex. VAT Ex. VAT 0%

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 NVMe storage for repositories NVMe storage for repositories
  • High-frequency CPUs for CI builds High-frequency CPUs for CI builds High-frequency CPUs for CI builds
  • Private VLAN at 10–25 Gbit/s Private VLAN at 10–25 Gbit/s Private VLAN at 10–25 Gbit/s
  • Root access and IP-KVM Root access and IP-KVM Root access and IP-KVM
nl-map nl-map
AMD Zen 5 up to 5.7 GHz AMD Zen 5 up to 5.7 GHz AMD Zen 5 up to 5.7 GHz
Unmetered traffic Unmetered traffic Unmetered traffic
Enterprise NVMe drives Enterprise NVMe drives Enterprise NVMe drives
DDR5 ECC memory DDR5 ECC memory DDR5 ECC memory

GitLab and GitLab Runner hardware requirements

Instance: CPU and RAM

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.

Instance: storage

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.

Instance: steady performance

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.

Runners on separate servers

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.

Runners: clock speed, cores and NVMe

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.

Private VLAN between instance and runners

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

Up to 1000 users

From €60.40/month
Team instance 4–8 cores, 8–16 threads 16–64 GB ECC RAM 2× NVMe in RAID 1 VLAN up to 25 Gbit/s
- Repositories, registry and web UI
- Runners on separate servers
Select configuration

Fast CI jobs

From €166/month
Runner server 8 cores, up to 5.3 GHz 32–192 GB DDR5 ECC RAM NVMe build cache VLAN up to 25 Gbit/s
- GitLab Runner or GitHub Actions
- Builds for a small team
Select configuration

Parallel pipelines

From €179/month
Pipeline runner 12 - 16 cores, up to 5.7 GHz 64–256 GB DDR5 ECC RAM 2 - 4× NVMe build cache VLAN up to 25 Gbit/s
- Several pipelines at once
- Monorepos and long test runs
Select configuration

Build farm

From €250/month
Build farm node 32 cores and more 128 GB - 1,5 TB ECC RAM 4 - 10× NVMe VLAN up to 25 Gbit/s
- C++, Rust, Android builds
- Many runners on one host
Select configuration

Rent a dedicated server for GitLab
from INTROSERV

How to order a dedicated server How to order a dedicated server

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 documentation
Install and secure a single-node GitLab instance Install and secure a single-node GitLab instance

Install 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 tutorial

Servers and infrastructure for GitLab from one provider

Rent the GitLab server, the runner servers and backups from one provider. The servers run in one data center on a private VLAN, backups go to INTROSERV's own storage, and every step below can be ordered as a setup job.

  • 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.

Moving from GitLab.com to self-hosted?

Moving from GitLab.com to self-hosted?

Groups and projects, with their issues and merge requests, move to your own instance with GitLab's direct transfer. Container images and packages are moved separately.

cunsoultant

GitLab setup by INTROSERV engineers

Installation, migration, runners and backups as a one-time job, or ongoing care of the servers with a server management plan.

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.

GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions. INTROSERV is an independent hosting provider and is not affiliated with, endorsed by, sponsored by or a partner of GitLab Inc. GitLab is developed, licensed and supported by GitLab Inc.; INTROSERV provides the server hardware and optional system administration only. Linux, Docker and PostgreSQL are trademarks or registered trademarks of their respective owners, used for identification only.

processor

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.

VAT

  • Other

    Ex. VAT

    0%
  • austria

    Austria

    20%
  • Belgium

    Belgium

    21%
  • Bulgaria

    Bulgaria

    20%
  • Croatia

    Croatia

    25%
  • Cyprus

    Cyprus

    19%
  • Czech Republic

    Czech Republic

    21%
  • Denmark

    Denmark

    25%
  • Estonia

    Estonia

    22%
  • France

    France

    20%
  • Finland

    Finland

    24%
  • Germany

    Germany

    19%
  • Greece

    Greece

    24%
  • Hungary

    Hungary

    27%
  • Ireland

    Ireland

    23%
  • Italy

    Italy

    22%
  • Latvia

    Latvia

    21%
  • Lithuania

    Lithuania

    21%
  • Luxembourg

    Luxembourg

    17%
  • Malta

    Malta

    18%
  • Netherlands

    Netherlands

    21%
  • Poland

    Poland

    23%
  • Portugal

    Portugal

    23%
  • Romania

    Romania

    19%
  • Slovakia

    Slovakia

    20%
  • Slovenia

    Slovenia

    22%
  • Spain

    Spain

    21%
  • Sweden

    Sweden

    25%
  • USA

    USA

    0%
european
states
  • kingdom
  • germany
  • Español
  • French
  • Hrvatska
  • Italiano
  • Poland
  • Slovenski
  • ukraine
  • Türkçe
  • Русский
  • Other
  • Austria
  • Belgium
  • Bulgaria
  • Croatia
  • Cyprus
  • Czech Republic
  • Denmark
  • Estonia
  • Finland
  • France
  • Germany
  • Greece
  • Hungary
  • Ireland
  • Italy
  • Latvia
  • Lithuania
  • Luxembourg
  • Malta
  • Netherlands
  • Poland
  • Portugal
  • Romania
  • Slovakia
  • Slovenia
  • Spain
  • Sweden
  • USA

Request information from the manager

Please provide your contact information, the manager will send you detailed information on the selected tariff.

mail mail

Thank you for your request

Manager will contact you as soon as possible.

I've hosted an average of 8-10 domains with INTROSERV since May 2004. Their pricing attracted me at first, but it could only have been the quality of customer support that has retained me for this length of time. My IT knowledge level is best described as dangerous. I am confident that I have created more than my share of "situations." Yet the guys and gals at INTROSERV have patiently and determinedly handled my problems and resolved all issues on a continuing basis. If you're looking for web hosting, things are going to go wrong wherever you go. That's just the nature of humans and our technology. You had better go with an outfit that can resolve your problems in a timely and professional manner. INTROSERV just did that for me again, prompting me to write this long overdue recommendation