Jenkins cost 2026
./jenkins --free-software --real-infra-cost
Jenkins is free, the marketing tagline goes. The software is. Running it is not. The total cost of ownership for a Jenkins deployment splits across cloud infrastructure, plugin maintenance, security patching, and the engineer-hours nobody costs out properly. This page works through what a Jenkins setup actually costs in 2026.
Cloud infrastructure cost / public list rates
| Setup | Configuration | AWS / month | GCP / month | Best for |
|---|---|---|---|---|
| Small | 2 vCPU / 4 GB / 50 GB SSD | ~$35 | ~$32 | Solo / 2-3 devs |
| Medium | 4 vCPU / 8 GB / 100 GB SSD | ~$80 | ~$73 | Small team, 5-10 devs |
| Large | 8 vCPU / 16 GB / 200 GB SSD | ~$180 | ~$165 | Mid team, controller + 2 agents |
| HA | 3 controllers + 4 agents | ~$700 | ~$640 | Enterprise / regulated |
# Numbers reflect on-demand list pricing. Reserved Instances or Committed Use Discounts can cut 30-50%.
The hidden costs nobody quotes
Plugin maintenance
4-8 hours / month routine. Plugins drift, breaking pipelines on upgrade. Budget operator time or accept fragile builds.
Security patching
Jenkins issues regular security advisories. 1-2 emergency patching windows per year. Skip them and you become a CVE.
Major upgrades
Jenkins LTS major versions every 12-18 months. Plugin compatibility breaks. Plan for a 1-2 day outage every couple of years.
Worked example / 20 dev team running self-hosted Jenkins
# 1 controller (m5.large) + 4 agents (t3.medium)
controller_aws = $70 / mo
4 agents @ ~$30 = $120 / mo
storage (artifacts, EBS) = ~$25 / mo
networking + backups = ~$15 / mo
infra_subtotal = $230 / mo
# operator time (typical loaded $100/hr)
plugin / core maintenance = 6 hrs/mo = $600 / mo
# total monthly
monthly_tco = $830
Compare against GitHub Actions Team for the same team (around $180/month at the post-January-2026 rate of $0.006 per Linux minute). Jenkins costs more in cash terms but you control the entire stack and don't pay per-minute fees, useful when your build volume is high or your data must stay on your network.
Managed Jenkins alternatives
- CloudBees CI / enterprise managed Jenkins. Sales-led pricing, typical floor ~$40K/year for 25 users.
- AWS CodeBuild / Jenkins-compatible buildspec on AWS-managed compute. From $0.005 per build-minute on small instances.
- Jenkins X / Kubernetes-native open source. Free software, but operating Kubernetes is its own cost.
Compare with hosted CI/CD
Frequently Asked Questions
# click any question to expand
Is Jenkins really free?>
The Jenkins controller and agents are open source under MIT licence. Zero per-seat or per-minute fees. Everything else costs money: cloud servers to run the controller and agents, an engineer's time to install plugins and patch CVEs, and disk space for build artifacts and Jenkinsfiles. A typical mid-size Jenkins setup ends up at $200 to $700 per month in infrastructure plus 4 to 20 hours per month of admin time.
What's the cheapest way to run Jenkins?>
A single t3.medium EC2 instance ($35/month on-demand or $20/month Reserved) running both controller and one ephemeral agent is the cheapest viable setup. It works for small teams with low parallelism. Push past 5 concurrent jobs and you'll need separate agent instances. Spot instances on AWS or preemptible VMs on GCP can cut compute costs 60-80% if your jobs tolerate restarts.
When should I pick Jenkins over hosted CI/CD?>
Three scenarios. (1) You have strict data-residency or compliance rules that prevent code leaving your network. (2) You're at very high build volume (80,000+ minutes per month) where per-minute fees add up faster than infrastructure. (3) You need deep customisation that hosted platforms don't expose. For everyone else, hosted is cheaper once you factor in engineering time.
What does CloudBees CI cost?>
CloudBees CI is the enterprise managed Jenkins distribution. Pricing is sales-led but typical contracts start around $40,000 per year for a 25-user package and scale up. CloudBees provides a hardened Jenkins, RBAC, multi-controller orchestration, and support. It's a fit for regulated industries and large enterprises that already standardised on Jenkins.
What about plugin and security maintenance?>
Jenkins has 1,800+ plugins and most teams use 30-100. Plugin compatibility breaks across major Jenkins releases, and security advisories arrive every few weeks. Budget 4-8 hours per month of operator time for routine plugin and core upgrades, plus an emergency patching window roughly twice per year. Skip this and you accumulate technical debt that eventually costs more to fix.
Are managed Jenkins alternatives worth it?>
AWS CodeBuild offers Jenkins-compatible build environments at $0.005 per build-minute on the smallest instance type, with no infrastructure to manage. It's a good fit for teams who like Jenkinsfiles but don't want to operate Jenkins. CloudBees CI is the high-end option. Most teams who have already invested in Jenkins infrastructure stay self-hosted because the migration cost outweighs the savings.