Try our new research platform with insights from 80,000+ expert users
reviewer1829205 - PeerSpot reviewer
Senior Performance Engineer at a financial services firm with 1,001-5,000 employees
Real User
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.

Buyer's Guide
Git
August 2025
Learn what your peers think about Git. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
865,164 professionals have used our research since 2012.

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.
PeerSpot user
Rahul Rajpurohit - PeerSpot reviewer
Sr DevOps Engineer at Aptos
Real User
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.
PeerSpot user
Buyer's Guide
Git
August 2025
Learn what your peers think about Git. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
865,164 professionals have used our research since 2012.
Senior manager at Softstoneinc
Real User
Top 10
The solution is stable, easy to use, and it can be used for application development
Pros and Cons
  • "The product is easy to use."
  • "The price could be improved."

What is our primary use case?

I use the solution for application development.

What is most valuable?

The product is easy to use.

What needs improvement?

The price could be improved.

For how long have I used the solution?

I have been using the solution for almost ten years. I am using the latest version of the solution.

What do I think about the stability of the solution?

I like the product’s stability. I rate the stability a nine out of ten.

What do I think about the scalability of the solution?

The tool is scalable. Five people in our company are using the solution. It is not used extensively in our company.

How was the initial setup?

The initial setup was straightforward. The deployment took five minutes.

What about the implementation team?

I could deploy the product by myself. I used GitHub Actions for deployment. We need one person to deploy and maintain the product.

What's my experience with pricing, setup cost, and licensing?

The tool is not expensive. I rate the pricing a three or four out of ten on a scale where one is cheap and ten is expensive.

What other advice do I have?

People should use the solution because it is easy to use. Overall, I rate the solution a nine out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Senior Developer at SmartStream Technologies ltd.
Real User
A standard and open-source product with features like git clone
Pros and Cons
  • "It is a pretty standard product with features like git clone and development branches."
  • "Git is mostly command based and needs to have a helpful user interface."

What is our primary use case?

We use Git for our code. 

What is most valuable?

It is a pretty standard product with features like git clone and development branches. 

What needs improvement?

Git is mostly command based and needs to have a helpful user interface. 

For how long have I used the solution?

I have been working the solution for the last three years. 

What do I think about the stability of the solution?

Git is highly stable and I would rate it a ten out of ten. 

What do I think about the scalability of the solution?

The solution is highly scalable and I would rate it a ten out of ten. My company has 500 users for it. We use it on a daily basis. 

How are customer service and support?

We don't connect with the support team since all the information is available on the internet. 

Which solution did I use previously and why did I switch?

We switched to Git because it supports multiple vendors. 

How was the initial setup?

Git's setup is easy and I would rate it a nine out of ten. There are documents available with plenty of information. Hence, if there are any issues, you can sort them out. The tool's deployment is fast. 

What about the implementation team?

We did the product's deployment in-house. Users can do it by themselves.

What's my experience with pricing, setup cost, and licensing?

Git is free and you don't have to pay for it. 

What other advice do I have?

I would rate Git a nine 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.
PeerSpot user
Matt Hardy - PeerSpot reviewer
Infrastructure Manager/Deployment Manager at Hivedome Consultancy Services
Real User
Top 5Leaderboard
It has a large community, so there are lots of resources
Pros and Cons
  • "Git is a product everyone uses, so it's almost inescapable. I like the fact that there is a large ecosystem around it. You can bolt various graphical user interfaces onto it or sign up for various repositories like GitHub and AWS CodeCommit. Git has a large community, so there are lots of resources and knowledge bases you can use."
  • "The scalability could be better. I think it requires some discipline to have large teams working on the same project without facing problems merging code. I'm using Git for personal projects, but I know companies face merge conflicts when more than one person is working on code simultaneously."

What is our primary use case?

I'm doing little projects to teach myself things and storing them in a Git repository. We have about 20 users at my company. We're open to using it more.

What is most valuable?

Git is a product everyone uses, so it's almost inescapable. I like the fact that there is a large ecosystem around it. You can bolt various graphical user interfaces onto it or sign up for various repositories like GitHub and AWS CodeCommit. Git has a large community, so there are lots of resources and knowledge bases you can use. 

For how long have I used the solution?

I have used Git for about three years.

What do I think about the scalability of the solution?

I rate Git seven out of 10 for scalability. The scalability could be better. I think it requires some discipline to have large teams working on the same project without facing problems merging code. I'm using Git for personal projects, but I know companies face merge conflicts when more than one person is working on code simultaneously. 

How was the initial setup?

Git is easy to set up. I've done it multiple times on various systems, and it only takes a few minutes. 

What other advice do I have?

I rate Git eight out of 10. 

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Environmental engineer at Coventry Building Society
Real User
A free tool that helps with website management
Pros and Cons
  • "I use the solution for website management."
  • "The tool's user interface is terrible. It needs to be more user-friendly."

What is our primary use case?

I use the solution for website management. 

What needs improvement?

The tool's user interface is terrible. It needs to be more user-friendly. 

For how long have I used the solution?

I have been using the product for ten years. 

Which solution did I use previously and why did I switch?

I used a version control software called Bazaar. I switched to Git since everyone is using it. 

How was the initial setup?

The tool's setup is straightforward. I could complete the solution's deployment in two minutes. 

What's my experience with pricing, setup cost, and licensing?

The tool is free. 

What other advice do I have?

I would rate the solution a five out of ten. There are better solutions out there than Git. 

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Software developer at Abc solution
Real User
With an intuitive interface in place, the tool is extremely easy to manage
Pros and Cons
  • "Git is easy to manage...It is helpful for me and easy to manage the interface we are using from development to production."
  • "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."

What is our primary use case?

We use Git for the desktop to maintain some versions of the codebase.

What is most valuable?

Git is easy to manage, which is one of the main features. Also, the codebase is a major feature. It is helpful for me and easy to manage the interface we are using from development to production. So we manage the versioning of codebases.

What needs improvement?

The price is an area that needs improvement.

The process of raising a pull request could benefit from some improvement. Currently, when a pull request is created in an organization, a branch is also created. However, each pull request must be individualized to a specific branch. 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. Therefore, it would be beneficial if pull requests were individualized to each user so that any modifications made are attributed to the specific user's pull request.

For how long have I used the solution?

I have been using Git for a year. Also, I don't remember the version of the solution I am using.

What do I think about the stability of the solution?

Stability-wise, I rate the solution a nine out of ten.

What do I think about the scalability of the solution?

Scalability-wise, I rate the solution a ten out of ten.

How was the initial setup?

The solution's initial setup process was easy. It is also easy to get the data. So, even though there are a large number of files, it's easy to clone and get the data details and codebase easily.

What's my experience with pricing, setup cost, and licensing?

The organization looks into the pricing aspects of the solution.

What other advice do I have?

I would recommend the solution to those planning to use it. I rate the overall tool 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.
PeerSpot user
Founder at Simpro Tech
Real User
User-friendly, easy to install, reliable, and effective project management
Pros and Cons
  • "Version control is beneficial as it allows me to keep track of all the modifications I have made to the applications."
  • "It would be preferable if the updates could be completed at a faster pace."

What is our primary use case?

I use Git to manage my personal projects involving web basics, web design, and web pages. I am able to clone most things using Git.

I use it for web design version control. I also conduct a lot of research on open-source technologies that we can install using Git.

I have discovered that most of the solutions offered on Git can also be found on Docker.

How has it helped my organization?

It would be preferable if the updates could be completed at a faster pace.

What is most valuable?

Version control is beneficial as it allows me to keep track of all the modifications I have made to the applications.

What needs improvement?

I have no problems with Git and prefer using the Terminal Point of View for its high speed.

I attempted to use an alternative user interface, but it was too sluggish for me. I discovered that the Terminal is more efficient and rapid for executing events on Linux and Ubuntu. Its swiftness in event deployment is remarkable.

For how long have I used the solution?

I have been working with Git for three or four years.

I update the versions every now and then.

What do I think about the stability of the solution?

I would rate the stability of Git a nine out of ten.

Performing periodic updates can be time-consuming, but it is not a significant concern as it doesn't disrupt my schedule. However, I do need to make a conscious effort to initiate the updates.

What do I think about the scalability of the solution?

Git is a scalable solution.

Another advantage is that any team can work on it effortlessly, even large teams, making it highly collaborative.

I am currently using it and there are only a few people who I would like to share my changes with. With the current capability to view the modifications I have made, I am able to open it and see the updates for my team.

I am not planning to increase my usage at this time.

How are customer service and support?

I have not contacted technical support.

Which solution did I use previously and why did I switch?

Ever since I began my training in web and development, it was the easiest platform for me to use and was the only one that was introduced. I did not explore others.

How was the initial setup?

The initial setup is straightforward.

The deployment process was quick for me. I was able to execute it on my personal computer and also clone it to my personal Git account.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

I highly recommend others use Git for version control.

Because of its version control, I would rate Git a ten out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Download our free Git Report and get advice and tips from experienced pros sharing their opinions.
Updated: August 2025
Product Categories
Version Control
Buyer's Guide
Download our free Git Report and get advice and tips from experienced pros sharing their opinions.