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
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
Travis CI
Ranking in Build Automation
21st
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of LaunchDarkly is 0.3%. The mindshare of Travis CI is 0.7%, down from 1.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

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.
Pravar Agrawal - PeerSpot reviewer
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

"The ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit."
"It has really helped during the series of product lines and faster deployment and faster development."
"The setup is easy."
"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."
"I appreciate that we can release any feature in production and maintain control over it."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"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."
"Right now, no improvements are needed."
"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."
"I have used LaunchDarkly for around two and a half years and I haven't faced any issues with it."
"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 Build Automation solutions are best for your needs.
846,617 professionals have used our research since 2012.
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

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.
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, ...
 

Overview

 

Sample Customers

Information Not Available
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: April 2025.
846,617 professionals have used our research since 2012.