No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Subversion vs Git comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 3, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Apache Subversion
Ranking in Version Control
10th
Average Rating
7.0
Reviews Sentiment
5.5
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Git
Ranking in Version Control
4th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
38
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Version Control category, the mindshare of Apache Subversion is 4.6%, up from 1.4% compared to the previous year. The mindshare of Git is 13.4%, up from 8.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Version Control Mindshare Distribution
ProductMindshare (%)
Git13.4%
Apache Subversion4.6%
Other82.0%
Version Control
 

Featured Reviews

Vijay Londhe - PeerSpot reviewer
Assistant Programmer at Mahadis
Enables centralized code management but lacks modern CI/CD integrations
There is room for improvement in Apache Subversion, especially when comparing it with other version control systems such as GitHub or GitLab, where many improvements could be made. Improvements I would like to see in Apache Subversion include configurations, customizations, and functionalities such as those provided by GitHub Actions for immediate pipeline triggers, as well as the version controlling and CI/CD platform offered by GitLab. In future updates of Apache Subversion, I would like to see CI/CD integrations as well as build and deployment servers. The lack of latest features includes basic requirements such as pull requests, CI/CD platform integration, and artifact storage such as GitHub packages, which it does not offer.
Hari Kathireshan - PeerSpot reviewer
Sr PHP Developer at GE
An easy-to-use solution that can be used for configuration management
We use Git for configuration management Git is an easy-to-use solution that can be used for parallel working. Git's user interface could be improved. I have been using Git for almost eight years. Git is a stable solution. Git is a scalable solution. Around 2,000 users use the solution in our…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The ease of installation, configuration, and user friendliness."
"I find the strong point of Apache Subversion to be that it is a centralized version control system, allowing us to keep our code repositories at a central server."
"We have developed automation to speed up common repetitive processes."
"As an open source solution it's very effective, will be very useful for individual and for small teams."
"Apache Subversion is a scalable solution."
"The most valuable feature is having access to the local country repository even if we have problems with distance access."
"The setup process is pretty simple."
"Git is easy to use."
"Code versioning, for example, we work in the branch and want to come back to this branch another time.Git is a very useful tool, helpful to collaborate with other members in the group to finish more rapidly our work."
"I like that it's easy to use and because it's accessible from a terminal or a graphical user interface if needed. I also like that we can pass comments from Linux if required."
"We use the tool to store codes."
"The product protects our data."
"The most valuable feature of Git is its reliability and user popularity."
 

Cons

"The lack of latest features includes basic requirements such as pull requests, CI/CD platform integration, and artifact storage such as GitHub packages, which it does not offer."
"Apache Subversion should be easier to use."
"The most valuable feature is CLI."
"It's easy, cost effective but not a enterprise tool therefore the community has to work with that direction."
"Its handling of complex merging needs work."
"The tool's user interface is terrible. It needs to be more user-friendly."
"The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter."
"About the configuration it is a little bit difficult, it can be improved."
"The solution could improve by having more customization."
"The UI can be more user-friendly."
"Git could improve the merge conflicts."
"The main problem for me is the frequent upgrades in the solution because every other upgrade is a minefield. When you do the upgrade, there is always something that doesn't work."
"If other people are included in their project, you're going to have to make merge requests to merge the code you made, and the code your colleagues have made. So it's a little bit complicated."
 

Pricing and Cost Advice

"The tool's price is good."
"There are some extra costs to Git, but it depends on your use case."
"This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges."
"I am not required to pay due to the small number of users we have. We have a small user base, and we are not using the enterprise version."
"Git is an open-source software."
"The tool is an open-source product."
"Git is completely free."
"The tool is free."
"The platform is less expensive."
report
Use our free recommendation engine to learn which Version Control solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
17%
Financial Services Firm
12%
Marketing Services Firm
10%
Construction Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Midsize Enterprise1
Large Enterprise6
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise9
Large Enterprise21
 

Questions from the Community

What is your experience regarding pricing and costs for Apache Subversion?
I am satisfied with the pricing and licensing cost of Apache Subversion; it is very low compared to other products.
What needs improvement with Apache Subversion?
There is room for improvement in Apache Subversion, especially when comparing it with other version control systems such as GitHub or GitLab, where many improvements could be made. Improvements I w...
What is your primary use case for Apache Subversion?
The typical use case for Apache Subversion is to store the application code repositories, which is how we use this product in our company. For multiple projects, we are using Apache Subversion, and...
What needs improvement with Git?
There is nothing that could be improved at this time.
What is your primary use case for Git?
I use Git to store our code and maintain different versions, and for some projects, we use CI/CD as part of GitHub.
What advice do you have for others considering Git?
I would recommend Git to other people. I'd rate it nine out of ten.
 

Comparisons

 

Overview

 

Sample Customers

IBM, General Electric, Amazon, HP, Facebook, Bank of America, American Express, AT&T, Nike, PayPal, Wells Fargo, Best Buy, Tesla Motors, Citi, The Home Depot
Google, Facebook, Microsoft, Twitter, LinkedIn, Netflix, PostgreSQL, Android, Rails, QT, Gnome, Eclipse
Find out what your peers are saying about Apache Subversion vs. Git and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.