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-3 of 3)
Companies can't remove reviews or game the system. Here's why
December 21, 2021

GitLab: Future of DevOps

ANurag Tamrakar | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
GitLab is not just a source code repository hosting platform. It's a DevOps platform bagged with source code repository hosting, continuous integration, continuous delivery, artifact management, package management, Container registries, SAST, issue tracking and management, Source code vulnerability scanning, and much more. Very good role-based access control + user and group management. Group-based Isolation is also very good. Even If you're giant incorporation can easily manage multiple organizations within one instance of GitLab.
  • Source code repository hosting.
  • Continuous Integration and Continuous Deployment.
  • Package, Artifact, Container Image hosting.
  • Source code scanning.
  • Issue management and service desk.
  • There are two offerings, Self-managed and SaaS. The cost of both types of offers is the same which I don't like, the cost of self-managed GitLab should be less.
  • There are some resource limitations SaaS version if compared with self managed.
  • Licensing of self-managed shouldn't be per user it should be a fixed amount per instance.
  • There should be a feature of webhook proxy. This will feature addition will enable GitLab to send webhooks to resources hosted in a private network.
It's not just a source code repository hosting platform. When we started using GitLab it reduced our burden of managing some tools like CICD, Artifactory as It's a DevOps platform bagged with source code repository hosting, continuous integration, continuous delivery, artifact management, package management, container register, SAST, issue tracking, and management, Source code vulnerability scanning and much more. I thought a lot about the demerits of GitLab but there isn't any disadvantage of using GitLab it's better than all means if compared with GitHub or BitBucket. I strongly recommend using GitLab. It's super valuable.
  • It made development easier and reduced the release cycles as all the development operations are being executed in one single platform.
  • As it came with in-built CI/CD, Artifact management, Package, and Container registry. we've stopped maintaining all of them separately which resulted in increased productivity of our team.
  • As we're using the SaaS version of GitLab all the automation which are backed by webhooks has stopped working as GitLab doesn't support sending webhooks to resources that are hosted in private networks.
  • We're saving dollars and our effort of infrastructure and server maintenance by using the SaaS version of GitLab.
GitLab is rich in features if compared with GitHub or Bitbucket. GitHub is very popular and now it supports CI/CD as well which is known as GitHub actions but it's not mature as GitLab CI is. When we decided to use GitLab, Gitlab-CI was one of the strong reasons to make a decision. We're a big branched corporate with multiple organizations. Some organization needs to host source code repositories in their own infrastructure. GitHub doesn't offer a Self-managed instance it's only SaaS-based but GitLab does offer a self-managed instance.
Yes, we're using paid plans of Gitlab but we're not using security features of GitLab as we're already using some other security tools such as Checkmarx, Blackduck, and SonarQube to identify security vulnerabilities and quality of code.
By using GitLab CI we are linting our source code and deploying it on dev and test servers. GitLab pipeline is triggered on Every commit if it's configured for the branch in which a commit is made. All the collaborators receive an email from GitLab for pipeline failure if a stage is failed. Earlier we were using a separate CI tool to lint and deploy the code and it was an annoying task for us to notify all if code has validation, stylistic or programmatic errors.
JFrog Artifactory, SonarQube, Checkmarx, Bitbucket, Terraform, by HashiCorp, Microsoft Teams, Microsoft Visual Studio Code, GitHub, Jira Software, Red Hat OpenShift, Red Hat Enterprise Linux (RHEL), AWS Certificate Manager, Amazon Route 53, Amazon CloudFront, Cloudflare, Jenkins, 1Password, greytHR, Kibana, Elasticsearch, Amazon Elastic Kubernetes Service (EKS), Sumo Logic, Dynatrace, Docker, Kubernetes, PagerDuty, CentOS Linux, AWS Lambda, AWS CodePipeline, Grafana
Our Engineering teams use GitLab to manage and host source code repositories of their products. Also, they use to set up CI and CD for their projects and deploy container images, packages, and artifacts in Gitlab.
  • Hosting Source code repositories.
  • Storing artifacts, container images and packages.
  • Setting up CI/CD pipelines.
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.
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
Return to navigation