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

Apache Subversion vs Git comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 14, 2024

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 May 2026, in the Version Control category, the mindshare of Apache Subversion is 4.2%, up from 1.2% compared to the previous year. The mindshare of Git is 12.6%, up from 8.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Version Control Mindshare Distribution
ProductMindshare (%)
Git12.6%
Apache Subversion4.2%
Other83.2%
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.
Dimitris Iracleous - PeerSpot reviewer
Lead Technical Instructor at Code.Hub
A powerful and mature solution that helps to collaborate and eliminate issues with code
Some challenges arise when Git is not used correctly, particularly in managing branches. It's easy to get lost, but these challenges can be overcome with proper management. A common advice is maintaining the repository and ensuring developers are in sync with the production branch. Branches should be promptly merged into development to avoid getting lost in many branches.

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."
"Apache Subversion is a scalable solution."
"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."
"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."
"The most valuable feature of Git is its ability to track updates, such as firmware documentation, and many people can make changes to code without problems while it is able to solve conflicts very easily."
"The product is easy to use."
"Git offers the ability to roll back to the previous version. You can also track all the small changes that you do."
"The scalability of the solution is good."
"The setup process is pretty simple."
"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."
"Version control is beneficial as it allows me to keep track of all the modifications I have made to the applications."
"My advice to others is Git is the industry standard for source code versioning and my recommendation for them is to learn it and use it."
 

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."
"It's easy, cost effective but not a enterprise tool therefore the community has to work with that direction."
"The most valuable feature is CLI."
"Its handling of complex merging needs work."
"Apache Subversion should be easier to use."
"There is nothing that could be improved at this time."
"More security is always welcome in my opinion."
"There is room for improvement in the pricing model of Git."
"Synchronization could be better. Sometimes when you create a branch and merge it into another branch, I think it's a bit complex for no reason. The initial setup is also tricky when you do it for the first time."
"If another person raises a pull request under the same ID assigned to the previous person, and both parties modify the tool, their changes will be grouped together in the same request until it is closed, which is an issue."
"We would like to see tutorials added to the product, for new users to follow so that they can optimize their use of the solution."
"I would like to see an improvement in the way the product owner can review changes."
"New developers sometimes find it difficult to call a review or create a request."
 

Pricing and Cost Advice

"The tool's price is good."
"I rate the tool's pricing a five out of ten."
"The tool is free."
"As a student, I didn't have to pay for the license."
"Git is an open-source software."
"This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges."
"The tool is an open-source product."
"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."
"There are some extra costs to Git, but it depends on your use case."
report
Use our free recommendation engine to learn which Version Control solutions are best for your needs.
893,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
16%
Financial Services Firm
11%
Marketing Services Firm
11%
Healthcare Company
5%
 

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.
 

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: April 2026.
893,164 professionals have used our research since 2012.