Softwr

Software · pricing

Jenkins pricing

Jenkins publishes 2 tiers. Below is each one, what it adds over the tier beneath it, and where the ladder stops being worth climbing for most people.

Entry price
Free
Model
Open-source
Tiers
2
Free tier
Yes

Jenkins plans, side by side

Every published tier in ascending order of price, with the number of features each one lists. An absence here means the record does not itemise it, not that the tier lacks it.

Jenkins pricing tiers
PlanPriceFeatures listedStep up from the tier below
Open SourceFree5Entry tier
CloudBees CIOn request5Priced on request

What each tier adds

The set difference between each tier's feature list and the one beneath it. Where a tier lists nothing new, the vendor has either stopped repeating the inherited list or the tier raises limits rather than adding capability, the record does not distinguish the two, so this page does not either.

Open Source

Free

The entry tier. It covers unlimited builds, 1000+ plugins, self-hosted, community support, full source access.

CloudBees CI

On request

Over Open Source, this tier adds:

  • Enterprise features
  • High availability
  • Role-based access
  • Professional support
  • Managed service options

Where Jenkins stops being free

Open Source, Free

  • Unlimited builds
  • 1000+ plugins
  • Self-hosted
  • Community support
  • Full source access

No paid tier on record

Jenkins lists a free tier and no priced tier above it in the record we hold.

What the product covers

The full Jenkins feature record, grouped as the catalogue groups it. This is the product as a whole; the record does not map every feature onto a specific tier.

Core

  • Continuous integration
  • Continuous delivery
  • Pipeline as code
  • Distributed builds
  • Plugin ecosystem
  • REST API
  • CLI tools
  • Build triggers

Integrations

  • GitHub
  • GitLab
  • Bitbucket
  • Docker
  • Kubernetes
  • AWS
  • Azure
  • Slack

Security

  • LDAP
  • Active Directory
  • RBAC
  • SSL

Deployment

  • On-premise deployment
  • Cloud deployment
  • Hybrid deployment

Platform

  • Linux support
  • Windows support
  • Macos support
  • Docker support

Localization

  • English language support
  • Japanese language support
  • Chinese language support
  • French language support
  • German language support

People bring Jenkins in for ci/cd pipelines, automated testing, build automation, deployment automation, infrastructure as code. If that is not the job you are buying for, the alternatives to Jenkins are worth a look before you commit to a tier.

Before you pay for Jenkins

Three things this page cannot tell you, and all three change the bill. The record carries a price and a billing period but not the unit - per-seat and flat-rate pricing are indistinguishable in this data, so a five-person team may be looking at five times the figure above. It carries no annual rate, so any discount for paying yearly is not something this page can quote. And it carries no trial length.

What it can tell you is the shape of the ladder: 2 tiers between Free and On request, with the jump itemised above. Because there is a free tier, the cheapest way to answer the rest is to use it before paying anything.

Jenkins runs on linux, windows, macos, docker, and is published by Jenkins Project of Open Source. The full record is on the Jenkins review.

Jenkins pricing on the vendor's own site

Jenkins pricing questions

How much does Jenkins cost?
Jenkins publishes 2 tiers, from Free for Open Source up to On request for CloudBees CI. The entry tier costs nothing.
Does Jenkins have a free plan?
Yes. The Open Source tier costs nothing and covers unlimited builds, 1000+ plugins, self-hosted.
What is the difference between Open Source and CloudBees CI on Jenkins?
CloudBees CI costs On request against Free, and adds enterprise features, high availability, role-based access, professional support.
What am I actually paying for with Jenkins?
The record lists 32 features across 6 areas: core, integrations, security, deployment, platform, localization. In practice it is brought in for ci/cd pipelines, automated testing, build automation.
Does Jenkins charge per user?
The record carries a price and a billing period for each of its 2 tiers, but not the unit that price is charged in. Per-seat and flat-rate billing look identical in this data, so check the vendor's page before budgeting for a team.
Are these Jenkins prices current?
They are what the catalogue entry holds, refreshed when the entry is. Vendors change pricing without notice and nobody at Softwr re-verifies each tier by hand, so treat this as a structured summary and the vendor's own pricing page as the authority.
What should I compare Jenkins against before paying?
Nothing else in this directory is filed close enough to Jenkins to make a useful price comparison.

Related pages