We use this solution to host our software, and where we need to develop new features and new functionality, we create new branch from our existing software, work on our branch, develop it, test it, validate it, and then merge it with the master or main software.
Scientist - Instrument II at a manufacturing company with 10,001+ employees
An excellent open source, software hosting solution that provides strong version control functionality and a user-friendly interface
Pros and Cons
- "The best thing about this solution is that it can be learned very quickly, and used very easily."
- "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."
What is our primary use case?
What is most valuable?
The best thing about this solution is that it can be learned very quickly, and used very easily.
What needs improvement?
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.
For how long have I used the solution?
We have been using this solution for more than three years.
Buyer's Guide
Git
January 2026
Learn what your peers think about Git. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,665 professionals have used our research since 2012.
What do I think about the stability of the solution?
We have found this to be a very stable solution.
What do I think about the scalability of the solution?
This solution is easily scalable, and can comfortably handle multiple users accessing the system at the same time.
How are customer service and support?
This solution provides a lot of support online, that gives quick access to fixes for the majority of issues.
How was the initial setup?
The initial setup of this solution is very easy and straightforward. New users download the interface, using a simple command on the command line, then begin using it.
What's my experience with pricing, setup cost, and licensing?
This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges.
What other advice do I have?
We would recommend new users to start with the areas of this solution that have a user interface. This has a step-by step guide available that will allow them to get used to the product.
I would rate this solution a 10 out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Laboratory Instructor for the course INF2010 Data Structures and Algorithms at a university with 1,001-5,000 employees
Helps to distribute development, do version control and manage source code
Pros and Cons
- "The tool's most valuable feature is branch workflows."
- "I believe there is room for improvement in preventing work loss due to conflicts or overwriting. Another area for improvement could be implementing features for automated code verification within Git."
What is our primary use case?
I use Git for version control. It helps us to distribute development and manage source code.
What is most valuable?
The tool's most valuable feature is branch workflows.
What needs improvement?
I believe there is room for improvement in preventing work loss due to conflicts or overwriting. Another area for improvement could be implementing features for automated code verification within Git.
What do I think about the scalability of the solution?
I rate the solution's scalability a seven out of ten. My company has eight developers using it.
How are customer service and support?
I haven't contacted the tool's technical support.
How was the initial setup?
I would rate my experience with the initial setup of Git as a seven or six out of ten. It has clear documentation and takes one or two hours to deploy. The deployment process involved installing Git, creating a project in Git, and configuring it with administrative privileges. Then, the steps included preparation, conversion, synchronization, and migration. This set up the repository, allowed for safe changes, and enabled inspection of the repository.
What's my experience with pricing, setup cost, and licensing?
I rate the tool's pricing a five out of ten.
What other advice do I have?
I can provide support and control over the development teams, such as developing scripts for managing code or administering Git repositories for all members. However, we may need an extra week or two for additional training.
According to my opinion, every programmer should use Git.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Git
January 2026
Learn what your peers think about Git. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,665 professionals have used our research since 2012.
Senior ict specialist at a government with 201-500 employees
Easy-to-use product with good scalability features
Pros and Cons
- "Git is easy to use."
- "The platform could have a feature for monitoring data recovery similar to Azure."
What is most valuable?
Git is easy to use. With the help of a few online tutorials, a person can understand how it works.
What needs improvement?
The platform could have a feature for monitoring data recovery similar to Azure.
For how long have I used the solution?
We have been using Git for nine months.
What do I think about the stability of the solution?
It is a stable product.
What do I think about the scalability of the solution?
It is a scalable product.
How are customer service and support?
Git’s technical support services are satisfactory.
How was the initial setup?
Git’s initial setup has 60% complexity. In the beginning, it was not easy to set up for us. Although, with more experience, it has become more accessible. It takes a few days to complete. We have to make sure we have covered all the essential things.
What's my experience with pricing, setup cost, and licensing?
The platform is less expensive.
What other advice do I have?
I rate the product an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Data Archirect at a comms service provider with 1,001-5,000 employees
Great for storing software, development, and tracking versions
Pros and Cons
- "The implementation is easy."
- "The UI can be more user-friendly."
What is our primary use case?
We use Git for storing software, development, and tracking versions. We have plans to use it for ODI as well, mainly to unify software version tracking. Although ODI already has its own internal versioning control, we can also transfer it to Git.
What is most valuable?
The implementation is easy.
What needs improvement?
The UI can be more user-friendly.
For how long have I used the solution?
I have been using Git for around four years.
What do I think about the stability of the solution?
Git is stable.
What do I think about the scalability of the solution?
I believe Git is scalable.
What other advice do I have?
I give Git an eight out of ten.
We have a few hundred end users.
I recommend Git to others.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Professor at a educational organization with 201-500 employees
A simple and stable solution useful for tracking changes
Pros and Cons
- "Stability-wise, I rate the solution a ten out of ten...Since I am a very simple user of the tool, its scalability is good for me."
- "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."
What is our primary use case?
Git is used for downloading stuff and tracking purposes. It is very simple. In short, I use Git for tracking changes in the computer, which is very simple.
What is most valuable?
It's a tool for collaboration, and that's what we use it for in our company.
What needs improvement?
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. We have to spend days to correct it. Then, we stop all updates, and we do the updates in six months or a year. There is always a problem, especially if you do an update, since after that, some libraries don't work. We then spend a lot of time trying to fix it. Therefore, the frequent updates are really, really terrible. The aforementioned area can be improved.
For how long have I used the solution?
I have experience with Git. Also, I don't remember the version of the solution I am using.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a ten out of ten. I may not probably be the right person to evaluate the tool.
What do I think about the scalability of the solution?
Since I am a very simple user of the tool, its scalability is good for me.
In my company, two or three people use the solution.
It is not an extensively used tool in my company, so there are no plans to increase its usage.
How are customer service and support?
I don't need any technical support because one of my colleagues provides the technical support. He had done the setup of Git, and we just used it. If there is some problem with the new version, he will do the setup, and that's enough for me.
How was the initial setup?
I wasn't involved in the setup.
What other advice do I have?
I just tried to use the solution for what I needed.
I would definitely recommend the solution to those planning to use it.
Overall, I rate the solution a ten out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Former Employee of Orange Business Services as Head of Security Engineering at a comms service provider with 5,001-10,000 employees
Helps with software development and version control
Pros and Cons
- "Git offers the ability to roll back to the previous version. You can also track all the small changes that you do."
- "The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter."
What is our primary use case?
We use the product for software development and version control. It helps us to maintain a safe repository of our development.
What is most valuable?
Git offers the ability to roll back to the previous version. You can also track all the small changes that you do.
What needs improvement?
The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter.
For how long have I used the solution?
I have been working with the solution for seven years.
What do I think about the stability of the solution?
The product is stable.
How are customer service and support?
There is no technical support since we use the open source version. We find support mainly on the forums.
What's my experience with pricing, setup cost, and licensing?
We use the open source version.
What other advice do I have?
I would rate the product an eight out of ten. The product is the best in the industry.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Performance Engineer at a financial services firm with 1,001-5,000 employees
Feature rich, scales well, and straightforward deployment
Pros and Cons
- "All of the features in Git are useful."
- "The solution could improve by having more customization."
What is our primary use case?
Git is used for version control.
Our extensive IT department collaborates on various projects, utilizing Git to manage versions effectively. One significant advantage is the ability to maintain multiple versions of the same code, even when offline. This is particularly beneficial in scenarios where internet connectivity is not available, enabling individuals to work on their code seamlessly. Ultimately, this is a crucial benefit for our team's productivity and market competitiveness.
What is most valuable?
All of the features in Git are useful.
What needs improvement?
The solution could improve by having more customization.
For how long have I used the solution?
I have been using Git for a few years.
What do I think about the stability of the solution?
The stability is good.
I rate the stability of Git a ten out of ten.
What do I think about the scalability of the solution?
We have approximately 500 people using the solution.
The solution is scalable.
How are customer service and support?
I have not used the support.
Which solution did I use previously and why did I switch?
I have used solutions prior to Git.
How was the initial setup?
The setup of Git is straightforward. The time it takes to set up depends on the size of the project.
When we're doing things manually, but now we use automation tools. When there is a request made it is automated and deployed in the project.
What about the implementation team?
We did the implementation in-house. We have a team that handles the implementation.
What other advice do I have?
A few people in each team have to do the maintenance of the solution.
I would recommend people start using Git. Users can work on an offline copy without internet connectivity and later sync their changes once online. This process is effortless and speedy. Additionally, it is highly secure. After setting up an Azure account, integration with other tools is possible, allowing for continuous integration and deployment.
I rate Git out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Sr DevOps Engineer at a tech vendor with 201-500 employees
Helps to store code in a single repository
Pros and Cons
- "We use the tool to store codes."
- "The product needs to improve its UI."
What is our primary use case?
We use the tool to store codes.
What is most valuable?
Our team members can work together and save the code in a single repository.
What needs improvement?
The product needs to improve its UI.
For how long have I used the solution?
I am using the tool for four to five years.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
My company has more than 1000 users for the solution.
How are customer service and support?
The software's technical support is good.
How would you rate customer service and support?
Positive
How was the initial setup?
The product's initial setup is easy.
What's my experience with pricing, setup cost, and licensing?
The tool is an open-source product.
What other advice do I have?
I would rate the product a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Git Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2026
Product Categories
Version ControlPopular Comparisons
GitHub
Bitbucket
Bitbucket Server
IBM Rational ClearCase
Atlassian SourceTree
DBmaestro Database Source Control
Liquibase
Helix Core
Surround SCM
Apache Subversion
Canonical Bazaar
Buyer's Guide
Download our free Git Report and get advice and tips from experienced pros
sharing their opinions.














