CloudBees CI vs GitLab CI/CD
CloudBees CI
cloudbees.comGitLab CI/CD
about.gitlab.comSide by side
| Figure | CloudBees CI | GitLab CI/CD |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 1 | 0 |
| Spec score · Continuous Integration Software | 8.7 (#6) | 6.0 (#56) |
| Founded | CloudBees was founded in 2010 by former JBoss CTO Sacha Labourey and colleagues. | 2011 |
Plans
In their own words
CloudBees CI
CloudBees CI is a centrally managed Jenkins environment for teams delivering continuous integration at scale. It can run on-premise or in the public cloud, with a modern cloud platform designed for Kubernetes and a traditional platform edition. Operations Center provides a central view across CI controllers. Pipeline capabilities include complex delivery pipelines, declarative syntax, and builds that can survive controller and agent failures. The CloudBees Assurance Program vets plugins, while Beekeeper helps administrators monitor and manage plugin upgrades. Documented integrations include GitHub and Bitbucket, plus Slack and Microsoft Teams. Security options include central management, role-based access control, single sign-on, and connections to external credential stores such as CyberArk and HashiCorp Vault. CloudBees CI is paid, with pricing available on request, and has no free plan. 24/7 expert support depends on the customer’s support agreement. CloudBees support policies cover only CloudBees-certified plugins on services based on Jenkins core.
GitLab CI/CD
GitLab CI/CD has no write-up on Specifiction yet; its figures are above.