Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Subversion
Score 9.6 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
Bugzilla
Score 8.5 out of 10
N/A
N/AN/A
GitLab
Score 8.7 out of 10
N/A
GitLab 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 SubversionBugzillaGitLab
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 SubversionBugzillaGitLab
Free Trial
NoNoYes
Free/Freemium Version
NoNoYes
Premium Consulting/Integration Services
NoNoYes
Entry-level Setup FeeNo setup feeNo setup feeOptional
Additional DetailsGitLab 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 SubversionBugzillaGitLab
Considered Multiple Products
Apache Subversion

No answer on this topic

Bugzilla

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 …
Best Alternatives
Apache SubversionBugzillaGitLab
Small Businesses
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.7 out of 10
GitGuardian
GitGuardian
Score 9.0 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.7 out of 10
Veracode
Veracode
Score 8.8 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.2 out of 10
GitLab
GitLab
Score 8.7 out of 10
Veracode
Veracode
Score 8.8 out of 10
All AlternativesView all alternativesView all alternativesView all alternatives
User Ratings
Apache SubversionBugzillaGitLab
Likelihood to Recommend
6.6
(10 ratings)
7.7
(18 ratings)
8.3
(152 ratings)
Likelihood to Renew
3.1
(2 ratings)
6.0
(10 ratings)
9.0
(5 ratings)
Usability
-
(0 ratings)
9.0
(3 ratings)
10.0
(6 ratings)
Availability
-
(0 ratings)
9.0
(3 ratings)
-
(0 ratings)
Performance
-
(0 ratings)
8.0
(2 ratings)
9.0
(1 ratings)
Support Rating
-
(0 ratings)
5.1
(3 ratings)
10.0
(12 ratings)
In-Person Training
-
(0 ratings)
9.0
(1 ratings)
-
(0 ratings)
Implementation Rating
-
(0 ratings)
8.0
(2 ratings)
-
(0 ratings)
Configurability
-
(0 ratings)
9.0
(1 ratings)
-
(0 ratings)
Ease of integration
-
(0 ratings)
9.0
(1 ratings)
-
(0 ratings)
Product Scalability
-
(0 ratings)
9.0
(1 ratings)
10.0
(1 ratings)
Vendor post-sale
-
(0 ratings)
7.0
(1 ratings)
-
(0 ratings)
Vendor pre-sale
-
(0 ratings)
8.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache SubversionBugzillaGitLab
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
Open Source
Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!
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
Open Source
  • Open source! No license fee involved, no limit to the number of licenses.
  • Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
  • Includes all the core features/fields that are needed to log a software bug/issue.
  • Multiple attachments are possible, supports various formats.
  • Good for reporting. Filtering mechanism lets you query bugs by various parameters.
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
Open Source
  • Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
  • Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.
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
Open Source
For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.
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
Read full review
Usability
Apache
No answers on this topic
Open Source
This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.
Read full review
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
Reliability and Availability
Apache
No answers on this topic
Open Source
I used it.
Read full review
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
Read full review
Performance
Apache
No answers on this topic
Open Source
I like this rating.
Read full review
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
Read full review
Support Rating
Apache
No answers on this topic
Open Source
Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need
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
Read full review
In-Person Training
Apache
No answers on this topic
Open Source
I know it.
Read full review
GitLab
No answers on this topic
Implementation Rating
Apache
No answers on this topic
Open Source
Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.
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.
Read full review
Open Source
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.
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
Scalability
Apache
No answers on this topic
Open Source
I used it
Read full review
GitLab
I think is very well designed, and like any VCS it works as intended
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
Open Source
  • It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
  • We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
  • Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.
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 What is Intelligent Orchestration for DevSecOps?Screenshot of an overview of GitLab Duo Agent PlatformScreenshot of a new agent creation screen