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

Buildkite vs Harness 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
Harness
Ranking in Build Automation
7th
Average Rating
7.8
Reviews Sentiment
7.5
Number of Reviews
7
Ranking in other categories
Static Application Security Testing (SAST) (16th), Cloud Cost Management (9th), Feature Management (2nd)
 

Mindshare comparison

As of March 2026, in the Build Automation category, the mindshare of Buildkite is 3.4%, up from 0.6% compared to the previous year. The mindshare of Harness is 5.3%, down from 6.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Harness5.3%
Buildkite3.4%
Other91.3%
Build Automation
 

Featured Reviews

Prabin Silwal - PeerSpot reviewer
Senior Engineering Consultant at ASSURANCE IQ, INC.
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.
MK
Technical Associate at ZS
Templatized pipelines have improved efficiency while limitations in code-based development remain
Harness UI can do a lot of good things. Harness's UI should not feel very complicated. At the current stage, it feels very commercialized and compared to other platforms such as Argo CD or Jenkins, which feel much more lively and much more simple. Infrastructure as code or pipeline as code is something that Harness severely lacks. There is not a lot of good support for pipeline as code, and I often find myself not using pipeline as code the way other platforms such as GitHub Actions or Jenkins integrate pipeline as code. Pipeline as code is definitely one of the disadvantages when it comes to Harness. Additionally, the entire platform feels very commercialized, which is something that a lot of developers, especially open-source enthusiasts, might not appreciate even within the organization. One of the very important key factors I observed was that there is no way to execute nested pipelines, which means that we cannot execute child pipelines within child pipelines and child pipelines even within those child pipelines. There is no way to execute nested pipeline execution, which may or may not be required based on the use case, but it is definitely one of those features that I wish the platform had.

Quotes from Members

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

Pros

"What I like best about Buildkite is its workflow management. You define YAML files to specify what needs to be done. The jobs can run based on a schedule, like a cron job, where you set it to run every night or every week. Additionally, you can set up triggers, such as new pushes to a repository."
"The solution can be considered as a very well-polished platform with a really great UI."
"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."
"They have great plugins, scalability, UI, and pipeline options. They also offer webhooks that allow integration with custom setups to send events dynamically."
"Using Buildkite, it's much easier to manage pipelines. It's straightforward to understand what each pipeline returns, making it easy to edit configurations, such as passwords. Although there is a steep learning curve initially, the overall process is still comprehensible. Additionally, Buildkite offers features like hooks and triggers; for example, an action in the app can automatically trigger a pipeline. These elements can be added to specific pipelines, ensuring the entire process is automated."
"The tool's flexibility with pipelines gave us a lot of advantages, especially when managing a huge amount of microservices."
"Buildkite allows us to build automations and integration tasks effectively."
"By adopting templates and various different pipelines across our own IDP platform, we have saved upwards of 30 to 40% of development time and also reduced risks of failures or error rates by upwards of 70%."
"Everything in Harness is configured and runs smoothly."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"Harness has positively impacted my organization as several teams have already migrated to it, and some are in the process of moving, reducing the dependency on one specific platform and making it faster with shortened build times and much faster deployments."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."
"It's a highly customizable DevOps tool."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
 

Cons

"It gets very complex if you want the tool to scale automatically."
"The product must provide better integration with other tools."
"I would like to see some improvements in the hooks implementation."
"The solution should offer more options for installing an agent and give users the option of having a separate self-hosted or provisioned agent."
"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."
"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."
"BuildKite should follow some providers like GitHub Actions. They can offer a shared agent or cloud agent."
"Since we were using Buildkite for the first time, we had a lot of difficulty understanding how it worked. We didn't find any documentation from third parties; only Buildkite provided documentation. As a result, we faced a steep learning curve. After some time, it became much easier to use. Initially, understanding certain features, like the R integration, was challenging."
"Even with automation, there's a requirement for manual change requests for approvals."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"Harness setup and configurations could be made easier to configure, which would be helpful."
"Harness can be improved by providing more clarity on the credits it issues for Harness Cloud, as it has a tiered pricing structure involving license and credit costs, which can get confusing."
"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."
"Infrastructure as code or pipeline as code is something that Harness severely lacks."
 

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."
"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."
"We used the solution’s free version."
"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.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
15%
Financial Services Firm
13%
Newspaper
13%
Computer Software Company
8%
Financial Services Firm
28%
Computer Software Company
8%
Manufacturing Company
7%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise1
Large Enterprise6
By reviewers
Company SizeCount
Small Business1
Large Enterprise9
 

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 do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
Harness can be improved by providing more clarity on the credits it issues for Harness Cloud, as it has a tiered pricing structure involving license and credit costs, which can get confusing. Addit...
What is your primary use case for Harness?
Harness helps us build a pipeline with containerized steps that isolates virtual machines, reduces DevOps-based drifts, and improves our process by integrating several security testing-related step...
 

Comparisons

 

Also Known As

No data available
Armory
 

Overview

 

Sample Customers

Information Not Available
Linedata, Openbank, Home Depot, Advanced
Find out what your peers are saying about Buildkite vs. Harness and other solutions. Updated: March 2026.
884,873 professionals have used our research since 2012.