No more typing reviews! Try our Samantha, our new voice AI agent.

Buildkite vs Harness comparison

Why PeerSpot?
 

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
16th
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
5th
Average Rating
8.0
Reviews Sentiment
7.3
Number of Reviews
11
Ranking in other categories
Static Application Security Testing (SAST) (7th), Cloud Cost Management (8th), Feature Management (2nd)
 

Mindshare comparison

As of September 2026, in the Build Automation category, the mindshare of Buildkite is 3.3%, up from 2.0% compared to the previous year. The mindshare of Harness is 4.6%, down from 7.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Harness4.6%
Buildkite3.3%
Other92.1%
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

"The documentation is quite helpful."
"The tool's flexibility with pipelines gave us a lot of advantages, especially when managing a huge amount of microservices."
"The tool is simple and has no learning curve. If you know YAML, you can master it. It is simple to learn."
"Buildkite allows us to build automations and integration tasks effectively."
"Buildkite makes it easier to conduct deployment. When I merge a PR in Buildkite, it automatically starts the deployment process. It used to be challenging to shift code from the development branch to the testing branch because I had to follow up with multiple developers. Previously, I was dependent on the DevOps team and developers to handle deployments, but now it allows me to deploy the solutions myself.This has made it much easier for me to handle both non-production and production environments."
"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."
"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."
"It is a stable solution."
"Some of the best features of Harness include powerful CI/CD pipeline automation, intelligent deployment strategies, and building monitoring, and its automation capabilities significantly improve speed and reliability while saving time by reducing manual operational tasks and the number of employees needed for deployments."
"It's a highly customizable DevOps tool."
"Harness positively impacts our organization by reducing deployment time, improving release confidence, and lowering operational overhead during deployment."
"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 starts integrating with organizations, making everything automated without the need for manual interruption."
"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"Approximately seventy-five percent time was reduced in case of deployment and around sixty to sixty-five percent time was reduced while troubleshooting it."
 

Cons

"The product must provide better integration with other tools."
"My company has had problems with the tool's parallel running and execution time. The testing framework also has some limitations. The tool cannot do everything."
"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."
"Compared to market leaders like Azure DevOps and Jenkins, Buildkite's community is smaller, but they do have some documentation."
"As a newbie, I think BuildKite has several issues. For example, it can't get the status of a PR once it's closed. The syntax is easy to use, but updating a pipeline requires administrator settings, and viewing pipelines for others isn't straightforward."
"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."
"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."
"One improvement I see for Harness is simplifying the configuration process for smaller teams or startups, as the platform offers powerful features that new users may require some time to understand."
"The licensing cost can be significant for larger teams, which should be taken into account."
"There are some UI components that can be improved."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"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."
"The initial setup can be complex and time-consuming, and the advanced features may require some learning time due to a steep learning curve."
 

Pricing and Cost Advice

"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."
"I don't think the tool is expensive."
"The self-hosted option is pretty cheap."
"For a business plan, it was 19 USD per month per user."
"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."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
21%
Financial Services Firm
12%
Manufacturing Company
10%
Healthcare Company
8%
Financial Services Firm
23%
Outsourcing Company
11%
Manufacturing Company
7%
Comms Service Provider
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 Business4
Midsize Enterprise1
Large Enterprise10
 

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 Harness?
There are some UI components that can be improved. The needed UI improvements include more graphs, more history, the ability to create pipelines through the UI, and more interactions, with UI compo...
What is your primary use case for Harness?
My main use case for Harness is to create pipelines, deploy applications, and manage security pipelines. I use Harness to deploy applications to EC2 instances and Kubernetes instances, and I create...
What advice do you have for others considering Harness?
My advice for others looking into using Harness is to use AI capabilities, create pipelines, and then use it to deploy. Harness is a good tool. I would rate this review a nine out of ten.
 

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: September 2026.
913,806 professionals have used our research since 2012.