Skip to main content



What is GitLab?

GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts.…

Read more
Recent Reviews

The Best CI/CD Platform

10 out of 10
July 12, 2024
Primary use for GitLab is of course source/version control, allowing collaboration on projects such as writing code. But GitLab does much …
Continue reading

Solid and complete tool

9 out of 10
October 10, 2023
It's the main tool used to manage our git versioning, CI/CD, merge requests and repository for several of our projects. But we don't use …
Continue reading

Pipelines Rock

9 out of 10
October 03, 2023
Our organization has grown large enough such that managing individual projects is a bit of a pain. We try to delegate to our dev teams as …
Continue reading
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 9 features
  • Version History (9)
  • Branching and Merging (9)
  • Pull Requests (9)
  • Code Review Tools (9)

Reviewer Pros & Cons

View all pros & cons
Return to navigation


View all pricing

GitLab Essential


per month per user

GitLab Premium


per month per user

GitLab Ultimate


per month per user

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visit…


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation


Version Control Software Features

Version Control Software Features allow uses to manage and control document history and versions.

Avg 6.8
Return to navigation

Product Details

What is GitLab?

GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software.

Differentiators, as described by Gitlab:

  • Simplicity: With GitLab, DevSecOps can be achieved through a single platform with a user-friendly interface
  • Security: GitLab offers built-in security scans that provides a comprehensive security solution.
  • Transparency: The code base for GitLab is open to community contributions, to ensure transparency and an open-core approach.
  • Cloud-Agnostic: Can be deployed anywhere with no vendor lock-in

GitLab Screenshots

Screenshot of GitLab, a comprehensive DevSecOps platform.Screenshot of Security DashboardScreenshot of Merge Request

GitLab Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac, BSD* (Ubuntu 14.04 LTS or later), Android, iOS, full list see
Mobile ApplicationNo
Supported CountriesInternational
Supported LanguagesChinese, English, German, Japanese, Korean, Portuguese, Spanish

Frequently Asked Questions

GitLab starts at $0.

JFrog Artifactory, Jira Align, and Jenkins are common alternatives for GitLab.

Reviewers rate Branch Protection highest, with a score of 9.3.

The most common users of GitLab are from Enterprises (1,001+ employees).
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings


Attribute Ratings


(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
We use GitLab for storing our code repos as well as storing the applications that we use to test our product and test applications. We integrate GitLab with Jenkins, SonarQube, blueOcean, and a variety of other applications to ensure code quality in our CI/CD pipeline. We use GitLab to track changes to applications as well as have multiple versions. GitLab is great for version history as well.
  • Version history - having the ability to see when things were last changed and by who.
  • Integration with our other tools - to help ensure code quality.
  • Multiple repos.
  • Easy navigation.
  • Checking for duplications - we have ended up with two applications being the exact same for a while, and then one gets updated, and one doesn't cause issues.
I use GitLab to store our applications - GitLab makes it easy to make small changes in the online IDE and push changes to the rest of the team. We use GitLab to store our repos - Easy navigation between projects, and the versioning is top-notch. We integrated our CI/CD pipeline and GitLab, we manage code reviews, can track pipeline status, and if our integration tests fail, then the merge is blocked, which is great for not pushing code that will break our environments.
  • Better code quality.
  • Faster time to code reviews.
  • Pipeline works well with our other applications and reports all in one spot.
We migrated from Gerrit to GitLab, and minus a few minor bumps during migration, GitLab has been hands down better. Our devs have faster time to code review with notifications, the UI is easy to navigate and, and our pipeline is integrated and automated, so once everything is in place, our merges happen automatically. Gerrit was lacking in the UI, and notifications were hit or miss, so code reviews were delayed. Our pipeline is much smoother with GitLab.
We do not have a paid plan.
As stated, our code reviews are much faster with this integration; our unit tests and integration tests are triggered and reported back to GitLab, so we have all the information related to a code change in one spot rather than chasing pieces of information down to figure out what happened.
  • Integrations with our other CI/CD tools.
  • We integrate with Jira and the connection there is fantastic.
  • We integrate with Jenkins and can easily report build failures back to gitlab and block the merge.
  • Nothing particularly difficult, I do wish there was some better compare features when creating a new/updated code base because we have had issues with duplication.
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
Willian Molinari | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Gitlab was used by the entire engineering team (developers and operations) to hold all the code for all our projects. It was installed on-premise since we had 1000 projects to hold. All teams throughout the company used it on a daily basis to share code and discuss merge requests and issues.
  • Great interface for merge requests and issues.
  • Great community. It's easy to interact with and propose new stuff.
  • Used Gitlab community edition for years and it solved all my complaints during these years.
In case you have many repositories and want some on-premise, Gitlab is the best thing you can get. For new startups looking for a great a great (or free) place to have private repositories, Gitlab is the best option you will find as well. It also has an integrated CI for your project, which is really nice.
  • We were using Gitorious a long time ago and Gitlab helped us to get rid of it. Gitorious was really old and unmaintained, so we gave a new life to our developers.
  • We had to do our own packaging for the first versions because their Debian package was really bad at the time. Our package still remains to this time, but theirs are really better now.
Gitlab has a free version on-premise install, which makes it the best between them. Gitorious was our solution between Gitlab but it was abandoned for a long time. GitHub doesn't have a free version for private repositories. Bitbucket was not so good at the time and on-premise was not an option.
I only use the free version, tried the paid version but did not need it after all. For this reason, I don't have much to comment on the paid version of Gitlab.
Continuous integration is probably the best feature of Gitlab. The main Git hosting is great, but the way they do CI is awesome. Gitlab was one of the first to introduce CI and it was available for their own installation and also the open source version. I used both and they work great. I have nothing but positive things to say about it.
Yes, it certainly makes. Currently, I'm using Gitlab to host the source code for one of my clients and it certainly makes the code easy to collaborate. We use the full feature set: code hosting, CI, pull requests, etc. The interface is very clean and makes everything obvious for all developers. The fact that we can configure the CI via yml file in the source code is another plus.
I had the chance to use Gitlab when working on-premise and now working remotely for more than 3 years. In both cases, Gitlab enabled a great collaboration setup for my team. We used the open-source version installed locally at the time and now I'm using their own SaaS version. Both work seamlessly.
When using the open-source version, it prevented us to have a very expensive Github account to hold all of our repositories. Gitlab also helped us to not have a dedicated tool for review (like Gerrit) because we were able to rely entirely on their CI + Pull Request management infrastructure.
They are all developers. We use Gitlab as a way to sync our code and review each others' work.
Currently, it's a one-man's work. We are using the SaaS version of Gitlab. The free version is enough for our usage. It's current my role to make sure everything works as expected and buy the paid version if something else is needed. In general, there's not much to do, it just works. All the work we have to do is to improve our own process.
  • Code sharing
  • Easy review via Merge Requests
  • Easy CI to test our code on every change request
  • We use the CI to check our HTTPS certificate. On every build, we check DNSimple and upload the certificate to Heroku. It guarantees we always have the HTTPs certificate updated
  • We have the whole boad of directors on Gitlab so they can create issues and interact with developers there
  • All of our product tracking is done via Gitlab boards.
  • We want to use Gitlab CI to deploy a new app every time we create a new merge request so people can validate the app before merging
Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.
Long ago, when I first used Gitlab, we changed from Gitorious. Gitlab was still new, but way better than its competitor. Github was not an option for us at the time because it was too expensive. Gitlab proved to be a good choice with time.
  • Price
  • Product Features
Github was too expensive and we wanted to deploy something in our infrastructure. The open-source version of Gitlab was exactly what we wanted. It had less features but became feature-complete for us quickly.
I wouldn't change anything. We evaluated other competitors and Gitlab was clearly the winner.
We were using the open-source version, but even when using the free version, I didn't need support. When I faced a problem, I provided a Merge Request to the community version or opened an issue to the code directly. Their response was usually very good.
Yes, I did via Gitlab issues. The development team was very responsive. I was able to fix the problem myself and provide the code for the open-source version, which was promptly accepted.
I found a problem after installing a new version. I was able to reproduce myself and fixed in my local environment. I proposed a change via Merge Request and their response came in a few hours asking for more tests. I implemented them and my change was accepted some minutes after my push. The experience was great.
  • CI configuration via yaml file is great. You can just use a default and do your changes via version control
  • I like the way their Merge Requests work. They had many features implemented before Github.
  • If you use the open-source version, you have to do the updates yourself. They have a good changelog, but it's up to you to manage the whole infrastructure. It's not a problem with Gitlab itself, but it takes time to get used to it.
I don't use it very much but their website is responsive. It seems to work well.
I like it a lot. To me, it feels very simple than other systems I used in the past. Version control is not something easy and they make it simple and easy to use. The whole experience their platform provides is just great.
Score 9 out of 10
Vetted Review
Verified User
I use Gitlab both personally and professionally. I have also used it at several organizations. In my current organization, it is being evaluated for rollout as a company wide version control standard.
  • Pipelines: Gitlab Pipelines is an excellent way to get started with pipelines easily and without much overhead. And with it being all encapsulated within Gitlab itself, it makes integrating your code into that pipeline even easier. Just a little bit of code and VOILA. You have at least a minimum viable pipeline.
  • VCS: Gitlab is, of course, a great version control system.
  • Usability: Gitlab has really put a significant amount of focus into usability. They've drilled down and ensured that the way companies and individuals need to use the tool, they can.
  • Groups: Gitlab makes setting permissions on projects extremely easy. Other version control systems make it more difficult to set things granular enough, but gitlab allows you to group things in a granular enough way for your projects.
  • In some ways, it's more difficult to navigate the web UI than I would like. Could be an overload of options, or could just be the difference of switching between different version control systems.
Gitlab is extremely well suited for an enterprise VCS solution. It's also great for personal projects as well. Best part is: it's free up to a certain point which allows you to properly evaluate the solution for your organization.
Gitlab's pipeline solution is by far the best when compared to Bitbucket and GitHub. GitHub's "actions" being relatively new. Gitlab is by far superior in overall reliability, extensibility, and functionality when compared to Bitbucket and run's relatively even with GitHub.
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft.
Chef, Terraform, Consul, Bitbucket, Bitbucket Server (formerly Stash), GitHub
Gitlab makes team collaboration a breeze. Literally a life saver keeping me from having to keep track of all these different tools for artifact storage, pipelines, code management, issue tracking, etc. Doing it all in Gitlab just makes things WORK. It also helps standardize platforms so you do not have teams using 20 different tools to accomplish the same goal.
Using Gitlab really drives home remote collaboration. There are so many tools in this space now, but Gitlab really practices what they preach as they are a remote first company. As such, they have thought through what challenges remote and on-prem teams face that are the same, but have made a huge effort to deliver a product that makes sure regardless of locale you're able to work together and collaborate effectively. At the end of the day, that's the important part. From a user experience perspective, Gitlab really nails this 100%.
Gitlab actually reduces the need for quite a bit of tooling. First and foremost, Gitlab as a version control system allows teams to use it as opposed to the multitude of other vcs systems out there. Gitlab has also eliminated the need for having a separate artifact storage (at least for our needs). Finally, gitlab has made issue tracking a breeze which has eliminated the need for Jira (at least within our use case). Jenkins as well -- using Gitlab as our pipeline solution really gets rid of complexity, plugin reliability, and unnecessary configuration outside the code base.
In some ways, as mentioned before, the web interface can be a little different to get used to. The gitlab documentation is also a little lacking compared to documentation of other tools in the same class.
September 22, 2020

Gitlab. Perfect for CI

Marco Carnevali | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We use Gitlab for every code project we have such as the website, APIs and mobile applications. It offers a free plan that has everything you need. We use Gitlab, especially for it's CI (continuous integration) feature that let us automate team working and deploying frameworks on dev and productions channels
  • Continuous integration
  • Git
  • Automations
  • Artifacts
Gitlab it's needed if you are developing software, and you want to enhance your development with integrations and automation.
  • Faster work
Gitlab is far better for its continuous integration. It gives you pre-made scripts to build and send an artifact to you or your team.
We haven't use any security features provided by gitlab
We use continuous integration to share artifacts and developing status across all our channels including slack. It helps automate the QA process and get things done quicker.
I've never used Gitlab support.
Bitbucket, GitHub, Microsoft 365 (formerly Office 365)
Yes we use gitlab to store more than 10 different code projects. Thanks to CI we enabled automations to connect Gitlab to third party services like Slack and really helped team collaborating.
We use gitlab issue and Pull requests to assign bug or features request to developers on our team and to merge code from different environments
We replaced bitbucket just because gitlab let us have more and better automations using CIs
They represent the core business. We store the website, mobile applications and API of all our products
Supporting gitlab it's really easy you just need to know how to use any Git service and dev-ops softwares
  • Automations
  • Artifacts
  • Store code
  • Integrating gitlab with third party services
  • for testing the backend in an automated way
We haven't found a service as good as gitlab on the CIs level
It replaced bitbucket for dev-ops. We replaced it because gitlab is far better on the CI department and it help us automating and deploying artifacts in a quicker and easier way then bitbucket
  • Product Features
  • Product Usability
  • Product Reputation
  • Prior Experience with the Product
We decided to use Gitlab for price + automations and CIs features the gitlab provides
in the process I would evaluate "Gitlab" just because it now supports CIs
During setup process I couldn't implement a edge feature of CI and they helped me indicating what tutorial to follow
  • Continuos integration
  • Managing projects
  • Artifacts
I think gitlab is really easy to use but they still have way to improve the UX of their interface
Kevin Ritchey | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Gitlab across our entire business, from documentation to code versioning to CI/CD and IaaS. We've used other documentation tools such as Confluence by Atlassian but we keep coming back to Markdown in Gitlab because of the simplicity, exportability, portability, better versioning, better integration - such as with Readthedocs. Our helpdesk team finds Gitlab easy to use. We also use Gitlab for our development teams and operations teams.
  • Markdown.
  • CI/CD integration.
  • User and group management.
  • Branding.
  • Standard Gitlab implementation.
  • Themes.
  • Need to reconfigure too often.
  • Use the same Markdown engine everywhere.
We would whole-heartedly recommend Gitlab for code versioning with teams across different organizations as the management of users and groups is so easy. CI/CD is built-in and batteries included and because the implementation of Gitlab is standard it is easier to use than Bitbucket. If your organization is already in the Cloud Gitlab is one of the easiest solutions to roll out on AWS, DigitalOcean, GCI, Azure, Linode, etc. Even the management of Gitlab itself can be versioned and deployed using CI/CD tools such as Jenkins.
  • Better documentation.
  • Better bug fixes.
  • Better team coordination.
  • Better productivity from our operations and development teams.
The web console management is superior and I would have given Gitlab a 10, but sometimes it is hard to find documentation about a configuration setting in the gitlab.rb configuration file. As we move everything to code that means moving our CVS tools to code as well - and Gitlab to code. The usability of Gitlab from the end user's perspective is superior and the usability from the operations team is very good and getting better but there could be a little improvement in the gitlab.rb config file layout and documentation.
The online documentation is best in breed and sets the example for all other platforms. We find it so useful that we have never once had to reach out to the Gitlab support team for assistance. In fact, because the chef recipe is so well written we have found that most issues are resolved with 'gitlab-ctl reconfigure'.
Gitlab surpasses Bitbucket in all areas except of course the very tight integration Bitbucket has with JIRA and Confluence. Almost everyone uses JIRA at some level or time so Bitbucket has a more natural and tight integration feel. However, there is good JIRA integration with Gitlab and we have found that we're not sacrificing anything to afford ourselves a better experience in every other area when choosing Gitlab over Bitbucket.

Gitlab is as good as GitHub in every area that we use version control. It excels in that we keep everything in-house and tightly monitored. We do not open our Gitlab instances to anonymous users and our public repositories are public only to our teams.
Return to navigation