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

CloudBees vs Codefresh comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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

CloudBees
Ranking in Build Automation
6th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
20
Ranking in other categories
Configuration Management (10th), Value Stream Management Software (2nd), DevSecOps (4th), AI-Augmented Software-Testing Tools (2nd), Feature Management (1st), AI Software Development (9th)
Codefresh
Ranking in Build Automation
18th
Average Rating
9.4
Reviews Sentiment
6.2
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2026, in the Build Automation category, the mindshare of CloudBees is 2.9%, up from 1.2% compared to the previous year. The mindshare of Codefresh is 0.9%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
CloudBees2.9%
Codefresh0.9%
Other96.2%
Build Automation
 

Featured Reviews

KishoreKumar4 - PeerSpot reviewer
Senior Qe Lead at Cognizant
Consistent automation has improved deployments and supports efficient client-facing workflows
Deployment and other processes are feasible for me, making this a smooth process. The integration part is good. We can use multiple things by integrating with CI/CD pipelines, and this is very feasible for us. This allows us to do our work easily. The productivity is very good. CloudBees is a good and efficient tool. We can work in client-facing scenarios, and since clients have provided these types of tools, we are able to work on them effectively.
US
Dev Ops 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

"CloudBees assists by automating tasks, previously done manually, in the pipeline setup."
"CloudBees operates seamlessly. Deploying to a cluster is straightforward—just one click, and the job is done."
"It can manage multiple Jenkins instances."
"CloudBees is a good and efficient tool."
"CloudBees updates its features frequently, so if we need something like SSL login, they enable it."
"Scalability largely depends on how the tool is set up within your infrastructure"
"It’s a very good tool for auditing your project pipelines as well."
"CloudBees's user interface is very simple and user-friendly."
"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; it has been amazing."
"Since switching to Codefresh, our organization has definitely seen approximately a 30 percent reduction in deployment times."
"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."
 

Cons

"We've noticed occasional issues with folder permissions changing unexpectedly. Specifically, permissions sometimes shift from the CloudBees user to the root user. This can cause pipeline failures, as pipelines require the correct CloudBees user permissions to execute properly."
"One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time."
"It could improve the document upload process."
"A lot of stability issues are there with CloudBees."
"If you're logged in and working for about thirty minutes and then go idle for five to ten minutes, Jenkins will prompt you to re-authenticate."
"The user interface of CloudBees is good but could be even more intuitive. Improving the user-friendliness of the interface and having simpler setup configurations would greatly benefit new users."
"The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times."
"To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture."
"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 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."
"Codefresh can be improved with more capability inside the GCP ecosystem."
"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."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Construction Company
15%
Manufacturing Company
9%
Computer Software Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business1
Midsize Enterprise3
Large Enterprise18
No data available
 

Questions from the Community

What needs improvement with CloudBees?
For CloudBees, I can suggest that the log is very high, which is very hectic for us when trying to find which error is coming. This creates complexity. If possible, we could sort the logs so we can...
What is your primary use case for CloudBees?
We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.
What advice do you have for others considering CloudBees?
We can upload the JAR file and deploy at the Jenkins level during our deployment. These types of labels and IDs can be deployed using CloudBees. Once we click to start the build, it automatically r...
What needs improvement with Codefresh?
Codefresh has a learning curve for teams, as the initial pipeline configuration may require some familiarity with YAML and container-based CI/CD processes; a junior engineer cannot configure these ...
What is your primary use case for Codefresh?
I use Codefresh for Kubernetes applications and to deploy Kubernetes applications. We have used Codefresh for deploying containerized applications to Kubernetes environments, and our organization h...
What advice do you have for others considering Codefresh?
Previously, the process had to be done by three to four DevOps engineers, which included writing the YAML file, managing the containers running in Kubernetes, managing the configuration file, and c...
 

Comparisons

 

Overview

 

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Information Not Available
Find out what your peers are saying about CloudBees vs. Codefresh and other solutions. Updated: May 2026.
894,738 professionals have used our research since 2012.