Git vs. GitLab

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Git
Score 10.0 out of 10
N/A
N/AN/A
GitLab
Score 8.7 out of 10
N/A
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…
$0
per month per user
Pricing
GitGitLab
Editions & Modules
No answers on this topic
GitLab Essential
$0
per month per user
GitLab Premium
$29
per month per user
GitLab Ultimate
$99
per month per user
Offerings
Pricing Offerings
GitGitLab
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
GitGitLab
Considered Both Products
Git
Chose Git
We migrated from svn to Git and the transition was smooth. We have tools that migrate the complete history along with the authors of the various files and the history from svn to Git. The migration was seamless and easy. We can see complete history of check-in as if we were …
Chose Git
We were using the TortoiseSVN previously and it was super slow when we created a new branch or switched between branches. Git makes our life easy. :)
Chose Git
Git is far superior at merging than SVN and I think every other VCS from what I've heard. It's also by far the most common so using it is a no brainer. Since it's written by the one true king Linus himself there can be no question to its design and architecture.
Chose Git
The only other VCS tool I've used in production is SVN. In my option Git is a better option for several reasons. Reason one is simplicity, actions like reviewing changes, committing or stashing changes, and managing multiple feature branches is much easier with Git. The second …
Chose Git
The two main alternatives to Git that I know about are Mercurial and Subversion. I've never used either one, but I know a bit about Subversion. From what I remember, Subversion requires a server. I don't anyone using any other source control other than Git, it seems to have …
Chose Git
Git is more advanced and easier to use. It has a very simple UI and a very efficient command-line tool. Git gives you flexibility and performance for the price, and has greatly increased the complexity of workflow. The overall performance is good. It caches information locally …
Chose Git
What I know is Perforce and CVS, such other repos tend to store deltas while Git stores the snapshots of the stuff as their commit ID's. This is what makes Git much much faster when you are developing on huge repos, since the checkouts are just instantaneous.
Chose Git
Gitlab provides similar features like Git. Git is more robust, secure and developer-friendly to work on.
Chose Git
There are not many surviving alternatives for Git (maybe SVN) which in itself is quite meaningful. Git is the best versioning system of all time for programming, period. The difference between a good mathematical tool and sending .zip-s around emailing lists or FTP drives is so …
Chose Git
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria.
GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way.
G…
Chose Git
It's easy to use and stable. These are the two strengths I see in Git. It does not need a lot of time to learn, but you still need to learn it. It has high stability. Bugs are not often to see in Git, and the community support is wonderful. With the help of GitHub, you can …
Chose Git
Compared to SVN, Git has a decentralized approach which increases collaboration in the team by enabling the local stored branches. There is no need to be connected to the repository(via an internet link) to work and commit code. Besides the fact that the performance of Git is …
Chose Git
I do not have much experience with other version control tools. Git is highly used everywhere and it is hard to find a development team that isn't using it. One thing I know is that with Git each developer has their own copy of a repository so they could technically work …
Chose Git
Git is the best Source Control Management Tool I've used. Every company, team, and project I've worked on professionally either used Git 100%, or was moving to Git, away from the alternatives like SVN. Git has all the features necessary, as well as a very large community of …
Chose Git
Git is by far the best version control system out there. It's open source, free, and fast. No other version control system I've ever used has had all three features.
Chose Git
Primarily we chose Mercurial, but our customers from abroad choose Git and recommended us to use it within a project that we are doing with them. Git for us is very easy way to contribute to these projects. But from the other side we see that more and more projects and …
Chose Git
For us, we use both Git and GitHub so they were a package. I suppose you could use Git with another VCS/hosting service to track changes if it fit well enough, but for us we just went with design out of the box. We pay for the GitHub private repository for the extra security.
Chose Git
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in …
Chose Git
N/A. No other products like Git were used.
Chose Git
Branching and merging are easy: Branching is a walk in the park. It feels like a natural part of the workflow. They are cheap (fast and consume very little space) so that you can branch whenever you want. This means you can sandbox your features and ideas till they are ready …
Chose Git
Git is pretty much the main choice today when choosing a source control system. There are still others out there like Subversion and Mercurial, however I have not evaluated these as they are older than Git and I tend to try to stay on the leading edge of what is in use for the …
Chose Git
Git is a distributed version control system. There is more flexibility to work with a bigger team. You can modify the same file and later merge all changes into a single file.
Chose Git
After using Subversion previously for a number of years, Git comes across as the new and improved source control approach. Git seems very suited to working with Agile:- branches can be created easily, allowing multiple developers to switch to them quickly, and having local …
Chose Git
While my experience is limited on Microsoft Team Foundation Server, my understanding is that it works only for windows development work. This leaves out developers of alternative languages. Since git allows any code to be placed in it (you could even use it to back up plain …
GitLab
Chose GitLab
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
Chose GitLab
For small projects or companies that do work on a few only code repositories selecting one of the git code hosting services like GitLab, GitHub, Bitbicket etc does not make a big difference.

But, if you are on a code development company that handles too many repositories and …
Chose GitLab
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
Chose GitLab
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
Chose GitLab
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
Chose GitLab
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Chose GitLab
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Chose GitLab
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.

GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
Chose GitLab
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Chose GitLab
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
Chose GitLab
I tried Github in the past, and it was really similar as GitLab. But we prefer use GitLab for the cicd part, easier to handle
Chose GitLab
i have more exoerence in GitLab rather than bitbucket . As personally , it is good for me to understand how things is going on. i have used personally and also in organisation . It is great for developer to see there 3 months ago code and also can come up with new solution to …
Chose GitLab
Because with Visual Studio code, it was very easy for us to install GitLab in it and have easy access through the terminal and due to GitLab, it was easy to implement codes regarding API and AWS services to make our software better. Gitlens and all features help to check the …
Chose GitLab
GitLab provides a far superior platform due to it's great integration and CI/CD focus. And while in the beginning the UI might look a bit overwhelming with use you will find it way more useful than it's competitors. The variables and settings also make way more sense and it's …
Chose GitLab
My feedback may not be important here because when I joined the company they already had GitLab and we still use it due to the ability to do CI/CD Integration, deployments, debugging, code owners approval, and Jira integration. So far we have not had any major blocker that has …
Chose GitLab
Github is more open-source first and enterprise-first second in their approach. The reverse is true for GitLab. Both are exceptional products and it highly depends on the specific needs of an org
Chose GitLab
Used Jenkins to connect with GitLab for building and deployment of microservices. GitLab helps in easy integration.
Chose GitLab
GitLab has a open-source community and great documentation that provides support resources and community contributions. AWS CodeCommit is used for integration with other AWS services in the AWS ecosystem and also have a low community and support compared to GitLab hence …
Chose GitLab
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
Chose GitLab
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
Chose GitLab
1. Easier to use and setup then any other product.
2. CI/CD is also easier in GitLab
Chose GitLab
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
Chose GitLab
GitLab is rich in features and access control if compared with GitHub also GitHub stands no where in CI/CD if compared with GitLab.
GitLab CI/CD is mature, robust and far better than GitHub actions in all means.
If I talk about quality of support and reponse time of GitLab it is …
Best Alternatives
GitGitLab
Small Businesses
GitHub
GitHub
Score 9.0 out of 10

No answers on this topic

Medium-sized Companies
GitHub
GitHub
Score 9.0 out of 10
Veracode
Veracode
Score 8.7 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.7 out of 10
Veracode
Veracode
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GitGitLab
Likelihood to Recommend
10.0
(0 ratings)
8.9
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
9.9
(0 ratings)
Usability
9.0
(0 ratings)
9.0
(0 ratings)
Support Rating
8.5
(0 ratings)
9.1
(0 ratings)
Implementation Rating
9.0
(0 ratings)
-
(0 ratings)
User Testimonials
GitGitLab
Likelihood to Recommend
Git is by far the best Source Control Management Tool I've used. I would recommend it to anyone, whether it's an individual working on their own project, a small start-up company, or a huge organization with thousands of developers. Maintaining code via source control is absolutely mandatory for all developers everywhere.
Read full review
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
Read full review
Pros
  • Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
  • Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
  • Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
Read full review
  • GitLab excels in managing code versions, allowing easy tracking of changes, branch management, and merging contributions.
  • It helps maintain code stability and reliability, saving time and effort in the development or research workflow.
  • Powerful code review features, enabling collaboration and feedback among team members.
  • Robust project management features, including issue tracking, kanban boards, and milestones.
Read full review
Cons
  • Some of the commands are a little obtuse if you're not using a Git Client
  • Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
  • It's hard to fault a tool that is so ubiquitous and hardly gets in your way.
Read full review
  • CI variables management is sometimes hard to use, for example, with File type variables. The scope of each variable is also hard to guess.
  • Access Token: there are too many types (Personal, Project, global..), and it is hard to identify the scope and where it comes from once created.
  • Runners: auto-scaled runners are for the moment hard to put in place, and monitoring is not easy.
Read full review
Likelihood to Renew
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Read full review
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
Read full review
Usability
Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
Read full review
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!
Read full review
Reliability and Availability
No answers on this topic
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
Read full review
Performance
No answers on this topic
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
Read full review
Support Rating
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Read full review
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
Read full review
Implementation Rating
It's easy to set up and get going.
Read full review
No answers on this topic
Alternatives Considered
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria. GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way. GIT have the facility to quickly fetch the complete repository on to your local system.
Read full review
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
Read full review
Scalability
No answers on this topic
I think is very well designed, and like any VCS it works as intended
Read full review
Return on Investment
  • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
  • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
  • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Read full review
  • GitLab cut down our spent on container, package and infrastructure registry
  • Best thing is we can now have everything in single platform which cost effective too
  • Quality of support is really good and they do have emergency support team as well which is great
Read full review
ScreenShots

GitLab Screenshots

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