CloudBees Licensing Explained: What It Costs and Who Counts as a User
This page answers the CloudBees licensing questions buyers actually ask — what the products are now called, what CloudBees CI costs, and why the quote is so often larger than expected. Figures are in USD.
The short answer: CloudBees CI is licensed per named user, and CloudBees’ definition of a user includes anyone who commits to a source control system that triggers a job — whether or not they ever open Jenkins. For an organisation with 400 committers and 30 people who actually use Jenkins, the licensable population is 400. That single definition changes more quotes than any other factor.
What is CloudBees selling in 2026?
CloudBees has repositioned repeatedly and the naming is genuinely confusing. Current state:
| Name | Status |
|---|---|
| CloudBees Unify | Current SaaS flagship. Was “CloudBees platform”. An operating layer over your existing toolchain — connects to GitHub Actions and Jenkins rather than replacing them |
| CloudBees CI | Current, self-managed. Formerly CloudBees Core, before that CloudBees Jenkins Enterprise |
| CloudBees CD/RO | Current. Originally Electric Cloud ElectricFlow |
| CloudBees Build Acceleration | Current, on a traditional EOL schedule |
| CloudBees Smart Tests | Current, from the Launchable lineage |
| CloudBees Compliance | No longer standalone — now a capability inside Unify |
| CloudBees Feature Management | Labelled “legacy” in CloudBees’ own docs. Successor capability lives in Unify |
| CloudBees CodeShip | Retired |
If you are reading a proposal or an old contract, the rename chain that matters is CloudBees Jenkins Enterprise → CloudBees Core → CloudBees CI. Same product line, three names.
What does it cost?
There are two entirely different pricing models, which is the second source of confusion.
CloudBees Unify (SaaS) — published
| Tier | Price | Users | Workflow minutes |
|---|---|---|---|
| Free | $0 | 5 | 2,000/mo — workflows pause when exceeded |
| Team | $30/user/month | 25 | 10,000/mo, then $0.01/minute |
| Enterprise | Quote | — | Custom |
Unify also meters storage and egress per GB, and — for feature flags — Client-Side Users, which count unique client instances rather than people. One person on three devices counts three times. If you are using Unify for feature management against a large end-user fleet, that meter scales with your customers, not your team.
CloudBees CI (self-managed) — quote only
CloudBees publishes no list price for CloudBees CI. Its pricing page is a quote-request form with no figures. The only genuinely published figure we could find is a cloud marketplace listing at $12,000 per year for 10 users — roughly $100 per user per month — and that is a private-offer listing referencing an older support tier name, so treat it as a ceiling rather than a price. Real deals are negotiated and volume-discounted. Contact us for details or a special quote.
For scale comparison: at that anchor, CloudBees CI self-managed is roughly 3.4× GitLab Premium at $29 per user per month. But the effective gap is usually much wider, because of how the two count users.
Who counts as a licensed user?
CloudBees defines a user as any individual or machine authorised to log into and use the products or to perform code commits into a source control management system triggering jobs. No login is required. Read-only viewers who can log in count. New hires and the people they replaced count separately.
Practical consequences worth establishing before you get a quote:
- Committers count even if they never touch Jenkins. This is the number one reason CloudBees quotes surprise people.
- Bots and service accounts count as machine users — with a useful carve-out: where an SCM uses a service account to trigger builds, the person who committed is counted rather than the automation.
- CloudBees can see your real number. The License Tracker plugin deduplicates identities across usernames, emails and SCM handles, and reports usage back to CloudBees to inform licensing discussions. Plan for that conversation rather than being surprised by it at renewal.
What CloudBees CI adds over open-source Jenkins
If you are weighing the licence against staying on community Jenkins, these are the capabilities that are genuinely hard or impossible to replicate yourself:
- Operations Center and managed controllers — central provisioning and management of many controllers, including across Kubernetes clusters. Open-source Jenkins has no cross-controller management layer at all.
- Active/active high availability — multiple controller replicas behind a load balancer with shared storage, so builds continue on another replica if one fails, plus rolling restarts with zero downtime. This is the hardest thing on the list to self-build and is frequently the actual purchase trigger.
- CVE backports. CloudBees commits to including fixes for critical security issues in each monthly release even if they are not yet in the community Jenkins release. Given that Jenkins advisories occasionally ship with no fix available for a plugin, this is the strongest single differentiator.
- Configuration-as-Code bundles distributed fleet-wide, rather than per-controller JCasC.
- Granular RBAC at system, folder and job level, administered centrally.
- Pipeline templates with constrained parameters, so a platform team can enforce consistency.
- Air-gapped support — documented and real, via a proxy artifact repository and plugin catalogs. For regulated and defence buyers this is often the whole reason for the contract.
Support tiers
| Priority | Free | Essentials | Advanced | Premier |
|---|---|---|---|---|
| P1 Urgent | Best effort | 2 hours | 1 hour | 30 minutes |
| P2 High | Best effort | 4 business hours | 3 business hours | 2 business hours |
| P3 Normal | Best effort | 8 business hours | 6 business hours | 4 business hours |
| P4 Low | Best effort | 2 business days | 2 business days | 1 business day |
All paid tiers cover standard business hours, plus 24/7 for P1 on Essentials and Advanced, and 24/7 for P1 and P2 on Premier. Ticket submission is 24/7/365 on every tier.
These are response targets, not resolution targets, and we could find no published resolution-time or uptime SLA for self-managed CloudBees CI. Ask for both explicitly. Also note that only Tier I and Tier II plugins are supported — running a plugin outside the CloudBees Assurance Program envelope puts that pipeline outside your support contract.
Where CloudBees contracts catch buyers out
Licence expiry is a hard stop
CloudBees documents that on expiry the software is blocked and you cannot access the instance until you renew. No grace period is documented. For a CI system, that is an outage, not an inconvenience — put the renewal date somewhere that gets watched.
Controllers carry time-bounded sublicences
Operations Center holds the licence; connected controllers receive auto-renewing sublicences valid in three-day increments. A controller severed from Operations Center for more than about three days will fail its licence. Standalone controllers not connected to Operations Center need their own licence entirely.
The trial is seven days
CloudBees CI offers a full-featured seven-day trial. That is not a realistic window in which to evaluate a controller migration and reconcile a plugin estate. Plan the evaluation before you start the clock.
True-up mechanics are not published
What happens if you exceed licensed users mid-term — automatic billing, blocked builds, or reconciliation at renewal — is not documented anywhere public. Negotiate it, along with a growth band, before signing.
Frequently asked questions
Is CloudBees CI the same thing as CloudBees Unify?
No, and this is the most common mix-up in current proposals. CloudBees CI is self-managed Jenkins-based CI, licensed per named user, quote-only. Unify is a SaaS operating layer over your existing toolchain, priced at $30 per user per month for the Team tier. They solve different problems and are bought separately.
Do we need CloudBees, or can we keep running Jenkins ourselves?
The honest test is whether you need active/active high availability, contracted CVE backports, air-gapped support, or fleet-wide configuration management. If none of those is a real requirement, community Jenkins plus disciplined operations may be sufficient. If HA or air-gapped operation is a hard requirement, self-building it is a much larger project than the licence.
How do we reduce the user count on a quote?
You largely cannot, because the definition keys off commits rather than logins. What you can do is establish the number accurately before the conversation, understand which repositories actually trigger CloudBees jobs, and negotiate volume banding and growth terms from an accurate baseline rather than a guess.
Which plugins will we have to give up?
Any plugin outside the CloudBees Assurance Program envelope — classified untrusted, or outside Tier I/II support. On a mature Jenkins estate with a long tail of niche plugins, reconciling this is the main source of unplanned migration work. Run the inventory before you commit to a date.
What is our exit cost if we leave?
Reverting to Jenkins LTS is documented, but you lose Operations Center, configuration-as-code bundles and HA. Ask the question before signing rather than at renewal.
Licensing terms and support SLAs verified 19 September 2026 against CloudBees’ published documentation and support terms. CloudBees CI pricing is quote-only and not published; the per-user figure referenced above comes from a cloud marketplace private-offer listing and should be treated as indicative. ReleaseTEAM is a CloudBees partner.
Get the user count right before the quote
We audit Jenkins estates ahead of a CloudBees conversation — the real committer population, the plugin envelope reconciliation, and whether HA is a genuine requirement or an expensive nice-to-have. It usually changes the number materially.