No more typing reviews! Try our Samantha, our new voice AI agent.

CloudBees vs LaunchDarkly comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CloudBees
Ranking in Feature Management
1st
Ranking in AI Software Development
10th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
20
Ranking in other categories
Build Automation (7th), Configuration Management (10th), Value Stream Management Software (2nd), DevSecOps (4th), AI-Augmented Software-Testing Tools (2nd)
LaunchDarkly
Ranking in Feature Management
3rd
Ranking in AI Software Development
15th
Average Rating
7.8
Reviews Sentiment
5.8
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Feature Management category, the mindshare of CloudBees is 17.0%, down from 32.1% compared to the previous year. The mindshare of LaunchDarkly is 18.3%, down from 19.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Feature Management Mindshare Distribution
ProductMindshare (%)
CloudBees17.0%
LaunchDarkly18.3%
Other64.7%
Feature Management
 

Featured Reviews

KishoreKumar4 - PeerSpot reviewer
Senior Qe Lead at Cognizant
Consistent automation has improved deployments and supports efficient client-facing workflows
Deployment and other processes are feasible for me, making this a smooth process. The integration part is good. We can use multiple things by integrating with CI/CD pipelines, and this is very feasible for us. This allows us to do our work easily. The productivity is very good. CloudBees is a good and efficient tool. We can work in client-facing scenarios, and since clients have provided these types of tools, we are able to work on them effectively.
reviewer2769948 - PeerSpot reviewer
Staff Software Engineer at a wholesaler/distributor with 10,001+ employees
Has increased developer confidence by enabling safe production releases using targeted feature toggles
I wish we were using more targeting in our feature toggles and I wish we were using more feature toggles as well as feature toggle dependencies. Making one feature toggle or one set of feature toggles dependent on another one would allow us to turn them all on or turn them all off at one time. For improvements in LaunchDarkly, managing team members and access to those team members was challenging. We could add team members through Terraform and do it programmatically, and then modify it through the user interface. However, once we started modifying things through the interface, we weren't able to go back to using any configuration programmatically for the team members. It made it challenging to orchestrate team member management. The other aspect I wasn't particularly fond of was when they started adding AI to the interface and deployment interface. It reminded me of old school wizards when installing software and simplified the interface too much, removing some of the engineering control I preferred.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I find the automation feature most valuable. CloudBees is highly scalable and supports both small and large teams. The deployment process is also faster when compared to on-premise."
"Scalability largely depends on how the tool is set up within your infrastructure"
"The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar, management master to CloudBees, Blue Ocean, JobConfig, and support."
"One recent product feature that stands out is the pipeline explorer, which is providing significant value for us right now."
"The solution's most valuable feature is its flexibility."
"CloudBees's user interface is very simple and user-friendly."
"The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."
"CloudBees is the Jenkins tool for building and deploying. There's open-source Jenkins, which is free and can be used by any organization, but it offers a different architecture for Jenkins. If your organization is larger, you might choose the architecture. This way, you can have different masters for different applications, and different teams can manage their masters separately. However, a single person can still control all the masters, whoever manages it for the organization."
"I appreciate that we can release any feature in production and maintain control over it."
"The setup is easy."
"From the development side, it allows us to manage multiple things."
"The initial setup is very easy."
"The best feature LaunchDarkly offers is the capability of having a feature flag that we don't have to build in-house."
"It has really helped during the series of product lines and faster deployment and faster development."
"These features in my current project have helped my team because they allow us to specifically target users to start turning on functionality, we can monitor the behavior and make sure that it's behaving as expected when the feature toggle is turned on, and then we can increase the usage."
"I like that it offers the ability to control the flags."
 

Cons

"If you're logged in and working for about thirty minutes and then go idle for five to ten minutes, Jenkins will prompt you to re-authenticate."
"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"There could be improvements in the ease of use."
"A lot of stability issues are there with CloudBees."
"The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times."
"To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture."
"We've noticed occasional issues with folder permissions changing unexpectedly. Specifically, permissions sometimes shift from the CloudBees user to the root user. This can cause pipeline failures, as pipelines require the correct CloudBees user permissions to execute properly."
"The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it."
"Fetching information about multiple flags in a single action would be beneficial."
"We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns."
"The feature where one feature flag is dependent on another could be explored more for our usage."
"When the system has an excessive number of feature flags, managing them can become cumbersome."
"I think LaunchDarkly's customer support can be improved as it is not responsive."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
"Managing team members and access to those team members was challenging. We could add team members through Terraform and do it programmatically, and then modify it through the user interface. However, once we started modifying things through the interface, we weren't able to go back to using any configuration programmatically for the team members."
"Right now, no improvements are needed."
report
Use our free recommendation engine to learn which Feature Management solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
17%
Construction Company
16%
Outsourcing Company
6%
Construction Company
14%
Outsourcing Company
10%
Financial Services Firm
9%
Real Estate/Law Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise18
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise5
 

Questions from the Community

What needs improvement with CloudBees?
For CloudBees, I can suggest that the log is very high, which is very hectic for us when trying to find which error is coming. This creates complexity. If possible, we could sort the logs so we can...
What is your primary use case for CloudBees?
We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.
What advice do you have for others considering CloudBees?
We can upload the JAR file and deploy at the Jenkins level during our deployment. These types of labels and IDs can be deployed using CloudBees. Once we click to start the build, it automatically r...
What is your experience regarding pricing and costs for LaunchDarkly?
My experience with pricing, setup cost, and licensing is that pricing is great, affordable, and fair.
What needs improvement with LaunchDarkly?
LaunchDarkly can be improved by managing old flags. We have an issue with old flags; it became very messy very fast and we need to be very disciplined about managing these flags. I also heard from ...
What is your primary use case for LaunchDarkly?
My main use case for LaunchDarkly is feature flagging and gradual rollouts. Instead of releasing a new feature to all users at once, we can first enable it for internal users, then for a small grou...
 

Comparisons

 

Overview

 

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Information Not Available
Find out what your peers are saying about CloudBees vs. LaunchDarkly and other solutions. Updated: April 2026.
900,644 professionals have used our research since 2012.