TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Contact about GitLab

Please fill out the form below to get in touch.

GitLab

Connect with GitLab

What are you interested in?

Already have an account?

You hereby consent to have TrustRadius share the information supplied on this form with GitLab so that GitLab and TrustRadius may contact you in regard to the information requested.

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Subversion

    Score9.9 out of 10
    N/AApache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.N/A

    Git

    Score10 out of 10
    N/AN/AN/A

    GitLab

    Score8.9 out of 10
    N/AGitLab is an intelligent orchestration platform for DevSecOps, where software teams enable AI at every stage of the software lifecycle to ship faster. The platform enables teams to automate repetitive tasks across planning, building, securing, testing, deploying, and maintaining software.

    $0

    per month per user

    Pricing
    Apache SubversionGitGitLab
    Editions & Modules
    No answers on this topic
    No answers on this topic
    GitLab Free (self-managed)
    $0
    GitLab Free
    $0
    GitLab Premium
    $29
    per month per user
    GitLab Premium (self-managed)
    $29
    per month per user
    GitLab Ultimate
    Contact Sales
    GitLab Ultimate (self-managed)
    Contact Sales
    Offerings
    Pricing Offerings
    Apache SubversionGitGitLab
    Free Trial
    NoNoYes
    Free/Freemium Version
    NoNoYes
    Premium Consulting/Integration Services
    NoNoYes
    Entry-level Setup FeeNo setup feeNo setup feeOptional
    Additional Details——GitLab Credits enable flexible, consumption-based access to agentic AI capabilities in the GitLab platform, allowing you to scale AI adoption at your own pace while maintaining cost predictability. Powered by Duo Agent Platform, GitLab’s agentic AI capabilities help software teams to collaborate at AI speed, without compromising quality and enterprise security. If usage exceeds monthly allocations and overage terms are accepted, automated on-demand billing activates without service interruption, so your developers never lose access to AI capabilities they need. Real-time dashboards provide transparency into AI consumption patterns. Software teams can see usage across users, projects, and groups with granular attribution for cost allocation. Automated threshold alerts facilitate proactive planning. Advanced analytics deliver trending, forecasting, and FinOps integration.
    More Pricing Information
    Community Pulse
    Apache SubversionGitGitLab
    Considered Multiple Products
    Apache
    Chose Apache Subversion
    Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
    Incentivized
    Chose Apache Subversion
    We used Visual SourceSafe before SVN many years ago and we chose SVN at that time mainly because it allowed us to do collaborative work on the same source code. It also had improved conflict resolution when doing code merges, blaming changes etc, which improved the speed of …
    Incentivized
    Chose Apache Subversion
    Git is probably the biggest open source rival to Subversion. It's designed for distributed development, an environment I'm not very familiar with. I've only got some experience with it, and only as a user, and even that is limited. I had some trouble wrapping my mind around the …
    Incentivized
    Chose Apache Subversion
    Git is a newer version control system compared to that of svn. I think that svn is more stable, easy to learn/use, and not-so-complex as Git. Also, svn has very good client applications which provide extremely user-friendly user interfaces. Apache Subversion is also open source …
    Incentivized
    Chose Apache Subversion
    Git is better than Subversion in every aspect except that is not free . But since our company has bought Git licenses and I would not go back to using Subversion .
    Open Source
    Chose Git
    Gitlab provides similar features like Git. Git is more robust, secure and developer-friendly to work on.
    Incentivized
    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 …
    Incentivized
    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. :)
    Incentivized
    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 …
    Incentivized
    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 …
    Incentivized
    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…
    Incentivized
    Chose Git
    After using Subversion previously for years, Git comes across as the new and improved source control approach.
    Incentivized
    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 …
    Incentivized
    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 …
    Incentivized
    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 …
    Incentivized
    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.
    Incentivized
    Chose Git
    N/A. No other products like Git were used.
    Incentivized
    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.
    Incentivized
    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 …
    Incentivized
    Chose Git
    Git is my favorite among all of the version control systems out there. It follows the Linux software philosophy of being built by many loosely coupled and small components that do one thing well. It's incredibly open, and its adoption in the open source community seems to be …
    Incentivized
    GitLab
    Chose GitLab
    Git has a Distributed Model. SVN has a Centralized Model. In git every user has their own copy of code on their local like their own branch. In SVN there is central repository has working copy that also make changes and committed in central repository
    Incentivized
    Chose GitLab
    GitLab stands up great to other Git hosting services. GitLab CI blows GitLab past it's competitors to take a Git server and make it a complete application management platform. Versus GitHub, GitLab does not stand up for hosting open source projects as GitHub has a much larger …
    Incentivized
    Chose GitLab
    Above and beyond Perforce and subversion, close to github.com but a lot cheaper (CE edition)
    Incentivized
    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.
    Incentivized
    Chose GitLab
    GitLab is distributed version control system unlike Subversion (SVN) is a centralized version control system. Multiple developers can work on the same file simultaneously unlike Subversion (SVN) if a developer locked a file other developers can not change it. GitLab provides a …
    Incentivized
    Chose GitLab
    Earlier we used SVN as our SCM tool. SVN was a centralized version control system due to which developers had to connect to the server every time they needed to commit. It was causing trouble for developers considering the large Org size. Also, SVN does not have a robust CI …
    Incentivized
    Key User Insights
    Would buy again
    No answers on this topic
    100%
    Would buy again
    12 Answers
    97%
    Would buy again
    150 Answers
    Delivers good value for the price
    No answers on this topic
    100%
    Delivers good value for the price
    11 Answers
    99%
    Delivers good value for the price
    135 Answers
    Happy with the feature set
    No answers on this topic
    100%
    Happy with the feature set
    12 Answers
    99%
    Happy with the feature set
    152 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    9 Answers
    100%
    Lived up to sales and marketing promises
    92 Answers
    Implementation went as expected
    No answers on this topic
    100%
    Implementation went as expected
    9 Answers
    97%
    Implementation went as expected
    120 Answers
    Best Alternatives
    Apache SubversionGitGitLab
    Small Businesses
    GitHub
    Score9.2 out of 10
    GitHub
    Score9.2 out of 10
    GitGuardian
    Score9 out of 10
    Medium-sized Companies
    Git
    Score10 out of 10
    GitHub
    Score9.2 out of 10
    No answers on this topic
    Enterprises
    Perforce P4
    Score7.6 out of 10
    Perforce P4
    Score7.6 out of 10
    No answers on this topic
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Apache SubversionGitGitLab
    Likelihood to Recommend
    6.6
    (10 ratings)
    10.0
    (36 ratings)
    8.6
    (168 ratings)
    Likelihood to Renew
    3.1
    (2 ratings)
    10.0
    (1 ratings)
    9.0
    (6 ratings)
    Usability
    -
    (0 ratings)
    9.0
    (1 ratings)
    8.8
    (20 ratings)
    Performance
    -
    (0 ratings)
    -
    (0 ratings)
    9.0
    (1 ratings)
    Support Rating
    -
    (0 ratings)
    8.5
    (11 ratings)
    10.0
    (12 ratings)
    Implementation Rating
    -
    (0 ratings)
    9.0
    (1 ratings)
    -
    (0 ratings)
    Product Scalability
    -
    (0 ratings)
    -
    (0 ratings)
    10.0
    (1 ratings)
    User Testimonials
    Apache SubversionGitGitLab
    Likelihood to Recommend
    Apache
    It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
    Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
    Incentivized
    Read full review
    Open Source
    GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
    Incentivized
    Read full review
    GitLab
    In general it's a good product with a huge number of features. It can do CI/CD checks, deployment, repo hosting, integrations etc. A lot of it can be managed from just the UI but also has an ok API. It does tend to release new features semi-often too which is nice. It can have a steep learning curve for certain features so not a starter-friendly vendor, but great for most businesses.
    Incentivized
    Read full review
    Pros
    Apache
    • Revision control done properly - you have end to end visibility of all changes in the project.
    • Conflict resolution - visually highlighting the differences helps to track down the problem.
    • Being open source and very popular.
    • We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years.
    • Rollbacks are made simple and easy to use.
    Incentivized
    Read full review
    Open Source
    • Ability to create branches off current releases to modify code that can be tested in a separate environment.
    • Each developer had their own local copy of branches so it minimizes mistakes being made.
    • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
    • Conflicts are displayed nicely so that developers can resolve with ease.
    Incentivized
    Read full review
    GitLab
    • 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.
    Incentivized
    Read full review
    Cons
    Apache
    • Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
    • Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
    • Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.
    Incentivized
    Read full review
    Open Source
    • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
    • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
    • Many different GUIs, many people (including myself) opt to just use the command-line.
    Incentivized
    Read full review
    GitLab
    • 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.
    Incentivized
    Read full review
    Likelihood to Renew
    Apache
    While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
    Read full review
    Open Source
    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.
    Incentivized
    Read full review
    GitLab
    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
    Incentivized
    Read full review
    Usability
    Apache
    No answers on this topic
    Open Source
    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.
    Incentivized
    Read full review
    GitLab
    - As a combination of features and products, GitLab is a really great tool for developers. - Also, it comes with both light and quick changes in a web browser version, as well as pro work in VS Code mode. However, in certain areas, such as large-scale issues/incidents, management can be improved.
    Incentivized
    Read full review
    Reliability and Availability
    Apache
    No answers on this topic
    Open Source
    No answers on this topic
    GitLab
    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
    Incentivized
    Read full review
    Performance
    Apache
    No answers on this topic
    Open Source
    No answers on this topic
    GitLab
    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
    Incentivized
    Read full review
    Support Rating
    Apache
    No answers on this topic
    Open Source
    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.
    Incentivized
    Read full review
    GitLab
    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
    Incentivized
    Read full review
    Implementation Rating
    Apache
    No answers on this topic
    Open Source
    It's easy to set up and get going.
    Incentivized
    Read full review
    GitLab
    No answers on this topic
    Alternatives Considered
    Apache
    Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
    Incentivized
    Read full review
    Open Source
    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 a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
    It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
    Incentivized
    Read full review
    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" 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.
    Incentivized
    Read full review
    Scalability
    Apache
    No answers on this topic
    Open Source
    No answers on this topic
    GitLab
    I think is very well designed, and like any VCS it works as intended
    Incentivized
    Read full review
    Return on Investment
    Apache
    • Subversion helps us feel secure in maintaining access to all of our product code, both current and historical.
    • Being free and open source makes it an even better "investment".
    Incentivized
    Read full review
    Open Source
    • 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.
    Incentivized
    Read full review
    GitLab
    • 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
    Incentivized
    Read full review
    ScreenShots

    GitLab Screenshots

    Screenshot of What is Intelligent Orchestration for DevSecOps?Screenshot of an overview of GitLab Duo Agent PlatformScreenshot of a new agent creation screen