GitLab is predominantly used for software development and practicing DevOps. GitLab CI/CD is one of the best features, and the solution is used primarily for software development.
Co-Founder at Fineshift Software Pvt Ltd
Robust software development tool with excellent new features and good support
Pros and Cons
- "They incorporate new features every September, and they have introduced their own code editor and AI features."
- "The pricing has been substantially increased, which is a major concern."
What is our primary use case?
What is most valuable?
GitLab is robust software and easy to use. There is excellent documentation available on their site but it can be overwhelming for early learners.
They incorporate new features every September, and they have introduced their own code editor and AI features.
What needs improvement?
The pricing has been substantially increased, which is a major concern. While GitLab has a lot of documentation, the complexity and volume can be overwhelming, especially for new learners. Structuring the documentation more effectively could help alleviate this issue.
For how long have I used the solution?
GitLab was resold for approximately two years.
Buyer's Guide
GitLab
January 2025
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,020 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is stable, and there have been no noted glitches or latency issues.
What do I think about the scalability of the solution?
The solution is easy to scale.
How are customer service and support?
Customer service and support are good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously we worked as resellers of other IT software like Snyk and Aqua Cloud Security.
How was the initial setup?
The initial setup is medium in terms of difficulty. It's neither too easy nor too difficult.
What's my experience with pricing, setup cost, and licensing?
Pricing is relatively expensive.
Which other solutions did I evaluate?
Previously explored solutions like Snyk and Aqua Cloud Security.
What other advice do I have?
GitLab is a very good solution.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
Last updated: Oct 27, 2024
Flag as inappropriatePrinciple Product Manager at a healthcare company with 10,001+ employees
Improved our CI/CD processes in software dependency management
Pros and Cons
- "The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."
- "There is a need to improve or adopt AI into the ecosystem like a co-pilot, which Microsoft has done with GitHub."
What is our primary use case?
We primarily use GitLab for code migration and version management. It helps us maintain metadata, manage versions, and facilitate continuous integration when working in teams. When working on a feature, we create a feature branch, which allows us to work on the feature independently. Once the feature is complete, it must be merged into the main branch. This streamlines the process of deploying the application to the production environment.
How has it helped my organization?
We use some orchestration tools to do it. We have our own built packet manager, and that package manager interacts with the excellent migration and everything internally.
What is most valuable?
The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline.
What needs improvement?
There is a need to improve or adopt AI into the ecosystem like a co-pilot, which Microsoft has done with GitHub.
For how long have I used the solution?
I have been using GitLab for nine years. I have worked across version management for continuous integration and deployment.
What do I think about the stability of the solution?
The product sometimes crashes.
I rate the solution’s stability a seven out of ten.
What do I think about the scalability of the solution?
The solution’s scalability is good.
I rate the solution’s scalability an eight out of ten.
Which solution did I use previously and why did I switch?
I have used GitHub before. GitHub now comes with an AI Assistant, similar to a copilot, its most significant advantage. With this copilot, it assists you in writing code. It provides examples and helps you rectify errors, especially during migration processes. Additionally, it offers previews of how migration can be performed. These enhancements are attributed to Microsoft’s support and involvement in OpenAI.
How was the initial setup?
The initial setup is easy and depends on the target enrollment; it typically takes just a few minutes to complete. Migration is also handled efficiently, typically in less than a few minutes or between three to five minutes, depending on the data size you want to migrate. The only drawback or consequence is that you need a private Git repository, which GitLab should provide by default.
What's my experience with pricing, setup cost, and licensing?
For small-scale usage, GitLab offers a free tier. For enterprise pricing, GitLab is more expensive than GitHub, as it's not as widely adopted. GitLab is the preferred choice for many developers despite its higher monthly pricing plan, which is around $126.
What other advice do I have?
GitLab has improved our CI/CD processes in software dependency management. It handles conflicts between versions seamlessly, such as when merging different features into the main branch. With GitLab, there are no conflicts in the code itself. Versioning is also efficiently managed within GitLab, allowing us to easily track the latest main branches, previous branches, and releases. For example, if a software depends on specific versions, it's easily traceable using GitLab. One of the most significant advantages is the built-in DTS, which supports ample file storage. This capability allows us to store 30-40 gigabytes of repository sizes.
The code diffs available in GitLab show the differences between the older version and the current one, indicating what has been added, deleted, or modified across the codebase. This helps you understand which portions of the code have changed within a particular file, such as a Python script, aiding in traceability and version management.
The merge request feature is standard and available even in GitHub, making it accessible on most Git platforms. It is one of the fundamental features of GitLab, a free product.
Overall, I rate the solution a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
GitLab
January 2025
Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,020 professionals have used our research since 2012.
Delivery Head - DevOps at Datamato Technologies
A single platform that is lean and easy to manage
Pros and Cons
- "The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
- "Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."
What is our primary use case?
We are using this solution for DevOps adoption primarily.
What is most valuable?
The best part of the solution is it's a single platform, and this platform can help you do your required management, your source code management, your build management, your test management, artifact management, deployment management, et cetera. If this solution was not there, you'd have to put three or four different products together to do all the activities. With this, we are using one single product, including security. Everything is happening on a single platform. It is lean and easy management with no complexities and no integration issues. This one platform is able to do everything for us.
The solution has an established roadmap that lays out its plans for upgrades over the next two to three years.
What needs improvement?
The release schedules are quite clear. Even if I'm expecting some improvement, the improvement release cycles are already there in place. So even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still.
For how long have I used the solution?
We have been using the solution for a year.
What do I think about the stability of the solution?
The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
We are using an on-premises deployment, and on-prem will always have challenges with scalability. On-premises infrastructure never has elasticity since everything is fixed. If I have 500 servers, I have only 500. I cannot grow them to a thousand in a minute. My storage is going to be limited.
Our users are not more than 500 users. So for us, the scaling we have fits.
I myself being a DevOps consultant, have seen deployments for 2000 or even 3000 users also.In that sense, there is an issue of scalability. The infrastructure we have means the solution will be quite scalable for the next three years.
Which solution did I use previously and why did I switch?
We have tried out a lot of other products, including Azure DevOps. We have tried a lot of open-source products as well. The major benefit we found in this solution is it's a single platform doing everything. If I go to Azure DevOps, Microsoft would also say it's a single platform, yet it's not a single platform. They have integrated themselves with multiple toolchain vendors, and it's a Microsoft wrapper on the top. When it comes to Microsoft is a resource-hungry solution. You require a lot of resources to run on Microsoft.
How was the initial setup?
The deployment is fairly easy. The people who are doing the deployment should be very clear about the fundamentals, like any adoption, like when you're doing a DevOps adoption and moving towards automation.
The most important part is you really have to work on education. On the one hand, you have the investment, however, the investment will never show you how to use it. Once the adoption grows in the organization, you'll be able to see the returns and the benefits that are there.
We are currently in a phase of adoption across the organization. It's going on very well, and deployment is fairly easy. I didn't find much difficulty when doing deployment and getting people to work with it. Anybody who works on DevOps toolchain implementation can even go and implement GitLab also. It's that easy.
What was our ROI?
We have a new adoption going on and within a year we'll begin to see a return on investment.
What's my experience with pricing, setup cost, and licensing?
GitLab is a paid version, Ultimate GitLab. It has three editions: one is a free edition or a community edition. They have a premium edition, which is a paid version. Then, they have the ultimate edition, which is also a paid edition.
There are no hidden costs or fees associated with the product. I pay one price and get everything I need.
What other advice do I have?
We are using GitLab Ultimate.
As a DevOps consultant, I would like to give advice some. From 2008 or 2009, when the global market started adopting DevOps, until the year 2019 or 2020, we always had a problem. If I wanted to have DevOps automation in the organization, we would require four or five tools minimum. Since GitLab in 2020 emerged as a single platform, always advise people who are implementing DevOps to always move towards a single platform.
The reason is that you save a lot of money on your infrastructure costs. You also save a lot of money on the resources which are required to maintain all infrastructure for a single platform. And if you maintain a single platform, you'll require an optimized resource tool to maintain that.
If you're going to have multiple tools in your infrastructure for DevOps, you require many people to maintain that. In the end, everything boils down to cost. Cost is definitely high if you need to maintain infrastructure with multiple toolchains. So my advice is always, when we talk about agility, to be lean. So when you bring in GitLab, you get a lean infrastructure; you get a simple and non-complex infrastructure. You have minimum compliance issues and minimum regulatory issues.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Salesforce Release Engineer at Cognizant
Helps to integrate CI/CD pipeline deployments and has good security model
Pros and Cons
- "The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
- "GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users."
What is our primary use case?
I use the tool for deployment.
What is most valuable?
The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good.
What needs improvement?
GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users.
For how long have I used the solution?
I have been working with the product for six years.
What do I think about the stability of the solution?
I haven't encountered any bugs in GitLab.
What do I think about the scalability of the solution?
In our company, I estimate that around 30 people use GitLab, primarily for branching and repository management.
Which solution did I use previously and why did I switch?
Our organization decided to use GitLab because it's easy to use, and its user interface is more intuitive than other tools.
How was the initial setup?
The tool's deployment is easy.
What other advice do I have?
I would recommend using GitLab. It provides a repository and API, allowing you to create deployment pipelines. I rate it a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Test Manager at ASELSAN
Complete solution for issue management and CI/CD, with a great UI
Pros and Cons
- "The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI."
- "For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
What is our primary use case?
In some of the projects we are involved with, we use GitLab for the purposes of issue management and as a configuration management tool. Along with GitLab, we also use the core Jira software for issue management functionality, as well as GitLab Runner for its CI/CD tools.
Our internet connection runs on a different infrastructure to the greater internet system, so we are using on-premises versions of all these solutions. Because nothing is cloud-based, we don't need much in the way of firewall or security solutions.
What is most valuable?
The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI.
What needs improvement?
For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better.
The main shortcoming is that with some parts of GitLab, things can get quite complex. Especially in the beginning, the learning curve can be a bit steep and it takes some time to learn how to use the tools. That said, once you understand the mentality of it, it becomes easy.
For how long have I used the solution?
We have been using GitLab for about five years.
What do I think about the stability of the solution?
We have had no instability issues with GitLab. When it comes to maintenance, we have IT departments that deal with that, and I am not directly involved in the maintenance of the tools themselves so I don't know if it's difficult to maintain or not.
What do I think about the scalability of the solution?
We haven't yet tried to scale it past the 100 or so users in my organization.
Which solution did I use previously and why did I switch?
We haven't used any other similar solution before GitLab.
How was the initial setup?
In some areas, the initial stages of using GitLab can be complex and presents a steep learning curve. It takes some time to learn and use all the tools properly, but once you understand the mentality behind it, it is not that difficult.
What about the implementation team?
We didn't implement GitLab ourselves as we have IT departments that take care of that process. I am unsure as to whether they used any external consultants or deployed it themselves, however.
What's my experience with pricing, setup cost, and licensing?
In total, I believe we have more than 300 licenses spread over about 100 users, though I can't comment on the costs involved.
What other advice do I have?
GitLab is a wholly complete solution and it is for this reason that I can recommend it to other users.
I would rate GitLab a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Cloud architect at DTech Cloud
Works as a source code manager or version control manager
Pros and Cons
- "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."
- "In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial."
What is our primary use case?
We use the solution as a source code manager or version control manager.
What is most valuable?
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.
Many global users prefer GitLab for its enhanced pipeline automation for CI/CD features. It stands out among source code managers due to its parent-child pipeline feature. If users want to leverage this feature, they should consider using it. It’s not the only platform with this capability, but GitLab excels in automating many operations and offers integration with other platforms.
The solution supports platforms like Azure, GCP, and AWS. This capability makes it a preferred choice, even though other platforms also offer similar integration features. Additionally, GitLab’s tendency to be independent of ownership by another major company makes it an attractive option for many developers who prefer cloud usage
The tool's UI is good.
What needs improvement?
In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial.
For how long have I used the solution?
I have been working with the product for more than six months.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The product is scalable.
How are customer service and support?
The tool's technical support is great.
What's my experience with pricing, setup cost, and licensing?
The solution is free.
What other advice do I have?
I rate the overall product an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 17, 2024
Flag as inappropriateVersion control history is valuable for our development workflow
Pros and Cons
- "I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."
- "I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
What is our primary use case?
We create the pipeline and push it to GitLab to initiate the process. The cloud integration is straightforward.
How has it helped my organization?
When it comes to GitLab's CI/CD integration, it significantly supports our development process by accelerating deployments. With automated pipelines, we can focus more on development tasks without worrying about manual deployments, ultimately speeding up our development cycle.
What is most valuable?
In GitLab, I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently. I haven't utilized GitLab's security scanning capabilities yet.
We plan to integrate tools like Sonicheap for code security. Currently, we use another product for security, focusing on Q4 security points.
We have used GitLab's features selectively for added security. We don't store passwords directly but use a secret manager and tools to sync passwords securely to our deployment environment.
What needs improvement?
I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities. Better integration and usability within the pipeline could make a significant difference in user experience. I would suggest considering new features or functions that could streamline workflows further and make using GitLab even more efficient. Having additional functionalities that cater to specific needs could greatly enhance the overall experience with the platform.
For how long have I used the solution?
I have been working with GitLab for the past 5 years.
What do I think about the stability of the solution?
Regarding stability, while I can't rate it on a scale of one to ten, I can say that we've experienced good stability with GitLab, with no downtime or major issues.
What do I think about the scalability of the solution?
When it comes to scalability, I can't provide a rating as we're using the enterprise version and haven't explored scalability yet in terms of user count, we have between three hundred and four hundred users in our company or department.
How are customer service and support?
I've had support from forums like Stack Overflow when needed. In my experience, GitLab integrates well with third-party tools like SonicWall and Slack without any major issues.
How was the initial setup?
The setup process for GitLab is straightforward and easy to use.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
When comparing GitLab to competitors like Bitbucket, I find GitLab to be superior, especially in terms of features and functionality. Bitbucket still has its own strengths and is preferred by some organizations.
What other advice do I have?
Overall, I would rate GitLab around eight or nine out of ten. I highly recommend it to other users for both company purposes and personal projects. GitLab provides a solid starting point for learning and working efficiently, making it a valuable tool for developers.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
DevOps Engineer at NayaPay
A highly stable and affordable solution that provides good repository management features and support
Pros and Cons
- "CI/CD is valuable for me."
- "The documentation is confusing."
What is our primary use case?
We use the solution for on-premises repository management
What is most valuable?
CI/CD is valuable for me. The product also has a monitoring feature connected to Grafana. It helps with alerts. We are using the free GitLab Community Edition. It has a lot of great features.
What needs improvement?
The documentation is confusing. Sometimes, it is incomplete or has incorrect information. I have informed the vendor about it. Some features in the GitLab Community Edition are not available to us.
For how long have I used the solution?
I have been using the solution for nine months. My organization has been using it for around two years. We are using the latest version of the solution.
What do I think about the stability of the solution?
I rate the tool’s stability a ten out of ten. We never faced any downtime.
What do I think about the scalability of the solution?
I rate the scalability of GitLab Community Edition a seven or eight out of ten. The product could improve the scalability of GitLab Community Edition. Around 60 people are using the product in our organization.
How are customer service and support?
Their support is good.
How was the initial setup?
The initial setup is easier for someone who knows Linux and has been working as a system administrator. We need to have experience to deploy the solution. It takes around three to four hours to deploy the solution.
What's my experience with pricing, setup cost, and licensing?
We are using the open-source version, anyone can download it.
What other advice do I have?
I am my company’s GitLab administrator. Many features we need are available in Enterprise Edition. If we say that we do not have enough features in GitLab Community Edition, GitLab might just ask us to upgrade to Enterprise Edition. Overall, I rate the product a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free GitLab Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 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)
Veracode
Snyk
Checkmarx One
Mend.io
Fortify on Demand
Sonatype Lifecycle
Acunetix
GitHub Advanced Security
PortSwigger Burp Suite Professional
HCL AppScan
Qualys Web Application Scanning
GitHub
Klocwork
Tenable.io Web Application Scanning
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?
- Which application security solutions include both vulnerability scans and quality checks?
- We're evaluating Tripwire, what else should we consider?
- 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?