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

LaunchDarkly vs Travis CI 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

LaunchDarkly
Average Rating
8.0
Reviews Sentiment
5.8
Number of Reviews
8
Ranking in other categories
Feature Management (3rd), AI Software Development (18th)
Travis CI
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
Build Automation (20th)
 

Mindshare comparison

LaunchDarkly and Travis CI aren’t in the same category and serve different purposes. LaunchDarkly is designed for Feature Management and holds a mindshare of 18.8%, up 11.1% compared to last year.
Travis CI, on the other hand, focuses on Build Automation, holds 2.2% mindshare, up 0.7% since last year.
Feature Management Market Share Distribution
ProductMarket Share (%)
LaunchDarkly18.8%
Harness23.7%
Optimizely16.5%
Other41.0%
Feature Management
Build Automation Market Share Distribution
ProductMarket Share (%)
Travis CI2.2%
GitLab9.0%
GitHub Actions8.1%
Other80.7%
Build Automation
 

Featured Reviews

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.
Pravar Agrawal - PeerSpot reviewer
Senior SRE at a tech vendor with 10,001+ employees
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

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

Pros

"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 ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit."
"I like that it offers the ability to control the flags."
"The initial setup is very easy."
"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."
"The setup is easy."
"From the development side, it allows us to manage multiple things."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"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."
"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."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
"When the system has an excessive number of feature flags, managing them can become cumbersome."
"The feature where one feature flag is dependent on another could be explored more for our usage."
"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."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
report
Use our free recommendation engine to learn which Feature Management solutions are best for your needs.
881,707 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
University
17%
Manufacturing Company
11%
Financial Services Firm
11%
Retailer
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise1
Large Enterprise5
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for LaunchDarkly?
At my current organization, I have no experience with licensing and setup cost. However, at my previous organization, I wasn't making any decisions but got some visibility into the pricing and usag...
What needs improvement with LaunchDarkly?
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 togg...
What is your primary use case for LaunchDarkly?
Currently, my main use case for LaunchDarkly is as a consumer. The application that I'm using uses LaunchDarkly as feature toggles. We toggle our flags on and off depending on what environment they...
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about Harness, CloudBees, LaunchDarkly and others in Feature Management. Updated: January 2026.
881,707 professionals have used our research since 2012.