CloudBees CI is CloudBees' commercial, centrally managed distribution of Jenkins for Kubernetes and traditional platforms; these pages cover running open-source Jenkins instead.
What CloudBees CI adds on top of Jenkins, such as the operations center, centrally managed controllers, role-based access control and active/active high availability, and what open-source Jenkins with Configuration as Code and the Kubernetes plugin covers without a license.
Moving controllers from CloudBees CI back to community Jenkins: inventorying CloudBees-only plugins, replacing operations center and RBAC with Configuration as Code and open-source authorization plugins, keeping Jenkinsfiles, and planning the license end date.
Cost of ownership by component: per-controller CloudBees CI licensing and support against open-source Jenkins with infrastructure, plugin upkeep, upgrades and a support partner, and which CloudBees features you would have to rebuild or buy elsewhere.
For organizations running many Jenkins controllers: replacing the CloudBees operations center with Configuration as Code, the official Helm chart, shared credentials from a secrets manager and a controller-per-team pattern, and the governance gaps that remain.
CloudBees CI active/active HA keeps builds running across controller replicas. This page covers what open-source Jenkins offers instead, a primary and backup controller behind a proxy, controller sharding and ephemeral Kubernetes agents, and the downtime each design accepts.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.