CI/CD Server — from €5.49/mo
Automate builds and deployments on your own server — runners, pipelines and a registry, with a 5-hour test period before payment, completely risk-free
Launch CI/CD now
A CI/CD server is a virtual server with full root access running your own build, test and deployment pipeline. Builds are bound by cores and disk: several parallel jobs run comfortably on 10 vCPU and 16 GB RAM (Power 1, €17.99/mo), while occasional pipelines fit 8 vCPU and 8 GB (Standard 4, €10.99/mo); the line-up starts at €5.49/mo. Reserve separate space for dependency cache and artifacts — 160 GB NVMe or more, otherwise the disk fills up within the first month of active builds. A self-hosted runner beats cloud minutes on cost when builds are constant, and it keeps your keys and secrets on your side. A 5-hour test period before payment lets you run a real pipeline first. All plans are on the VPS hosting page.
Plans
VPS for CI/CD
Occasional builds of a small project fit Standard 4 — 8 vCPU, 8 GB RAM and 100 GB NVMe for €10.99/mo. An active pipeline with parallel jobs calls for Power 1 (10 vCPU, 16 GB, 160 GB) at €17.99/mo — the space goes to cache and artifacts. 5-hour test period before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Your own pipeline
Install GitLab Runner, Jenkins or another tool — the build and deployment pipeline stays fully under your control.
Runners and jobs
Run runners and parallel jobs on the server — builds, tests and deployments trigger automatically on every push.
Full control
Root access, your own image registry, dependency cache, your own keys and secrets — the whole pipeline is on your side.
How to set up CI/CD on a VPS
Choose a plan and an image
Estimate the number of parallel jobs and the cache space, take anything from Standard 4 (8 vCPU) to Power 1 (10 vCPU, 160 GB), and select a Linux image: Ubuntu, Debian or another.
Install the OS yourself
Through the panel you deploy the chosen OS on a KVM server yourself — so the configuration stays fully under your control.
Build your pipeline
Over SSH or the KVM console install a runner or Jenkins, describe the pipeline and connect the image registry and deployment.
A server for your pipeline
We will help you size a plan for your builds: how much vCPU and RAM the runners need, and how much NVMe space to reserve for dependency cache and artifacts.
We can also help with runners, an image registry and HTTPS via Let's Encrypt. There are dedicated pages for specific tools: GitLab VPS and Jenkins VPS; for building and running containers see the Docker server.
Get sizing adviceFrequently asked questions
Did not find your answer?
Write to us via the contact page form.
Any — GitLab Runner, Jenkins, Drone and others. You install the tool you need yourself on a server with root access.
Yes, you set the number of runners and concurrent jobs yourself. For several parallel builds take Power 1 — 10 vCPU and 16 GB RAM at €17.99/mo.
A runner that compiles projects needs cores: 10 vCPU and 16 GB (Power 1, €17.99/mo) handle several parallel builds. Light pipelines fit 8 vCPU.
Yes. The pipeline runs on your VPS: keys, secrets and artifacts are stored on the server under your control.
Self-hosted is cheaper with constant builds and gives full control over the environment and cache. Cloud minutes win when builds are rare.
On the server's disk or in your own image registry. Reserve 160 GB or more for artifacts and cache — otherwise the disk fills up in the first month of active builds.
Yes, via the KVM console: it attaches to the server at the hardware level and works even when SSH is down or the system fails to boot.
Cache dependencies on NVMe and spread jobs across runners in parallel — we can help with the basic pipeline setup.