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

CloudBees vs Depot 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

CloudBees
Ranking in Build Automation
7th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
20
Ranking in other categories
Configuration Management (9th), Value Stream Management Software (2nd), DevSecOps (5th), AI-Augmented Software-Testing Tools (2nd), Feature Management (1st), AI Software Development (11th)
Depot
Ranking in Build Automation
22nd
Average Rating
7.4
Reviews Sentiment
5.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of CloudBees is 3.3%, up from 1.5% compared to the previous year. The mindshare of Depot is 0.5%. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
CloudBees3.3%
Depot0.5%
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.
RS
Senior Technical Lead at HCLSoftware
Managing complex code branches has been challenging but has improved team collaboration
Depot needs improvement as it was stable but also very slow. Depot's slow speed arises when we perform different integrations. On the positive side, it provides mono-repo scalability, meaning it can handle multiple users at any given time without crashing, which is a strong point. Depot should be improved for remote work because it functions poorly in that regard. Depot's branching style is also poor and could be improved. There is a steep learning curve that makes it difficult for people who previously worked on decentralized systems to adapt. It would be beneficial if Depot could become more similar to Git.

Quotes from Members

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

Pros

"The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar, management master to CloudBees, Blue Ocean, JobConfig, and support."
"The customer support is good. You get good representatives from CloudBees to help you and understand your requirements."
"The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."
"The most valuable feature of the solution is that its GUI is quite simple."
"CloudBees assists by automating tasks, previously done manually, in the pipeline setup."
"The security audit product offered by CloudBees is particularly beneficial in automating audit processes, which reduces the time developers spend on audits."
"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"
"Depot has positively impacted my organization by helping us manage our code better where multiple developers are working on the system."
"Depot has positively impacted my organization in an awesome way, and the fact that I can save time gives me the possibility to have more clients during the day, saving at least 20% each day because of Depot."
"Depot has positively impacted our organization by ensuring that everything works fully, which makes other clients really happy."
 

Cons

"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times."
"We did face some challenges, particularly with the infrastructure."
"When I started with CloudBees, I found the configuration at the CD level to be quite challenging when creating end-to-end orchestration or release execution flows."
"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."
"There are connection issues with CloudBees, specifically between Sybase and CloudBees. W"
"I think a preview of the errors would be good just at the point where the error occurs."
"There could be improvements in the ease of use."
"Depot needs improvement as it was stable but also very slow."
"However, they need improvement with older servers due to storage space issues, which prevents me from giving a perfect score of ten."
"Depot is a useful tool and there is space for improvement, but I can't figure out what can be done, which is why I chose eight out of ten."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
909,153 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
17%
Financial Services Firm
16%
Manufacturing Company
16%
Outsourcing Company
9%
Construction Company
42%
Manufacturing Company
12%
Comms Service Provider
9%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
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 is your experience regarding pricing and costs for Depot?
Regarding my experience with pricing, setup cost, and licensing for Depot, I have faced many challenges with cost optimization. We need to manage what services we can use and optimize the cost, whi...
What needs improvement with Depot?
Depot needs improvement as it was stable but also very slow. Depot's slow speed arises when we perform different integrations. On the positive side, it provides mono-repo scalability, meaning it ca...
What is your primary use case for Depot?
My main use case for Depot was for storing production code and deploying it through pipelines. A specific example of how I used Depot for storing production code and deploying through pipelines inv...
 

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. Depot and other solutions. Updated: August 2026.
909,153 professionals have used our research since 2012.