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

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

Depot
Ranking in Build Automation
21st
Average Rating
7.4
Reviews Sentiment
5.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
GitLab
Ranking in Build Automation
3rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
Application Security Tools (9th), Release Automation (2nd), Static Application Security Testing (SAST) (6th), Rapid Application Development Software (15th), Software Composition Analysis (SCA) (6th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (1st)
 

Mindshare comparison

As of November 2026, in the Build Automation category, the mindshare of Depot is 0.8%. The mindshare of GitLab is 6.1%, down from 11.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
GitLab6.1%
Depot0.8%
Other93.1%
Build Automation
 

Featured Reviews

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.
BasilJiji - PeerSpot reviewer
System engineer at a retailer with 10,001+ employees
Role-based workflows have transformed daily deployments and improve team collaboration
GitLab has role-based access control, so when a team member needs to make a code change, they cannot directly apply it to the environment but must put in a merge request. Once a senior reviews the code and approves it, then it is implemented across the environment, making it safer and allowing everyone to experience the process. The best features GitLab offers are version control and automation, which are the major things that stand out to me. When it comes to access, the login is very smooth, with just one login integrated with our Okta, allowing everyone to log in easily. Deployments become much easier, and that is how GitLab helps. The automation features make my work easier because we use a tool called AWX, which is connected to GitLab. Whenever we run a job on AWX, it directly checks the code and uses it. Since the code is not preserved locally but kept in the cloud, it is safe and nobody can tamper with it. When it comes to safety, that is a major thing. Automation features allow the code to be accessed from any tools we use, so the jobs we run are helping tremendously and doing their work perfectly. For pipeline tasks, we have created a significant amount of pipelines, which are all hosted in GitLab. Running the pipelines has become much easier, and they are doing a perfect job, helping tremendously in our day-to-day activities. GitLab has positively impacted my organization because previously we stored code locally on servers, leading to many risks. Since GitLab came into our environment, our integration and deployments became much easier, helping our work become much smoother. Improvements from GitLab have led to better team collaboration because when several people are working, they can all edit the code and submit it as a merge request, and once approved, it reflects directly to the main branch. Many can work at the same time. When it comes to deployments, deploying has become much faster since we started using GitLab, and even if errors occur, we can spot them easily and troubleshoot, which has helped tremendously.

Quotes from Members

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

Pros

"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."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"I like GitLab's security and SAS tools."
"The stability of GitLab is impressive."
"GitLab has positively impacted our organization by making our code very secure because GitLab prides itself on security."
"I previously used Gerrit and I prefer GitLab, as it is much better in the interface and integration, and it is more than only Git software, it is more of a complete package."
"This is a scalable solution. We had around 200 users working with it."
"It is scalable."
"We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution. We also found the straightforward setup, stability, and scalability of GitLab valuable."
 

Cons

"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."
"However, they need improvement with older servers due to storage space issues, which prevents me from giving a perfect score of ten."
"The technology could be made simpler to use, it should not be overly complex."
"GitLab should enhance its GitOps capability as they are currently using FluxCD, however, Argo CD is better and offers more features. GitLab should work on improving their user interface for GitOps as it is lagging behind."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"The solution could be faster."
"The integration could be slightly better."
"There are some challenges with repository file management as GitLab may struggle to manage larger files."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
 

Pricing and Cost Advice

Information not available
"We are using the open-source version."
"My company uses the free version of GitLab, which is GitLab Community Edition. There is a licensed version also available for GitLab."
"I'm not aware of the licensing costs because those were covered by the customer."
"It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."
"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."
"GitLab is an open-source solution."
"The open-source version is very good and the commercial version is reasonably priced."
"GitLab's pricing is good compared to others on the market."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
38%
Manufacturing Company
13%
Comms Service Provider
13%
University
6%
Financial Services Firm
13%
Manufacturing Company
11%
Government
8%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise10
Large Enterprise50
 

Questions from the Community

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...
What is your experience regarding pricing and costs for GitLab?
I was using the free version of GitLab , but I think the price is comparative and not a major differentiator.
What needs improvement with GitLab?
Since GitLab [Private Offer Only] the main part is the Git part. With AI being available, I see one thing happening. For example, Claude Code allows people to connect Jira or ClickUp, and then they...
What is your primary use case for GitLab?
My basic use case for Gitlab was the ticket management, the wiki, the CI/CD pipeline, and the code repository. These four use cases form my core usage.
 

Comparisons

 

Also Known As

No data available
Fuzzit
 

Overview

 

Sample Customers

Information Not Available
1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
Find out what your peers are saying about Depot vs. GitLab and other solutions. Updated: November 2026.
920,769 professionals have used our research since 2012.