GitLab runner hosting: your own runners on root vServers
Long queues, scarce compute minutes or builds that slow down your GitLab server? With your own GitLab runner on a root vServer, your pipelines run on guaranteed CPU cores and dedicated memory. We set up the runner with Docker and connect it to your GitLab – whether GitLab.com, a GitLab server with us or your own instance.
You get a root vServer with guaranteed resources on which we set up GitLab Runner and Docker – including Docker-in-Docker for image builds. After that you manage the server yourself with full root access. For runners with GPUs or as a managed service we prepare a custom quote.
GitLab runner from 25,51 € / month incl. VAT
- Root accessfull control over your runner
- Dockerincluding Docker-in-Docker
- Setup includedrunner registered and ready
- Made in GermanyISO/IEC 27001 certified, GDPR compliant
Which server fits your pipelines?
What matters is the number of parallel jobs and how compute-intensive your builds are. You can move to a larger server at any time.
| Use case | Server | Resources | Storage | Price/month |
|---|---|---|---|---|
| Single projects, smaller builds and tests | VS150 | 2 CPU cores · 4 GB RAM | 80 GB NVMe | 25,51 € |
| Teams with several pipelines and Docker image builds | VS250 | 4 CPU cores · 8 GB RAM | 160 GB NVMe | 46,46 € |
| Parallel jobs, large test suites and container builds | VS350 | 8 CPU cores · 16 GB RAM | 320 GB NVMe | 91,62 € |
| Many parallel jobs and large code bases | VS450 | 16 CPU cores · 32 GB RAM | 640 GB NVMe | 170,16 € |
| GPU, managed runners or several runners | Custom | as required | – | on request |
Root vServers for your GitLab runner
Monthly prices incl. 19% VAT, minimum term 3 months. Setting up the runner is included.
How your runner joins your pipelines
- Order the server
You choose the right root vServer and order via our form. - Create the runner
You create a runner in GitLab and send us the runner token. - Setup by us
We install GitLab Runner and Docker and register the runner with your GitLab. - Start your pipelines
Your jobs run on the new runner. From then on you manage the server yourself with root access.
What you get
Your own root vServer
guaranteedGuaranteed CPU cores, memory and fast NVMe storage just for your builds – no other customers slow you down.
Runner setup
includedWe install GitLab Runner and Docker and register the runner with GitLab.com, a GitLab server with us or your own instance.
Docker-in-Docker
DockerBuild Docker images directly in the pipeline. Every job runs in its own container with the image you specify.
Full root access
rootYou adapt the runner, caches and build tools yourself. You install updates yourself or book our update service.
Separate from GitLab
secureCompute-intensive or faulty builds do not affect your GitLab server. The runner opens its connection itself.
Servers in Germany
includedUnlimited traffic and operation in German data centres – your source code is built in Germany.
More than one runner? On request
For special requirements we design your build environment individually.
Update service
11,90 € / monthWe add your runner server to our update system and install the package updates of the operating system, Docker and GitLab Runner – on RPM-based systems such as AlmaLinux, Rocky Linux, CentOS Stream and Fedora.
Managed runners
on requestYou would rather hand over operation completely? On request we run your runners as a managed service. Send an enquiry
GPU runners
on requestFor AI models, rendering or compute-intensive tests we provide runners with GPUs. Send an enquiry
Root servers on the VEP Cloud
hourlyIn the VEP Self-Service Cloud you create servers with root access yourself and pay by the hour – for example for additional runners at peak times. Self-Service Cloud
GitLab server
from 101,15 €Repositories, merge requests and CI/CD in one tool – your own GitLab server, looked after by us. GitLab server
Why LCube – Professional Hosting?
We have been running development and project environments for teams for many years – secure, reliable and with personal support.
ISO/IEC 27001 certified
LCube itself is certified to ISO/IEC 27001. Information security is an audited standard in our own processes – not just in the data centre. More about our certification
Made in Germany
Our team works in Germany and your data is stored in German data centres. Operation is GDPR compliant.
Personal support
You talk directly to experienced specialists who know your system and personally take care of your request.
Since 1995
More than 30 years of hosting experience – from websites and online shops to development environments and business-critical servers.
Custom solutions
Whether a single server, a cluster or a special setup with VPN connection to your company network: we design the environment that fits your requirements.
Our own cloud platform
With the Virtuozzo Enterprise Cloud (VEP) we run our own cloud platform made in Germany – for highly available and business-critical workloads.
Frequently asked questions about GitLab runners
What is a GitLab runner?
A GitLab runner is the software that executes the jobs of your GitLab pipelines. It asks GitLab for new jobs, builds and tests your software and reports results and artefacts back. The runner works separately from GitLab, so you can run it on your own server with guaranteed resources. With us it runs on a root vServer in Germany, and we take care of setting it up with Docker.
Does the runner also work with GitLab.com?
Yes. Your runner can be registered with GitLab.com, with a GitLab server from LCube or with your own GitLab instance. It opens the connection itself via HTTPS, so your GitLab needs no access to the runner. Jobs on your own runners do not use compute minutes from your GitLab.com quota. This lets you build more often and faster without moving to a larger GitLab.com subscription.
Can I build Docker images in the pipeline?
Yes. We set up the runner with the Docker executor: every job runs in its own container with the image you specify in your .gitlab-ci.yml. Docker-in-Docker is possible, so you can build images directly in the pipeline and push them to your container registry. Because you have root access, you adjust caches, images and the number of concurrent jobs yourself or add further executors such as shell.
Who takes care of updates?
We set up the runner and Docker. After that it is your choice: with our update service for 11,90 € per month we add the server to our update system and install the package updates of the operating system, Docker and GitLab Runner from the repositories – on RPM-based systems such as AlmaLinux, Rocky Linux, CentOS Stream and Fedora. The update service is not available for runners on Ubuntu. You schedule restarts yourself. If you run your own GitLab instance, keep it up to date so that the runner and GitLab versions match. Without the update service you install updates yourself with root access.
Which server size do I need?
That depends on how many jobs run at the same time and how compute-intensive your builds are. For single projects and tests VS150 is often enough; for teams with several pipelines and Docker builds we recommend VS250. Large test suites, parallel jobs and container builds benefit from VS350 or VS450. You can move to a larger server at any time. We are happy to look at your pipelines. Ask for advice
Can I also run runners on the VEP Cloud?
Yes. In the VEP Self-Service Cloud you create virtual servers yourself and manage them with root access; you install and register GitLab Runner and Docker there yourself. Access is free of charge, and the resources you use are billed by the hour. This suits additional runners at peak times or teams that create servers automatically via the OpenStack-compatible interface. For runners that run permanently and are set up by us, a root vServer is usually the simpler choice. VEP Self-Service Cloud
Why does the runner not run directly on the GitLab server?
Builds need a lot of CPU and memory and execute third-party code, such as dependencies from public package sources. If they run on the GitLab server, they slow down repositories and the web interface and increase the attack surface. That is why we always run runners separately from GitLab. A faulty or very long build then only affects the runner, while your team keeps working in GitLab undisturbed.
What is the contract term?
The minimum term is 3 months. You pay for the root vServer for your runner monthly or yearly, all prices including 19% VAT; you will find the yearly prices with each server. Setting up GitLab Runner and Docker is included. If you need more performance later, you move to a larger server. If you have questions about the contract, our specialists are happy to advise you personally.
Where are the servers located?
In German data centres. LCube itself is certified to ISO/IEC 27001, and operation is GDPR compliant. Your source code is therefore built and tested in Germany, and deployment credentials do not leave the country – an important point for companies with compliance requirements. Our team is based in Germany too: when you have questions, you reach experienced specialists rather than a call centre. We have been providing hosting for businesses since 1995.
Your own GitLab runner
Choose your server or let our specialists advise you.