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

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

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
GitLab
Ranking in Build Automation
3rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
91
Ranking in other categories
Application Security Tools (6th), Release Automation (2nd), Static Application Security Testing (SAST) (4th), Rapid Application Development Software (12th), Software Composition Analysis (SCA) (4th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (1st)
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of Depot is 0.5%. The mindshare of GitLab is 6.3%, down from 14.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
GitLab6.3%
Depot0.5%
Other93.2%
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 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."
"My advice for others looking into this product is to go for it; GitLab is the future."
"Git hosting has an integration with ACD which is why we liked this solution in the first place."
"We use GitLab in the new project for CI/CD, integration, and deployment."
"In our software development lifecycle, GitLab is used as a component for code repository management. We use GitLab for several projects to handle code repositories. For other software projects, we use Bitbucket, but the use case for both is very similar."
"Gitlab is also more customizable."
"When a developer checks in code, it is automatically built and deployed, and automated test cases are also run. We have extensive integration with GitLab, which helps us with source code management. We run the static code analysis using SonarQube."
"The most valuable feature of GitLab is its security."
"This is a scalable solution. We had around 200 users working with it."
 

Cons

"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."
"Depot needs improvement as it was stable but also very slow."
"Technologies are always changing. Nowadays, new things like serverless computing and workload management have emerged. We have noticed a few gap items for faster service delivery. For example, we do user interface testing in the latest team and automate it using some tools. Recently, we integrated a tool with user interface testing, which can simulate a multi-user environment. So, we would like to see more integration with different platforms."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful."
"The integration could be slightly better."
"Atlassian offers more products than GitLab. GitLab offers source control management, version control and collaboration between developers. Atlassian offers features on top of this as well as more integration points for developers."
"GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."
"We had to write GitLab configuration files, commands and conditions, in a YML format. I would like configuration of a YML file to be done via UI rather than a code file."
"As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab. In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release."
 

Pricing and Cost Advice

Information not available
"As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that."
"The solution's pricing is acceptable."
"Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value."
"The price of GitLab could be better, it is expensive."
"GitLab's pricing is good compared to others on the market."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a five out of ten."
"I'm not aware of the licensing costs because those were covered by the customer."
"In terms of the pricing for GitLab, on a scale of one to five, with one being expensive and five being cheap, I'm rating pricing for the solution a four. It could still be cheaper because right now, my company has a small team, and sometimes it's difficult to use a paid product for a small team. You'd hope the team will grow and scale, but currently, you're paying a high license fee for a small team. I'm referring to the GitLab license that has premium features and will give you all features. This can be a problem for management to approve the high price of the license for a team this small."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
42%
Manufacturing Company
13%
Comms Service Provider
9%
University
5%
Financial Services Firm
14%
Manufacturing Company
10%
Government
9%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise10
Large Enterprise49
 

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?
The setup cost for GitLab is minimal since the team has its own minimal resource balancing. The costing falls into an intermediate stage and is impactful across all results within the team. It allo...
What needs improvement with GitLab?
There are many improvements that GitLab can implement, such as addressing the issue of caching. Currently, when I have multiple tasks to merge or attempt multiple merges, the CI/CD and overall GitL...
What is your primary use case for GitLab?
My main use case for GitLab is as a version control system that we are using. Currently, I am working on an end-to-end AI pipeline, and I have deployed my whole code using GitLab so that all things...
 

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: August 2026.
909,725 professionals have used our research since 2012.