IT Central Station is now PeerSpot: Here's why

GitLab OverviewUNIXBusinessApplication

GitLab is #1 ranked solution in top Build Automation tools, #2 ranked solution in top Software Composition Analysis (SCA) tools, #3 ranked solution in top Release Automation tools, #4 ranked solution in AST tools, and #4 ranked solution in top Enterprise Agile Planning Tools. PeerSpot users give GitLab an average rating of 8.2 out of 10. GitLab is most commonly compared to Microsoft Azure DevOps: GitLab vs Microsoft Azure DevOps. GitLab is popular among the large enterprise segment, accounting for 65% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a comms service provider, accounting for 21% of all views.
GitLab Buyer's Guide

Download the GitLab Buyer's Guide including reviews and more. Updated: August 2022

What is GitLab?

GitLab is a single application with features for the whole software development and operations (DevOps) lifecycle.

GitLab Customers

Siemens, University of Washington, Equinix, Paessler AG, CNCF, Ticketmaster, CERN, Vaadin

GitLab Video

GitLab Pricing Advice

What users are saying about GitLab pricing:
  • "I'm not aware of the licensing costs because those were covered by the customer."
  • "I think that we pay approximately $100 USD per month."
  • "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 Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Manager at a tech vendor with 5,001-10,000 employees
    Real User
    Top 5Leaderboard
    A double-sided solution for both DevOps and version management
    Pros and Cons
    • "I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."
    • "There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great."

    What is our primary use case?

    I'm part of the application development team comprising 10-12 developers and I have used GitLab for configuration and version management. We have also used it for DevOps, but I have not been involved in the DevOps side. My work with GitLab involved basic version management (i.e. checking in, checking out, merging) and related features. 

    I have also used GitLab for doing remote builds, which is when you check in and it triggers the build on the application remotely. For example, we have a YAML script that has been written for performing builds on GitLab automatically and when that script gets executed, it performs the builds and copies them to the destination folder. All of this gets triggered from GitLab.

    What is most valuable?

    I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand.

    What needs improvement?

    There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great.

    For how long have I used the solution?

    I have used GitLab for two months.

    Buyer's Guide
    GitLab
    August 2022
    Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: August 2022.
    621,593 professionals have used our research since 2012.

    What do I think about the stability of the solution?

    It's stable. 

    What do I think about the scalability of the solution?

    Once all the scripts are written, it becomes scalable. When an application gets deployed and people start using it, it's on the cloud and so it becomes scalable. All the applications that we design are deliberately written in such a way as to be scalable.

    How are customer service and support?

    We only used GitLab for a short duration, so there was not much scope or need for contacting technical support.

    How was the initial setup?

    The setup is straightforward to an extent because the part of GitLab that I was using for version management was similar to other tools that I have used such as Git and SVN. When I use GitLab, it's more or less the same process and workflow as these other tools, so there wasn't a big learning curve for me.

    Our application was an accumulation of multiple applications, so there were multiple builds happening at any given time. GitLab would process the builds and it would take only a couple of hours for us to deploy the builds on the cloud.

    The other thing is that the GitLab user interface is good, so it's easy to understand. You, yourself, can learn it simply by exploring and trying it out. Then there's a lot of help that is available on the GitLab website on how to use it. 

    What about the implementation team?

    For the implementation, we had a DevOps engineer who was the primary technical guy, and then the others were developers and related entities performing the development.

    What was our ROI?

    Personally, I can't say much about the return on investment because the licensing and costs and everything have been borne by our customer. We were just using it. But I think that the return on investment must be good, and it might be one of the reasons why the customer is using it for all their projects.

    What's my experience with pricing, setup cost, and licensing?

    I'm not aware of the licensing costs because those were covered by the customer.

    What other advice do I have?

    I can certainly recommend GitLab. It's a good product and I would rate it an eight out of ten.

    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.
    Flag as inappropriate
    PeerSpot user
    Technical Lead at a mining and metals company with 51-200 employees
    Real User
    Top 5
    Helpful interface facilitates peer code reviews, and the continuous integration features are good
    Pros and Cons
    • "GitLab offers a good interface for doing code reviews between two colleagues."
    • "We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."

    What is our primary use case?

    My daily usage involves fetching code, creating branches, modifying the code, and then committing my changes. Once I'm ready for a review with my colleagues, I create a merge request. Then, during a code review, they will use the interface to write comments. Once everything in the comments has been addressed, I complete the merge. This describes a typical scenario.

    We develop under Linux.

    How has it helped my organization?

    Everybody needs a source code versioning assistant, and GitLab is very flexible in this regard. 

    What is most valuable?

    GitLab offers a good interface for doing code reviews between two colleagues.

    The continuous integration feature is good.

    What needs improvement?

    We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating. In general, integrating with third-party tools is easy for some but difficult for others. When I create a new project, I go through all of the settings, and then I can integrate that with other tools. However, with Jira, I have problems.

    If we could have GitLab execute some of the system tests then it would be good because as it is now, we have to rely on another tool. Ideally, it would execute a system test, a unit test, and then create a report. It is possible to do it but requires a lot of scripting expertise. 

    It should be easily available on their menu, similar to adding tests, configuring the tests you want to execute when you launch a build, so the build would be done then tests would be performed, and the report would be created.

    This would allow us to know what went wrong during our systems test. If this aspect was more integrated into their interface, instead of relying on developers to script everything, it would be easier.

    I would like to see better integration with third-party software.

    For how long have I used the solution?

    I have been using GitLab for a bit more than a year.

    What do I think about the stability of the solution?

    GitLab is pretty stable. I would rate it an eight out of ten.

    What do I think about the scalability of the solution?

    I haven't really used it outside of our Linux development environment, so I cannot really tell.

    How are customer service and technical support?

    GitLab is not responding quickly enough to our request. I know one of the problems that I am experiencing is with the integration with Jira.

    We submitted the request to GitLab and we did not receive any replies. That was back in October.

    Technical support could be better and their response time needs improvement to respond more quickly.

    How was the initial setup?

    Since I am using the web-based version and accessing GitLab through the web, I didn't have to install Gitlab, so in that sense, there was no effort, obstacles, or challenges in the initial setup.

    I needed to understand the menu.

    When I create a new software project in GitLab, I need to go through all of the settings to configure everything, which was not a problem. I needed to understand all of the options, and what it was doing.

    What other advice do I have?

    I would rate this solution an eight out of ten.

    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.
    PeerSpot user
    Buyer's Guide
    GitLab
    August 2022
    Learn what your peers think about GitLab. Get advice and tips from experienced pros sharing their opinions. Updated: August 2022.
    621,593 professionals have used our research since 2012.
    Partenaire, CEO at a tech services company with 1-10 employees
    Real User
    Top 5Leaderboard
    Convenient to use, provides a central repository, and speeds up our development time
    Pros and Cons
    • "It speeds up our development, it's faster, safer, and more convenient."
    • "I would like to see better integration with project management tools such as Jira."

    What is our primary use case?

    We are a startup company working on a new firewall product, and we use GitLab as part of the software development process.

    How has it helped my organization?

    I see this product as an investment. It speeds up our development, it's faster, safer, and more convenient. We know that all of your information is going to be in the same place and you can do what you want.

    What is most valuable?

    The most valuable feature of GitLab is the level of control that it offers. I have more control over everything.

    What needs improvement?

    I would like to see better integration with project management tools such as Jira. I know that integration does exist for some, but it can be better. In the future, I would like to be able to add what I want.

    For how long have I used the solution?

    I have been using GitLab for one year.

    What do I think about the stability of the solution?

    This product is fully stable.

    How are customer service and technical support?

    We have not used GitLab technical support because as of now, we haven't needed it yet.

    Which solution did I use previously and why did I switch?

    Prior to using GitLab, I was using GitHub.

    How was the initial setup?

    The initial setup is not complicated. Especially if you have used GitHub before, it is pretty easy. Being on the cloud, you don't have to buy a server or anything else. You pay for it, set it up, and all of the protection and other services are included.

    What's my experience with pricing, setup cost, and licensing?

    GitLab can be used free of charge but if you use it for years and move to a paid license then it is better because you have more services. I think that we pay approximately $100 USD per month.

    What other advice do I have?

    We strive to always have the latest technology. In this business, you have to follow your client and follow the trend. In fact, you have to do things ahead of the trend and be prepared. For us, this tool is really convenient.

    My advice for anybody who is implementing this solution is to consider the paid version. Don't be afraid to pay a few dollars a year. Especially for a startup company, this tool is an investment. You don't have to look at it as an expenditure or expense. Don't think about it as spending money, but rather, investing money.

    From my point of view and for what I use GitLab for, it is okay for me. There may be other products, but this is a great tool. It's convenient and it's used by a million developers. The developers here consider it to be the best choice. That said, there is always room for improvement in a product.

    I would rate this solution a nine out of ten.

    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.
    PeerSpot user
    IT Processes Methodologist at Gysan Gmart
    Real User
    Top 20
    Easy to use, easy to install, and offers an open-source option
    Pros and Cons
    • "Of all available products, it was the easiest to use and easy to install."
    • "The solution should be more cloud-native and have more cloud-native capabilities and features."

    What is our primary use case?

    I've used the solution just for my learning purposes. My company is using currently GitLab. We are using it for our CI/CD purposes for continuous integration and continuous deployment.

    How has it helped my organization?

    To my knowledge, my company started to use it as there were no decent alternatives to GitLab when they started to use it. The only decent alternative was GitHub, however, it was lacking in the CI/CD pipeline capabilities. At that time there were no GitHub actions available at the moment.

    What is most valuable?

    Of all available products, it was the easiest to use and easy to install.

    What needs improvement?

    The solution should be more cloud-native and have more cloud-native capabilities and features. It should be more GitOps-ready.

    For how long have I used the solution?

    I started using the solution a year ago. My company has used it for four years.

    What do I think about the stability of the solution?

    I cannot speak to how stable the solution is. From what I have seen so far, there were no serious issues with GitLab.

    What do I think about the scalability of the solution?

    Approximately four to five developers and maybe a couple of QA testers and a couple of DevOps engineers are responsible exclusively for GitLab maintenance and support.

    How are customer service and support?

    Technical support has mostly been good.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    I tried to learn a little bit about Jenkins, however, it was only through some internet content.

    How was the initial setup?

    At the moment of the GitLab acquisition, I was not working for the company. I did not handle the implementation process.

    We need at least a couple of technicians, engineers, for deployment and maintenance. 

    What about the implementation team?

    Our own technical team handled the deployment. 

    What's my experience with pricing, setup cost, and licensing?

    When I was hired (in 2020) they told me that they were using an open-source version. I'm not sure if that's still the case as it's a quite big company. Nowadays they should be using some kind of paid version, as the demand is pretty high, as far as I know.

    I'm not sure of the exact licensing costs. 

    What other advice do I have?

    We are customers and end-users.

    As far as I know, we are using the on-premise version. There are two versions of GitLab - the on-premise and the cloud version. We are using on-premise. As far as I know, we also keep making sure it's up-to-date.

    I'd rate the solution 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.
    Flag as inappropriate
    PeerSpot user
    User at a real estate/law firm with 10,001+ employees
    Real User
    Top 5
    Stable and useful for pipelines, but needs better pricing and better integration with Kubernetes
    Pros and Cons
    • "GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable."
    • "Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes."

    What is our primary use case?

    We are using it for pipelines, continuous integration, and continuous deployment. 

    In terms of deployment, it can be a cloud solution, but we have installed it on our site on Azure.

    What is most valuable?

    GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable.

    What needs improvement?

    Its price should be improved. It is very expensive.

    Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes. 

    From the DevOps perspective, the way we deploy applications is too complicated. It needs to be simplified. It is very development-oriented, and it works very well for DevOps, but when you are at the group level, you want it to be simple and more oriented towards the process. The automation process to deploy is not a very good part of GitLab.

    For how long have I used the solution?

    I have been using this solution for three or four years.

    What do I think about the stability of the solution?

    It is stable.

    What do I think about the scalability of the solution?

    Its scalability is fine. We have 200 developers in our organization. 

    How are customer service and technical support?

    We have been doing okay on our own. We are able to find support inside our company.

    How was the initial setup?

    Its initial setup is okay. We did the installation in three months, but it was very slow and complicated to develop the continuous deployment during these three years for each application. We had to develop pipelines for multiple development languages.

    We are quite well organized now, but it took a long time to think about which pipeline to use with GitLab. We now have five pipelines. We have the infrastructure pipeline, the middleware pipeline, the image pipeline, the security pipeline, and the application pipeline.

    We have a team of 10 people for its deployment. They are admins and managers.

    What's my experience with pricing, setup cost, and licensing?

    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. 

    Which other solutions did I evaluate?

    We are using the Azure Cloud solution, and we are thinking of trying the Azure DevOps solution this year. 

    What other advice do I have?

    I would recommend this solution to others. The product is fine, but you have to do the integration with different pipelines.

    I would rate GitLab a seven out of 10.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Head Of Software Engineering at a financial services firm with 201-500 employees
    Real User
    Easy to deploy and configure with very good CI/CD pipeline management
    Pros and Cons
    • "Everything is easy to configure and easy to work with."
    • "The only thing our company is really waiting on in terms of features is the development of metrics."

    What is most valuable?

    Overall, our team is happy with the solution.

    The CI/CD pipeline management is the solution's most valuable aspect.

    Everything is easy to configure and easy to work with. Our team finds it to be very user-friendly.

    Generally, the volume control is very good.

    What needs improvement?

    I've looked at GitLab's roadmap. The only thing our company is really waiting on in terms of features is the development of metrics. We're looking forward to being able to take advantage of them.

    For how long have I used the solution?

    We've been using the solution for two years at this point.

    What do I think about the stability of the solution?

    We've never had any issues with stability. We're very happy with the setup we have and it works well for our team. We haven't had any issues with the product crashing or freezing and I don't recall dealing with bugs or glitches.

    What do I think about the scalability of the solution?

    The solution is very scalable. I'm not sure how many nodes we have currently, however, it is scalable. If we need the extra capacity, I know we can build it out and use different setups.

    We have about 100 users in our company using the product.

    How are customer service and technical support?

    We've never needed to contact GitLab for technical support. I can't speak to the level of service their in-house team might give.

    Which solution did I use previously and why did I switch?

    We previously used SVN. We migrated everything over to GitLab.

    How was the initial setup?

    Our platform engineering team found the initial implementation pretty straightforward.

    Within the organization, deployment took about a week. That said, we had to spend three weeks migrating from SVN, which is what we were using before.

    There isn't really any maintenance required. It's not something we think about or worry about, really.

    What other advice do I have?

    We're just a customer. We don't have a professional relationship with GitLab.

    We're using the latest version of the solution right now.

    I would definitely recommend the solution to other organizations. It's pretty easy to use and can scale if you need to. It's stable as well. We're not really missing any features. It's great.

    Overall, I'd rate GitLab nine out of ten. They can always improve, which is why I didn't give them a perfect score. What they are working on, based on their roadmap, is already quite impressive. We're looking forward to metrics coming down the pipeline later in the year.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Senior Solutions Architect at a tech company with 51-200 employees
    Real User
    Top 20
    Good price, scalable, easy to deploy, and easy to set up CI/CD and integrate with other tools
    Pros and Cons
    • "I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools."
    • "In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents."

    What is our primary use case?

    We are using it for building mobile applications and web applications. I am supporting the code in GitLab. It is only for giving access to my development team, and I just see what merge requests are coming.

    What is most valuable?

    I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools.

    What needs improvement?

    In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents.

    For how long have I used the solution?

    I have been using this solution for more than six months.

    What do I think about the stability of the solution?

    It seems stable.

    What do I think about the scalability of the solution?

    I didn't find any scalability issues so far. We have around 50 members who use this solution. Around 20 of them use it on a daily basis.

    How are customer service and technical support?

    One of my colleagues got in touch with them, and his response was that their technical support was not that great. The details that they provided for the question were not that great.

    Which solution did I use previously and why did I switch?

    We also use GitHub. Earlier GitLab was more favored, but now GitHub has everything that is there in GitLab. If GitHub is offering more, then there might be chances of switching to that. I am not attached to either of these solutions. If things are working better for me in GitHub, I will move to GitHub.

    How was the initial setup?

    It is simple. You just create one repo and then give access. It takes maybe 5 to 10 minutes.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    I would recommend this solution to others. I would rate GitLab an eight out of ten.

    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.
    PeerSpot user
    Product Development Team Lead R&D at a tech vendor with 1,001-5,000 employees
    Real User
    Web-based repository used for distributed programming and to store POC repositories
    Pros and Cons
    • "As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab."
    • "GitLab's Windows version is yet not available and having this would be an improvement."

    What is our primary use case?

    We use this solution for storing repositories for distributed programming. We have 15 to 20 users. We generally keep our POC repositories on GitLab.

    What is most valuable?

    As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab. 

    What needs improvement?

    GitLab's Windows version is yet not available and having this would be an improvement. This is compared to Azure Git where Microsoft provides us with the setup of virtual agents which you can download and set up quickly. Your laptop will become an agent which is connected to your cloud environment to execute the job which is triggered from the cloud environment. 

    For how long have I used the solution?

    I've been using GitLab as a developer for four to five years, but when it comes to practical implementation in my current organization, it's been about a year since we started shifting our repositories to this platform.

    What do I think about the stability of the solution?

    Absolutely, the solution is stable and satisfies our requirements. 

    What do I think about the scalability of the solution?

    Due to the relatively small number of users in our organization, I can't really comment on the scalability of this solution. 

    How are customer service and support?

    We have never needed to contact customer support. Whenever we had an issue, all the help we needed for a solution is on the platform or in the documentation.

    Which solution did I use previously and why did I switch?

    We used to use TFS repositories on the older versions of Microsoft.

    How was the initial setup?

    I have done a setup on-premise for GitLab and it was straightforward. The documentation is clean which is useful for the DevOps person who sets up the on-premise environment. Based on the documentation provided by GitLab, I have prepared my own documentation.

    To complete the deployment, it took me two to three days including downloading the artifact from the internet, getting the Linux server ready and setting up GitLab runner for CI/CD. I was the only person involved in the setup and we have 15 to 20 total users across our organization, almost all of them developers. 

    What other advice do I have?

    I rate this solution an eight out of ten. 

    Which deployment model are you using for this solution?

    Hybrid Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Other
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user