We are using the product for configuration management and source course management. For some projects, we are using it issue management.
General Manager at Ekinoks Software
An easy setup with good configuration and source management
Pros and Cons
- "The solution is stable."
- "We'd always like to see better pricing on the product."
What is our primary use case?
What is most valuable?
Configuration and source management are the most valuable aspects of the solution.
It offers an easy initial setup.
The solution is stable.
I find the product scalable.
It's not overly expensive.
What needs improvement?
We'd always like to see better pricing on the product. If they could make the cost lower, that would be ideal for users.
For how long have I used the solution?
We've been using the solution for five or six years.
Buyer's Guide
GitLab
October 2025
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: October 2025.
872,019 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
What do I think about the scalability of the solution?
It is scalable and easy to expand.
We have about 100 users on the solution. That includes developers and testers.
Our team is getting better. We'll likely need 30 more licenses. Therefore, we plan to expand usage.
How are customer service and support?
We don't need technical support. Our IT team has handled all the issues and therefore we don't need any additional support.
Which solution did I use previously and why did I switch?
We did previously use a different solution. I can't recall the name.
How was the initial setup?
The solution is very straightforward to set up. It's not very complex at all. My understanding is it quite easy to implement. However, I was not completely involved.
What's my experience with pricing, setup cost, and licensing?
We pay a yearly licensing fee. The pricing is pretty low. It's not too expensive.
Which other solutions did I evaluate?
We did not evaluate other solutions. We've always used GitLab.
What other advice do I have?
I'm not sure which version of the solution I'm using.
I'd rate this product nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Specialist Data Analysis vehicle safety at Cubeware
Scalable, stable, and has a straightforward setup, but requires a lot of steps just to push code to the repository
Pros and Cons
- "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."
- "I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."
What is our primary use case?
My team primarily uses GitLab for CI/CD purposes. Whatever code I develop has to go with the team, so I work in a team that tries to write its version of the code, or uses the ticketing system, takes a ticket, covers that information, and then updates the main branch about it. That's the use case my team has for GitLab.
What is most valuable?
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.
What needs improvement?
I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better.
My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button.
For how long have I used the solution?
I've been using GitLab for almost four years.
What do I think about the stability of the solution?
As of now, we don't have any issues with GitLab stability-wise. We never faced any critical issues, so everything's going smoothly.
What do I think about the scalability of the solution?
GitLab is a scalable solution.
How are customer service and support?
We didn't use the technical support for GitLab because there are specific people within our organization that we can contact about issues, for example, access issues or permissions, and they give us access to the folders.
Which solution did I use previously and why did I switch?
We haven't used any other build automation product other than GitLab.
How was the initial setup?
We found the initial setup for GitLab very straightforward. We're developers, so we develop the code, then push that code to our branch. We have a moderator who keeps track of the testing process, so from our side, we already have the steps and what needs to be done and written, so we follow those steps to set up GitLab.
What about the implementation team?
The implementation of GitLab was done in-house within my company.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
I'm a developer, so I write all the code from scratch, but I don't use predefined platforms. I've been using GitLab and Visual Studio, though.
As GitLab is only used within my team, only five people use it.
My team uses GitLab almost every day, then when a project is complete, my team pushes it back into GitHub.
My team is an end-user of GitLab.
Regarding recommending GitLab to others, I'm a developer of data science solutions, so I mostly do end-user tasks rather than developer tasks. As of now, nothing was so bad about GitLab, and I didn't come across any significant hardships in using the solution. For a person like me who uses resources in a bigger enterprise, there shouldn't be problems using GitLab. If you're part of a small company, there could be some issues.
My rating for GitLab is seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
GitLab
October 2025
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: October 2025.
872,019 professionals have used our research since 2012.
Solution Architect and Senior Consultant at Keysight Technologies
A fantastic service delivery model with good security and stability
Pros and Cons
- "The solution's service delivery model is fantastic."
- "The solution should again offer an on-premises deployment option."
What is our primary use case?
Our company is a partner and installs the solution for clients who manage their ACD and DevOps pipelines.
We have 700 developers who use the solution, Microsoft's integration, and SharePoint for uploading.
What is most valuable?
The solution's service delivery model is fantastic.
Integrations connect to the cloud server and are easy to use.
The solution offers good security and stability.
What needs improvement?
The solution should again offer an on-premises deployment option. In the past, an on-premises solution was offered that used to sync with the cloud-based solution. We would like that option to return because many industries are interested in offline uploads and pathways.
The solution should integrate Web 3.0 and provide better system transactions.
For how long have I used the solution?
I have been using the solution for three years.
What do I think about the stability of the solution?
The solution is very stable.
How was the initial setup?
The initial setup is simple.
You can immediately start using the solution as soon as you subscribe.
What's my experience with pricing, setup cost, and licensing?
The solution is based on a subscription model and is reasonably priced.
Many options are available in the database but a few uncommon options that our company actually liked have been phased out. If those options return, the solution will be fantastic.
Our company subscribes to the premium tier which includes security. It would be nice to offer security as an add-on at lower tiers so more users have access to these advanced features.
I rate the cost an eight out of ten.
What other advice do I have?
I recommend the solution and rate it an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
DevOps Lead at Adidas
Great continuous integration and fast deployment
Pros and Cons
- "GitLab's best features are continuous integration and fast deployment."
- "GitLab's UI could be improved."
What is most valuable?
GitLab's best features are continuous integration and fast deployment.
What needs improvement?
GitLab's UI could be improved. In the next version, the documentation of the migrations steps should be better.
For how long have I used the solution?
I've been working with GitLab for six years.
What do I think about the stability of the solution?
GitLab is very stable.
What do I think about the scalability of the solution?
GitLab is scalable.
How are customer service and support?
GitLab's technical support is quick and responsive.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is pretty simple for GitLab as a service, but it's more complex for a hosted solution.
What's my experience with pricing, setup cost, and licensing?
GitLab is comparatively expensive, but it provides value because it's feature-rich. I would rate its pricing four out of five.
What other advice do I have?
I would rate GitLab nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Project Manager at Leyton & Associés, SAS
Highly intuitive UI, reliable, and good performance
Pros and Cons
- "The most valuable features of GitLab are ease of use and highly intuitive UI and performance."
- "GitLab can improve by integrating with more tools, such as servers with Docker."
What is our primary use case?
We use GitLab for all of our Git sources and it is mapped to our integrated solution for the complete ICG platform.
What is most valuable?
The most valuable features of GitLab are ease of use and highly intuitive UI and performance.
What needs improvement?
GitLab can improve by integrating with more tools, such as servers with Docker.
For how long have I used the solution?
I have been using GitLab for approximately 11 years.
What do I think about the stability of the solution?
GitLab is a stable solution. We've never faced any issues.
What do I think about the scalability of the solution?
Our current setup is with one server but GitLab overall can scale.
We have approximately 300 people using the solution. Most of the people are in the developers' teams, management, and tech leads that all log into GitLab.
GitLab can be used for enterprise-sized companies.
How are customer service and support?
I have not used the support from GitLab.
Which solution did I use previously and why did I switch?
I have previously used GitHub as a developer. GitLab looks similar to GitHub and it's helping the developer use it better.
What about the implementation team?
We update the GitLab version annually for maintenance.
What's my experience with pricing, setup cost, and licensing?
GitLab is a free solution to use.
What other advice do I have?
I rate GitLab a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Head of Digital Solutions at Bravantic
Simple to set up, stable, and has Auto DevOps features
Pros and Cons
- "The most valuable functionality of GitLab, for me, is the DevOps. Besides the normal source control based on Git, I find the Auto DevOps features most important in the solution."
- "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."
What is most valuable?
The most valuable functionality of GitLab, for me, is the DevOps. Besides the normal source control based on Git, I find the Auto DevOps features most important in the solution.
What needs improvement?
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.
For how long have I used the solution?
I've been using GitLab for almost three years.
What do I think about the stability of the solution?
GitLab is a pretty stable solution, and on a scale of one to ten, with one being the worst and ten being the best, I'm rating its stability a ten. My team just learned some details about the configuration of GitLab, so it's now tuned up, and right now, there's no problem with the stability of the platform.
What do I think about the scalability of the solution?
In terms of GitLab scalability, based on its features, it's supposed to scale easily enough geographically, but my company hasn't tried scaling it yet. It shouldn't be a big problem to scale the solution.
How are customer service and support?
In terms of the technical support for GitLab, I mainly use the forums and support sites of the solution. I don't use the direct technical support line of GitLab.
How was the initial setup?
The initial setup for GitLab is simple mainly because of all its features that allow you to make a startup instance of the solution simpler and quicker, and that's very good.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
We evaluated Azure DevOps, but we liked the style of how things are built up inside GitLab for the end-user and the developer more compared to Azure DevOps, though Azure DevOps is also a very good choice.
What other advice do I have?
I'm using the latest version of GitLab.
My company has a small team and only has six users of GitLab.
On a scale of one to ten, where one is the worst and ten is the best, my rating for GitLab, in general, is nine. My company likes the solution very much, especially over Azure DevOps.
I would recommend GitLab for others to use.
My company is a customer of GitLab.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Engineering Quality Analyst at Visteon Corporation
Issue-free, straightforward to set up, and reliable
Pros and Cons
- "The scalability is good."
- "Perhaps the integration could be better."
What is our primary use case?
I primarily use it for verifying some things. We're using it as a repository. It's used for software code.
What is most valuable?
I didn't have an option when coming to this solution. It was imposed on me. That said, I've had no problems so far.
The solution is stable.
The scalability is good.
My understanding is that the setup is straightforward.
What needs improvement?
I'm not sure of the complete capabilities of the tool as I don't use it that much. Perhaps the integration could be better.
For how long have I used the solution?
I've used the solution for one year, however, not so regularly.
What do I think about the stability of the solution?
I have not heard of any stability complaints. My understanding is that the product is reliable. There are no bugs or glitches. It won't crash or freeze.
What do I think about the scalability of the solution?
We have about 100 people using the solution in our organization.
For our purposes, we find the solution scales well. It's okay. We've never had any issues.
Which solution did I use previously and why did I switch?
We previously used IBM CLM and RTC.
How was the initial setup?
I did not directly handle the initial setup. There is an IT team, which is responsible for all the installation and setup tasks. I'm not sure how many people were involved in the deployment and maintenance of the solution.
What about the implementation team?
Our IT team set the solution up.
What was our ROI?
I haven't looked into if we have noticed an ROI or not.
What's my experience with pricing, setup cost, and licensing?
I can't speak to the exact cost or licensing structure. I don't deal with this aspect of the product.
What other advice do I have?
I'd recommend the solution to others. I'd rate it eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Tool Manager at a computer software company with 10,001+ employees
Good for CI/CD and version control, highly scalable, and very easy to set up
Pros and Cons
- "CI/CD is very good. The version control system is also good. These are the two features that we use."
- "I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version."
What is our primary use case?
We use it for version control and CI/CD.
What is most valuable?
CI/CD is very good. The version control system is also good. These are the two features that we use.
What needs improvement?
Its security features are very expensive. The Ultimate version is very expensive.
I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version.
For how long have I used the solution?
I have been using GitLab for five years.
What do I think about the stability of the solution?
It is very stable. In five years, we had to fix it only once.
What do I think about the scalability of the solution?
It is very scalable. We have about 2,000 users, but as per the reference architecture documentation, it can be scaled up to 50,000 users.
How are customer service and support?
We are using the open-source free version. So, we don't have support. We are looking to buy the intermediate version or Premium version.
How was the initial setup?
It was very easy to set up.
What about the implementation team?
We set it up by ourselves. We also update it, and we don't have to turn it off.
What's my experience with pricing, setup cost, and licensing?
We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive.
Which other solutions did I evaluate?
We are evaluating its Premium version, and we are also evaluating other products like GitHub.
What other advice do I have?
I would rate it a nine out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free GitLab Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2025
Product Categories
Application Security Tools Build Automation Release Automation Static Application Security Testing (SAST) Rapid Application Development Software Software Composition Analysis (SCA) Enterprise Agile Planning Tools Fuzz Testing Tools DevSecOpsPopular Comparisons
SonarQube Server (formerly SonarQube)
ServiceNow
Snyk
Checkmarx One
Microsoft Azure DevOps
Veracode
Microsoft Power Apps
Appian
Coverity Static
Black Duck SCA
Red Hat Ansible Automation Platform
Mend.io
GitHub Advanced Security
JFrog Xray
OpenText Core Application Security
Buyer's Guide
Download our free GitLab Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- How does Microsoft Azure DevOps compare with GitLab?
- If you had to both encrypt and compress data during transmission, which would you do first and why?
- When evaluating Application Security, what aspect do you think is the most important to look for?
- What are the Top 5 cybersecurity trends in 2022?
- What are the threats associated with using ‘bogus’ cybersecurity tools?
- We're evaluating Tripwire, what else should we consider?
- Which application security solutions include both vulnerability scans and quality checks?
- Is SonarQube the best tool for static analysis?
- Why Do I Need Application Security Software?
- Which Email Security enterprise solution would you choose: Cisco Secure Email vs Forcepoint Email Security vs Barracuda Email Security Gateway?




















