Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Subversion
Score 8.0 out of 10
N/A
Apache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.N/A
GitLab
Score 8.6 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
Apache SubversionGitLab
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
Apache SubversionGitLab
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Apache SubversionGitLab
Considered Both Products
Apache Subversion

No answer on this topic

GitLab
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 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 …
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
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 …
Features
Apache SubversionGitLab
Version Control Software Features
Comparison of Version Control Software Features features of Product A and Product B
Apache Subversion
-
Ratings
GitLab
8.6
26 Ratings
8% above category average
Branching and Merging00 Ratings8.625 Ratings
Version History00 Ratings9.026 Ratings
Version Control Collaboration Tools00 Ratings8.224 Ratings
Pull Requests00 Ratings8.925 Ratings
Code Review Tools00 Ratings8.525 Ratings
Project Access Control00 Ratings9.026 Ratings
Automated Testing Integration00 Ratings7.924 Ratings
Issue Tracking Integration00 Ratings8.125 Ratings
Branch Protection00 Ratings9.223 Ratings
Best Alternatives
Apache SubversionGitLab
Small Businesses
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Enterprises
Perforce Helix Core
Perforce Helix Core
Score 6.8 out of 10
Perforce Helix Core
Perforce Helix Core
Score 6.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache SubversionGitLab
Likelihood to Recommend
6.6
(10 ratings)
8.6
(144 ratings)
Likelihood to Renew
3.1
(2 ratings)
9.9
(4 ratings)
Usability
-
(0 ratings)
9.0
(5 ratings)
Support Rating
-
(0 ratings)
9.1
(11 ratings)
User Testimonials
Apache SubversionGitLab
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.
Read full review
GitLab
GitLab is good if you work a lot with code and do complex repository actions. It gives you a very good overview of what were the states of your branches and the files in them at different stages in time. It's also way easier and more efficient to write pipelines for CI\CD. It's easier to read and it's easier to write them. It takes fewer clicks to achieve the same things with GitLab than it does for competitor products.
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.
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.
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.
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.
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
GitLab
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.
Read full review
Usability
Apache
No answers on this topic
GitLab
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
Support Rating
Apache
No answers on this topic
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
Read full review
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.
Read full review
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 out-of-the-box templates for Gitlab, we have never discovered a lack of feature parity.
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".
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
Read full review
ScreenShots

GitLab Screenshots

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