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

Bitrise vs Depot comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 13, 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

Bitrise
Ranking in Build Automation
8th
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
14
Ranking in other categories
AI Software Development (20th)
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 Bitrise is 1.4%, up from 0.6% 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 (%)
Bitrise1.4%
Depot0.5%
Other98.1%
Build Automation
 

Featured Reviews

Mansoor-Mohammed - PeerSpot reviewer
SRE at a consultancy with 11-50 employees
Weekly mobile releases have become reliable and pipeline incidents have dropped dramatically
The improvement I would suggest for Bitrise is that the cost is significantly the friction point. Mac build machines are considerably more expensive than Linux equivalents. As our team has grown, the monthly bills have scaled accordingly with limited room to optimize without reducing concurrency. The self-hosted runner option was evaluated as a potential cost-saving measure, but the documentation and tooling for it are still less mature than the cloud product. Build debugging remains a log parsing exercise. There is no interactive debugging session or live SSH access into a failing build environment, which would be a meaningful productive improvement. The analytics dashboard is very minimal and basic and lacks the depth that anyone would want for capacity planning and trend analysis.
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 faster deployment with Bitrise allows us to get to the market quickly, enabling us to receive feedback from clients rapidly, test our application internally, and deliver more robust solutions efficiently."
"Since I started using Bitrise, the development time, specifically the time that I spend on sharing these builds and handling the release process, is significantly reduced."
"I can share that after using Bitrise, we have seen a time savings of fifty percent."
"It reduced the release time by approximately 50 to 60 percent, improved deployment consistency, and also reduced our manual intervention in mobile releases."
"Bitrise has positively impacted my organization because previously we used to generate builds on our local machine, which was very time-consuming, and now all the build generation and the automation execution are directly done on Bitrise, and the automation execution is triggered from Bitrise to AWS Device Farm."
"A positive impact that Bitrise has had on my organization is that it kept the version releases consistent and we were able to catch PR problems, build and test problems, and SwiftLint issues during code review time."
"Within three months of going live on Bitrise, we moved to weekly releases, and now we have a reliable hotfix pipeline that can ship a production build within 45 minutes to an hour of a fix being merged."
"With Bitrise, as a team of 10 to 12 people, we are able to independently generate the build and save overall 20 to 40 hours per day."
"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

"Bitrise can be improved by offering a more customizable dashboard, faster troubleshooting for failed builds, and more advanced cost visibility for pipeline usage."
"The only downside I have to mention about my main use case is that debugging a failed build can sometimes be time-consuming, and whenever the build fails, it becomes expensive for the larger projects."
"Sometimes the builds fail, and the error messages that I get are not very descriptive."
"Bitrise has to work more on the error part. Sometimes I face issues when I trigger a build to generate, and I get a build failed without getting the proper log, which sometimes makes the user too annoyed."
"They need to add some extra documentation for how to use the parameters, such as variables, where to add them, and how to use them below the workflow."
"One improvement Bitrise can have is enhanced debugging tools for analyzing failed builds."
"The improvement I would suggest for Bitrise is that the cost is significantly the friction point."
"I think Bitrise could be improved if it was easier to generate Android QA and iOS at the same time."
"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."
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
Comms Service Provider
17%
Outsourcing Company
16%
Construction Company
13%
Manufacturing Company
10%
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 Business6
Midsize Enterprise5
Large Enterprise8
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Bitrise?
My experience with pricing, setup cost, and licensing for Bitrise was positive since it was really cost-optimized. The setup cost was actually null, and it was really easy to set up and renovate th...
What needs improvement with Bitrise?
Today I don't see any improvement points for Bitrise. It serves us very well, and the project is going very well with Bitrise. At certain times we have failures within the tool itself where we need...
What is your primary use case for Bitrise?
My main use case for Bitrise is for automating CI/CD in the projects where I work. I use Bitrise to automate processes for pushing releases, building versions, and building PRs. When we open a PR, ...
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

 

Also Known As

Bitrise on AWS: Linux bare metal CI builder, Bitrise on AWS: macOS bare metal CI builder
No data available
 

Overview

 

Sample Customers

TransferWise, Fueled, Tonal, Sixt, Cheddar, Eureka, Pulselive
Information Not Available
Find out what your peers are saying about Bitrise vs. Depot and other solutions. Updated: August 2026.
909,153 professionals have used our research since 2012.