We have approximately 20 software developers using this solution.

I rate the scalability of GitHub a seven out of ten.

We've never had an with the number of projects or developers using this tool. We've consistently had around a thousand developers over the years. The load will increase If a customer adds another 5,000 developers, then we may see some ups and downs in the scalability aspect of this tool, but we are all good with the scalability and stability so far.

GitHub is extremely scalable. We only have about half a dozen repositories in there, but I know some organizations with hundreds working without issue. We're using it extensively. Everybody in the organization is using it, but it's fewer than 50 because our organization's pretty small. We'll increase usage naturally with time, but we're almost close to 100 percent, so it's hard to really increase usage at this point.

It is a scalable solution. 

GitHub is scalable. It's just me using GitHub for my code. But if you had a bigger project with a team, you could always invite anyone to work with the code. GitHub is good for teams because everybody can start with one main code and then open their branch to code freely without destroying any other code. However, there should be one administrator who performs tests to combine each code.

I rate the tool’s scalability a ten out of ten. I have not encountered any issues with the scalability. I am using the tool for my personal projects. If I needed someone to collaborate, a maximum of five people would have access to the tool. I do not have plans to increase the usage for now.

The solution is highly scalable. We have between 100 and 150 end-users, both developers and testers.

The scalability of GitHub is good. I have not come across any limit.

We have six people using this solution in my organization. We have plans to increase usage.

It's obviously very scalable. We have thousands of users on it and there are no concerns.

The solution is very scalable. It’s expandable if you need it to be.

I’m not sure how many people use the solution in our company.

The solution is easily scalable and encourages migration. While I have other products at hand, GitHub makes things fun. We wish to lead and expand. We want to scale this project to the next level, since we have certain customers in hand.

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

We plan to increase the usage of the solution. There are a lot of products out there in the market, but I wouldn't say I would recommend it, but if you use it, then it's fine. I don't really compare much as long as that's what is expected from the solution functionality-wise is fulfilled. So, then I am fine with it.

This is a scalable, cloud-based product. We have a small team and do not plan to increase the number of users.

It is scalable. We can easily extend to team members, with a team of about six or seven people in a GitHub repository. Most users are developers, but we can also provide viewing access to others. We don't have any distinct plans to increase our usage of GitHub.

It is also scalable with respect to the branches.

The solution is scalable. We have approximately 200 users.

GitHub is scalable. We are more than 200 individuals, in many countries.

We have 70 to 80 users on the product currently. We use it on a daily basis.

It's very easy to scale as needed. 

We have different people in the company who are working on different projects on GitHub. It is safe to say that we have about 50 people in total who are using the platform.

The scalability is very good. It has never let me down.

I was using the solution for my own personal projects.

It supports growth. The platform has very many developers in the world, millions and millions of developers, so it's pretty much scalable.

The product is scalable. We have about 20 end users in total. 

We currently did not choose the option with the subscription, but the free version actually provided by GitHub and GitLab is acceptable for us. Maybe the institution wants to increase the number of developers to twenty from what we currently have three, then definitely we will increase and prefer to have additional services from GitHub as well as GitLab.

The product is extremely scalable. We've seen applications that are hundreds of thousands of lines of code and it doesn't have any problems working with them.

I'm a contractor for the Department of Veteran Affairs, and we've easily got several thousand people making use of the code just within the VA itself. It's being used by almost everyone on a product development team, including project managers, testers, developers, and documentation specialists.

This solution is potentially scalable. 

I have never tried a large-scale upload on GitHub. I create separate folders for each application. Right now, I have 15 to 20 applications uploaded and haven't faced any limitations or storage issues so far.

It's scalable.

It is scalable for what we need.

Stability is good, we have around 200 users.

It is scalable. Most companies and big organizations have a repository on the top scale.

This is a scalable solution. We have more than 2,000 users.

We have found this to be an easily scalable solution.

GitHub is scalable, we have around 120 users. They are mainly software developers and engineering managers. We have three people, DevOps engineers and support engineers, working with GitHub and we're likely to expand usage. 

The solution doesn't need to be scaled in this case, as it's just for my personal use.

We have the option to add storage if needed, so it's scalable. 

It's a scalable solution. 

GitHub is scalable.

Every developer in the R&D department is using GitHub in my company. There are approximately 2,300 people in the R&D department.

It is a scalable solution. 

We are not a private company. We are a part of a government institution and we are the IT office of that government institution. There are 14 of us using GitHub.

This is a scalable solution. 

Around 200 users are using GitHub in our organization.

We mostly use the solution for client projects. Across the company, I can't answer how many people use it exactly. We work with customers, so we see it used at the customer end.

We have not experienced any limitations of assets in terms of storage so far.

It's very scalable.

This is a scalable solution. We haven't had any problems where we've run out of capacity. We have 50 users on this solution. 

There are four teams working with GitHub currently in our company.

GitHub is scalable. Our organization has 1,000 people. Approximately 80% would be using GitHub.

I found this product to be scalable, we have at least 500 to 600 users within our company. For a small-scale deployment two people are more than sufficient, but that would increase with the complexity of the deployment.

Scaling the solution is very easy. 

In my organization, there are 130 people currently using GitHub. It has been used quite extensively because 130 guys are using it on a daily basis for checking their codes along with user stories.

We haven't needed anyone for maintenance of this solution.

The scalability is good. We had 20 developers using the solution and now we have 200, there have not been any problems.

Because it is cloud-based, you don't have scalability-related issues. We have around 30 users.

This is a scalable solution. We have between 300 to 400 users. There are five DevOps staff in our team who take care of maintenance.

It is definitely scalable.

The tool is scalable, and we can leverage our DevOps projects using it. My company has 200 users. 

It is on cloud, so it is pretty scalable. We use it in the consultancy department to test and see customer environments and errors. It is also good when doing a cause analysis because you can see the code that is being used.

This is a scalable solution. 

We don't require much scalability. There's the tech team and then we have around 100 developers, managers, some architectural cloud engineers, and a test engineer. They all use GitHub. We don't require maintenance but we have a cloud engineer who is mainly on AWS services. The only thing that I think they need to deal with is generating tokens for new users. We use the solution extensively.

The scalability is good. We're using it with Microsoft, Docker and Kubernetes, and whenever there's an increase in traffic, we're able to manage that. 

I've never had an issue with slowness or anything like that, so my assumption is that it's scalable.

We're using this solution for our personal projects, and there are approximately ten of us.

Since I am working as a contractor in our organization and I'm doing the development work as a site project manager, I don't have a fixed team. But we can say that for each project it's about 10 to 20 people using GitHub most of the time.

It is used on a daily basis.

It is easy to add new users.

This solution is scalable.