Deploy Jenkins in one click
The open-source CI/CD standard, ready in minutes
Jenkins is the leading open-source automation server – it builds, tests, and deploys your code on every commit.
-
Pipeline as code with Jenkinsfile -
2000+ community plugins -
Git, GitHub, and GitLab integration -
Webhook and scheduled build triggers -
Distributed builds across agents -
Built-in credentials management
Installs withyour VPS
Full rootaccess
Live in~2 minutes
Updates viaapt
Key features
Define builds in a Jenkinsfile with declarative or scripted syntax – pipelines live in your repository and version with your code.
The largest CI ecosystem there is – SCM, build tools, test reports, notifications, and cloud providers, all one install away.
Jenkins discovers branches and pull requests in your repository and runs each against its own Jenkinsfile automatically.
Offload builds to agents over SSH as your load grows – the controller stays responsive while workers do the heavy lifting.
Matrix-based authorization, encrypted credential storage, and pluggable authentication – from local accounts to LDAP and SSO.
Trigger jobs, query build status, and manage configuration from scripts – automate the automation server itself.
System requirements
View All VPS Options
Get started in 4 easy steps
-
1
Select a VPS plan
Choose the virtual server resources and performance tiers that fit your project requirements.
-
2
Pick your application
Browse our marketplace during VPS setup and select the self-hosted software you want to deploy.
-
3
Complete the payment
Pay the standard virtual server invoice – the 1-click deployment tool itself is fully complimentary.
-
4
Complete and access
Your server provisions and automatically installs the software. Once the setup process finishes, your new environment is fully ready for you to connect and use.
Deployment details
Application
Jenkins automation server – latest release
- Native package, updates arrive through apt
- Guided setup wizard on first login – pick your plugins, create your admin user
Operating system
Ubuntu 24.04 LTS – clean minimal install
- Native packages, no containers
- Full root access over SSH
Web access and SSL
Nginx reverse proxy serving Jenkins over HTTPS
- Self-signed certificate enabled by default
- A setup-ssl script issues a free Let's Encrypt certificate
Java runtime and service
Everything Jenkins needs to run as a system service
- OpenJDK 21 preinstalled – matches the official Jenkins requirement
- Runs under systemd, starts automatically on boot
Software licensing
MIT – open-source, no license fees
- No job limits, user limits, or paid tiers
- Full MIT license text
Why deploy on INTROSERV
-
NVMe storage
Every VPS runs on NVMe drives – fast I/O for databases, metrics, and busy workloads.
-
Locations in Europe and the US
Deploy close to your infrastructure and users – lower latency, regional compliance.
-
Unmetered traffic
No bandwidth caps and no overage bills – your monthly price stays predictable.
-
IPv4 and IPv6 included
A dedicated IPv4 address plus native IPv6 with every server.
-
24/7 human support
Engineers on duty around the clock – real answers, not ticket bots.
-
Scale anytime
Upgrade CPU, RAM, or storage as your workload grows – without migrating.
Terms and support boundaries
Infrastructure and support limits
Our company provides the Virtual Private Server infrastructure and the automation script for initial deployment. While we guarantee the availability and performance of your hardware and network, our technical support exclusively covers infrastructure-related issues – such as server connectivity, hardware stability, and billing. Assistance with application-specific configuration, software bugs, or user management is the responsibility of the server administrator or software maintainers.
Software licensing and compliance
All marketplace tools deploy standard versions of third-party software products and are provided "as-is" with no modifications to their original code. While the core of many available applications is open-source, using proprietary features or advanced enterprise tiers in production environments may be subject to the vendor's specific licensing terms. Users must manage and acquire any required commercial subscriptions directly from the software developers.
FAQ
-
Do I need a license to run Jenkins?
No. Jenkins is fully open-source under the MIT license – no paid editions, job limits, or feature gates. You only pay the standard virtual server invoice.
-
How do I log in after deployment?
Open the web interface URL from your INTROSERV panel – the initial administrator password is shown there as well. Enter it on the Unlock Jenkins page, then the setup wizard walks you through installing plugins and creating your own admin account. The whole first-run setup takes a few minutes.
-
Which plugins get installed?
You decide during the setup wizard – install the suggested set that covers the most common CI workflows, or hand-pick only what you need. Any of the 2000+ plugins can be added later from Manage Jenkins without reinstalling anything.
-
How do I get a valid SSL certificate?
The server ships with a self-signed certificate enabled by default. To issue a free Let's Encrypt certificate for your own domain or the server's FQDN, connect over SSH and run the setup-ssl script in the console – one command, no manual configuration.
-
Can I migrate my existing Jenkins installation?
Yes. Jenkins keeps everything – jobs, plugins, credentials, and build history – in its home directory (/var/lib/jenkins). Stop Jenkins on both servers, copy the directory over, and start the service. Keep the Jenkins versions close during the move to avoid plugin compatibility issues.
-
How are updates handled?
The server tracks the official Jenkins apt repository, so core updates arrive through the standard package manager, and plugin updates through the Jenkins UI. You have full root access and decide when to apply them – nothing updates behind your back.
-
Do builds run on this server or somewhere else?
By default, builds run on the controller itself – fine for solo and small-team use. As load grows, connect additional machines as build agents over SSH so the controller stays responsive while agents execute the jobs. Any VPS or existing server can act as an agent.
-
What if I outgrow my configuration?
Upgrade CPU, RAM, or storage of your VPS as your build load grows – no reinstallation needed. Disk usually fills first: build history, workspaces, and artifacts accumulate, so set retention policies per job and revisit your plan when parallel builds start queuing.
