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

Buildkite vs Codefresh comparison

 

Comparison Buyer's Guide

Executive Summary

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
Codefresh
Ranking in Build Automation
15th
Average Rating
8.6
Reviews Sentiment
5.9
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of Buildkite is 3.3%, up from 1.6% compared to the previous year. The mindshare of Codefresh is 0.9%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Codefresh0.9%
Buildkite3.3%
Other95.8%
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.
US
DevOps Engineer at a manufacturing company with 51-200 employees
GitOps control plane has transformed deployments and now enables proactive Kubernetes visibility
While using Codefresh, I still don't see many downsides, but I would say the UI performance with large logs is an area for improvement. When a complex pipeline generates a high volume of logs, the user interface can occasionally become sluggish, jittery, or take extra seconds to render. The only downside I would say is the UI experience and its smoothness. Although the visibility into Kubernetes is excellent, I would love to see out-of-the-box cost optimization metrics. Argo CD knows how a pod is performing, its status, and its state. There should be some kind of cost optimization metrics shown on the GitOps application where we could save money or perhaps reduce the resources of a particular pod application. One improvement I would say is a promotion process between environments, from lower to upper environment. Currently, the model with complex promotion logic such as specific concurrency strategies or smart rollbacks when multiple commits hit at once can feel quite manual. I would like to see more automated promotion gates that can handle multi-cluster dependencies without needing as much custom YAML configuration.

Quotes from Members

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

Pros

"You don't have to set up an agent in Buildkite like in Jenkins."
"It is a stable solution."
"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."
"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."
"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."
"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."
"Codefresh impacts my organization positively by improving security and making the time of releases much shorter and faster than the previous scenario with CI/CD implementations."
"Since switching to Codefresh, our organization has definitely seen approximately a 30 percent reduction in deployment times."
"Codefresh has helped save time, reduce errors, and improve collaboration across teams."
"Codefresh has positively impacted my organization; it has been amazing."
"Before Codefresh, we had to plan the strategy, write the configuration file, and run everything; it used to take two to three days to plan and implement, but now it is a one-time job, so it can be done in ten to fifteen minutes, which has reduced a lot of time and sped up the automation and CI/CD, requiring fewer employees."
"Codefresh has positively impacted my organization by helping to deliver stories faster, minimizing defects, and deploying code quickly while completing user stories in a shorter time."
 

Cons

"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 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 solution should offer more options for installing an agent and give users the option of having a separate self-hosted or provisioned agent."
"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."
"The product must provide better integration with other tools."
"I would like to see some improvements in the hooks implementation."
"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."
"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."
"The reason it is not a ten is because our developers who do not have Kubernetes and Docker knowledge cannot use Codefresh easily, and the configuration file we have to write is very complex, requiring prior knowledge of Kubernetes and Docker-based deployments."
"While using Codefresh, I still don't see many downsides, but I would say the UI performance with large logs is an area for improvement."
"The challenge that we faced with Codefresh is that it is a complex setup."
"Codefresh can be improved with more capability inside the GCP ecosystem."
"At this moment, I cannot think of anything about needed improvements for Codefresh."
 

Pricing and Cost Advice

"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."
"We used the solution’s free version."
"The solution's per-user pricing model suits huge enterprises but is expensive for small to medium businesses."
"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."
"For a business plan, it was 19 USD per month per user."
"The self-hosted option is pretty cheap."
"I don't think the tool is expensive."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Outsourcing Company
13%
Manufacturing Company
11%
Healthcare Company
7%
Insurance Company
30%
Outsourcing Company
13%
Construction Company
11%
Wholesaler/Distributor
8%
 

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 Business2
Large Enterprise5
 

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 Codefresh?
Codefresh can be improved by creating more integration with other tools or providers.
What is your primary use case for Codefresh?
My main use case for Codefresh is continuous integration and delivery. I use Codefresh for continuous integration and delivery in my workflow by using CI/CD pipelines to trigger builds for code and...
What advice do you have for others considering Codefresh?
I would rate Codefresh an eight out of ten because it is mostly positive. Regarding Codefresh's governance and security, I think it is pretty secure. Regarding Codefresh's accuracy and reliability ...
 

Comparisons

 

Overview

Find out what your peers are saying about Buildkite vs. Codefresh and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.