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

Buildkite vs Depot comparison

Why PeerSpot?
 

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
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 October 2026, in the Build Automation category, the mindshare of Buildkite is 3.3%, up from 2.2% compared to the previous year. The mindshare of Depot is 0.8%. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Buildkite3.3%
Depot0.8%
Other95.9%
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.
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

"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."
"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."
"The documentation is quite helpful."
"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."
"You don't have to set up an agent in Buildkite like in Jenkins."
"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."
"Buildkite allows us to build automations and integration tasks effectively."
"The tool's flexibility with pipelines gave us a lot of advantages, especially when managing a huge amount of microservices."
"Depot has positively impacted our organization by ensuring that everything works fully, which makes other clients really happy."
"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."
 

Cons

"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."
"Compared to market leaders like Azure DevOps and Jenkins, Buildkite's community is smaller, but they do have some documentation."
"The product must provide better integration with other tools."
"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."
"I would like to see some improvements in the hooks implementation."
"BuildKite should follow some providers like GitHub Actions. They can offer a shared agent or cloud agent."
"It gets very complex if you want the tool to scale automatically."
"Based on the load, the agents can be scaled up and scaled down, and while they are scaling up, sometimes they just get stuck."
"However, they need improvement with older servers due to storage space issues, which prevents me from giving a perfect score of ten."
"Depot needs improvement as it was stable but also very slow."
"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."
 

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."
"The self-hosted option is pretty cheap."
"The solution's per-user pricing model suits huge enterprises but is expensive for small to medium businesses."
"For a business plan, it was 19 USD per month per user."
"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."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
915,341 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%
Construction Company
38%
Manufacturing Company
13%
Comms Service Provider
12%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise1
Large Enterprise6
No data available
 

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 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

Find out what your peers are saying about Buildkite vs. Depot and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.