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

Buildkite 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

Buildkite
Ranking in Build Automation
8th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
14
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 June 2025, in the Build Automation category, the mindshare of Buildkite is 1.2%, up from 0.1% compared to the previous year. The mindshare of LaunchDarkly is 0.4%, up from 0.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Prabin Silwal - PeerSpot reviewer
Has an easy setup phase while also offering good documentation
The problem we are facing sometimes is that we have lots of unit testers, and we have to wait about ten minutes to complete all of those because we want to run or find a way. It's not directly due to the limitation of the tool as well, but when we are running the spec, we want to run those parallelly and decrease the downtime so that our deployment can be faster. I think that one is not possible only due to the it also depends upon the unit test framework as well we are using. When we tried with the multiple test cases in a parallel manner, there were some dependencies, and one over another kept failing. We make those sequential calls. The aforementioned area consists of the issues my company faced while using Buildkite.
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

"Buildkite allows us to build automations and integration tasks effectively."
"They have great plugins, scalability, UI, and pipeline options. They also offer webhooks that allow integration with custom setups to send events dynamically."
"The tool is simple and has no learning curve. If you know YAML, you can master it. It is simple to learn."
"The solution can be considered as a very well-polished platform with a really great UI."
"Buildkite's UI is particularly intuitive, making it simple to add steps to your pipeline. It also provides detailed logging."
"You don't have to set up an agent in Buildkite like in Jenkins."
"The product's initial setup phase was easy."
"If you join our team, it's very easy to learn Buildkite. We have our own boilerplate, so you can just clone it and add your configuration steps. Plus, we have documentation available to guide you through the process."
"The initial setup is very easy."
"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."
"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."
"I like that it offers the ability to control the flags."
 

Cons

"The solution should offer more options for installing an agent and give users the option of having a separate self-hosted or provisioned agent."
"It gets very complex if you want the tool to scale automatically."
"Most of our projects involve both front-end and back-end development. We write the code and then create a file to set up our process, including specifying the tests we want to run. Before deploying to production, we need to install and configure certain things. We need something like Docker Pro, but I'm unsure about that. I'm familiar with the steps for using Buildkite for this process. We start by defining which tests to run."
"Based on the load, the agents can be scaled up and scaled down, and while they are scaling up, sometimes they just get stuck."
"There is a need for rework occasionally, and issues like syntax errors can occur multiple times, especially when manual changes are made in AWS or Amazon Connect that are not captured in the code."
"BuildKite should follow some providers like GitHub Actions. They can offer a shared agent or cloud agent."
"Buildkite has issues while creating or extending branches as only the first five builds in the user-interface can be accessed and post that one has to access the next builds by remembering branch names without pagination which can be inconvenient."
"The way Buildkite represents workflows can be challenging. It uses Directed Acyclic Graphs, and there's a trade-off between abstraction and understanding what goes wrong when something fails. When a layer of jobs breaks down, it can be difficult to identify the issue at first glance. Additionally, logging can be cumbersome. I prefer GitHub Workflows."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
"We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns."
"Right now, no improvements are needed."
"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."
"I have used LaunchDarkly for around two and a half years and I haven't faced any issues with it."
"Fetching information about multiple flags in a single action would be beneficial."
 

Pricing and Cost Advice

"I don't think the tool is expensive."
"I find Buildkite cost-effective as it has definitely increased my productivity, especially on the deployment side. It saved a lot of my time and improved data management because I can handle different environments myself now."
"The solution's per-user pricing model suits huge enterprises but is expensive for small to medium businesses."
"We used the solution’s free version."
"Buildkite is known to be cheaper than GitHub Workflows, which is considered a standard in the industry. It can be cost-effective, especially for organizations that heavily utilize Docker and containerization, because every code change triggers a new build. Its integration with AWS, particularly with ECR, and its caching capabilities with layers are powerful features."
"For a business plan, it was 19 USD per month per user."
"The self-hosted option is pretty cheap."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
857,162 professionals have used our research since 2012.
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Buildkite?
One area that needs improvement in Buildkite is the requirement for rework of the code. There can be syntax errors when running the Buildkite pipeline, especially if someone has made manual changes...
What is your primary use case for Buildkite?
I use Buildkite for deployment tasks related to building AMI images and deploying routing profile queues into Amazon Connect. This involves using Buildkite in conjunction with GitHub. We create fil...
What advice do you have for others considering Buildkite?
With two years of experience on Buildkite, I would recommend it to others due to its manageable pipeline and the support team available for big issues. I am satisfied with it, rating its stability ...
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

Find out what your peers are saying about Buildkite vs. LaunchDarkly and other solutions. Updated: June 2025.
857,162 professionals have used our research since 2012.