Try our new research platform with insights from 80,000+ expert users

Jenkins vs LaunchDarkly comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

Jenkins
Ranking in Build Automation
3rd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
No ranking in other categories
LaunchDarkly
Ranking in Build Automation
12th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
7
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Build Automation category, the mindshare of Jenkins is 10.4%, down from 13.5% compared to the previous year. The mindshare of LaunchDarkly is 0.4%. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Dinesh-Patil - PeerSpot reviewer
A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment
The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.
James Bayhylle - PeerSpot reviewer
Provides risk-free releases with control access and A/B testing
It allowed us to deploy faster. Despite having a rigorous code review process that slowed things down, once the code was reviewed, LaunchDarkly enabled safe deployments. If there was ever an issue, we could easily roll back a particular release by simply turning off the feature flag. When configuring and setting this up, begin with feature sets that are relatively small in scope. This helps build the necessary skills to leverage the product effectively while maintaining control over the blast radius, thus reducing risk to your customers and application in case of misconfiguration. As you gain more experience with the solution, it's crucial to have a process to manage feature flag sprawl, as mentioned earlier. Implementing a life cycle management system for your feature flags is essential. Overall, I rate the solution a nine out of ten because of its intuitiveness and ease of use.

Quotes from Members

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

Pros

"Jenkins is free and open source."
"The initial setup is simple."
"Jenkins is a very mature product."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"Has a good interface, is reliable and saves time."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load."
"This is a great integration tool and very powerful."
"I appreciate that we can release any feature in production and maintain control over it."
"It has really helped during the series of product lines and faster deployment and faster development."
"The initial setup is very easy."
"I like that it offers the ability to control the flags."
"From the development side, it allows us to manage multiple things."
"The ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit."
"The setup is easy."
 

Cons

"The solution could improve by having more advanced integrations."
"It would be helpful if they had a bit more interactive UI."
"Jenkins could improve the integration with other platforms."
"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"It could be cheaper."
"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns."
"Fetching information about multiple flags in a single action would be beneficial."
"When the system has an excessive number of feature flags, managing them can become cumbersome."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
"The feature where one feature flag is dependent on another could be explored more for our usage."
"Right now, no improvements are needed."
"I have used LaunchDarkly for around two and a half years and I haven't faced any issues with it."
 

Pricing and Cost Advice

"The solution is open source."
"Jenkins is an open-source tool."
"Jenkins is not expensive and reasonably priced."
"There is no cost. It is open source."
"We are using the free version of Jenkins. There are no costs or licensing."
"The tool is open-source."
"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."
"​It is free.​"
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
18%
Manufacturing Company
11%
Government
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.
What needs improvement with LaunchDarkly?
We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns. I would rate LaunchDarkly a seven out of ten.
What is your primary use case for LaunchDarkly?
We use LaunchDarkly for managing feature flags. It helps manage the keys to control what users view on our screens.
 

Comparisons

 

Overview

 

Sample Customers

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Information Not Available
Find out what your peers are saying about Jenkins vs. LaunchDarkly and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.