Jenkins VPS — from €5.49/mo
Run your own Jenkins build server — pipelines, plugins and agents, with a 5-hour test period before payment, completely risk-free
Launch Jenkins now
A Jenkins VPS is a virtual server with full root access that hosts your continuous-integration controller: you install the JDK and Jenkins, describe builds in a Jenkinsfile, and attach plugins and agents. The controller itself is undemanding — several projects fit on Standard 4: 8 vCPU, 8 GB RAM and 100 GB NVMe for €10.99/mo. If builds run directly on the controller, plan for 16 GB and NVMe space for the dependency cache. Unlike a full platform, Jenkins stays a pure pipeline engine: repositories and the image registry live elsewhere. A 5-hour test period before payment is included. The full line-up is on the VPS hosting page, and the approaches are compared on VPS for CI/CD.
Plans
VPS for Jenkins
Occasional builds and a single project fit on Standard 1 — 4 vCPU, 4 GB RAM and 50 GB NVMe for €5.49/mo. Active CI with parallel jobs runs on Standard 4 (8 vCPU, 8 GB) for €10.99/mo, with heavy builds moved to a separate agent. 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 CI server
Install the Jenkins version you need on your own server — the controller, jobs and web interface stay fully under your control.
Pipelines and plugins
Describe builds in a Jenkinsfile, attach plugins and agents — tests and deployments run on your server.
Full control
Root access, artifact storage, HTTPS via a reverse proxy, your own users and server snapshots on your schedule — the server is entirely yours.
How to run Jenkins on a VPS
Choose a plan and an image
Size the configuration by the number of parallel jobs — from Standard 1 for occasional builds up to Standard 4 and beyond — and pick a Linux image with the JDK version you need.
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.
Deploy Jenkins
Over SSH or the KVM console install the JDK and Jenkins, set up a domain with HTTPS, attach plugins and create your first pipeline.
A server sized for your Jenkins
We will help you pick a plan for your builds: how much RAM and vCPU the controller and agents need, and how much NVMe space to reserve for artifacts and the dependency cache. The usual practice is simple — keep the controller small and give the resources to the agents.
We can also help set up HTTPS via Let's Encrypt and connect build agents. If you want repositories and a registry on one platform, see VPS for GitLab; for building images a Docker server comes in handy.
Get sizing adviceFrequently asked questions
Did not find your answer?
Write to us via the contact page form.
Jenkins is a build server only: repositories, the image registry and the issue tracker stay in external systems. GitLab installs as a whole platform and therefore needs noticeably more memory.
No, Jenkins is open-source software with no licence fees. You only pay for the server it runs on.
A controller with several projects runs on 8 vCPU and 8 GB — Standard 4 for €10.99/mo. If builds run directly on the controller, take 16 GB: Power 1 for €17.99/mo.
Yes. Jenkins runs on your VPS: builds, artifacts and configuration are stored on the server under your control.
Possible, but with heavy builds it is better to split them: the controller on a small plan, agents on a powerful one. The servers connect over a private network.
Restrict access by IP in the firewall and put Nginx with TLS in front of Jenkins. An openly exposed CI server is a common cause of breaches.
Connect through the KVM console: it works at the hardware level and stays available when the system fails to boot or SSH is closed.
Move heavy jobs to agents and keep the dependency cache on NVMe — we can help with the basic pipeline setup.