The solution was scalable. We could have as many endpoints as we wanted to include in the mess. The system, as it's sold, is designed for mass implementation. Supposedly they have customers managing 300,000 or 400,000 endpoints through one account. We're small change; I get that. The system, the way it looked, and all the features, I thought, could be amazing for a competitive price compared to what we were paying before (which was just a little bit more). It bragged about all these features that didn't actually function. As far as scalability, I would say it could go a long way (again, in theory).

We had six or seven staff/technicians plus maybe another ix or seven limited accounts for some of our power user clients. We have a couple of vendors that might need access to a couple of the containers. Probably we had 15 users in all.

We relied on it heavily. We've got multiple people working in RMM all day long during support hours. During the transition, there were hours and hours of support time, working directly with an engineering team. At some point, when it became obvious that they were going to be unable or unwilling to fix it, we started migrating in a different direction. For nine, maybe ten months, it was used very heavily.

With all of their features, I would say they are very scalable. If someone only wanted to do remote, they could use that portion of the system. We are probably only using about 35 to 40% of what we could be using with VSA. We just don't have what we need to take on the rest of it yet. They're missing some pieces, which prevents us from doing some of the work.

We have four administrators to monitor and approximately 170 staff, but this is installed on approximately 550 computers.

Probably more scalable than I'll ever run into. I have a small company. We're only currently taking care of 700 endpoints. I know they have accounts that have much larger situations. But it scales well.

The product has been scalable so far. I haven't served a massive number of customers yet, and I have had to face issues when trying to scale up.

My company mostly serves the needs of small to medium-sized companies that use the solution. It is difficult to cater to the needs of enterprise-sized customers since they have their own internal IT departments. My primary focus is on small to medium-sized companies or SME sectors with the tool.

Approximately 100 users are using the solution in our organization.

I rate the solution an eight out of ten for scalability.

Scalability is easy with this solution, and you can always go up. However, it is hard to go down because, just like everybody else, once you get to where you have so many users, you can't remove them due to the contracts.

We're actually in the process of growing, and we are hoping to bring on another 45 to 100 endpoints in the next three to four months. We're also in talks with another company to bring on another 300 endpoints in the next nine months, and we're expecting to grow by maybe one technician.

The scalability of the solution is good, it allows for rapid deployment of under an hour, whether for a smaller or larger number of workstations. We package in antivirus along with the remote control aspect, which allows very fast onboarding of clients at a basic level.
The probe functionality allows us to leave the probe on the domain controller and anybody connecting to the network would have Kaseya deployed to their workstation, and we receive an alert of the new addition. This is excellent for management and deployment.

Regarding our internal use of the solution, we had about 35 people using it. 

Our technicians, level one and level two, and our help desk all use this product.

The scalability is good; it is up to the end-user or we can add additional licenses if necessary. We can conduct policy checks as well.

We have a lot of customers that want more agents communicating a single VSA server. For example, 50,000 assets on a single VSA. 

We have 15,000 people using this solution.

I rate the scalability of Kaseya VSA a nine out of ten.

The solution is scalable, we have 15 users. 

VSA is unlimited in terms of scalability.

It is a very scalable solution. Scalability-wise, I rate the solution an eight out of ten.

In my organization, more than ten people use Kaseya VSA.

It is absolutely scalable. It will max out around 15,000 endpoints. The sweet spot is 13,000 endpoints. From my experience, you start seeing performance lags with 15,000 endpoints. Ideally, we'd like to see a Kaseya server handle about 50,000 endpoints. I don't know when that's coming or if it's coming, but 13,000 to 15,000 right now is the sweet spot.

We have several hundred users who use this solution.

I am working with a startup company, and we have 20 people working on the SaaS solution. At my previous workplace, we had Kaseya, and we had more than 250 users using the platform.

The solution is scalable. We manage around eighty clients, each with a minimum of thirty to forty devices, for the solution.I rate the solution an eight out of ten.

VSA's scalability used to be pretty good. We've got quite a bit of performance issues at the moment, and I hope version ten is gonna fix that, but after the hack that happened about two years ago, our VSA has never performed the same. It's always been slower. The performance hasn't been the best in the last two years.

Kaseya VSA is used by everyone in the organization. The solution is deployed on all user's systems.

We have 200 to 300 endpoints. Our customers are medium-sized businesses.

The solution is scalable. We had thousands of users.

We didn't have issues with scaling. When it was set up, it was designed so that, if a business joins, we join them on the server and they have their own ID there. We could install it on the computers. It connects that computer to the whole system. While it's hard for me to answer about scalability in a detailed way (I didn't work on that infrastructure part), my understanding was that it was decent at worst. It was pretty okay.

We used it daily. It was a core product for the servers. However, we were hacked, and for a few weeks, it was quite bad. 

We have about 200 users that are a combination of administrators, developers, and end-users. They do not work on it directly, but we capture the information from the endpoints on the developer's system.

It is quite scalable and easily manageable.

Kaseya VSA is scalable.

On the cloud deployment model, scalability is very easy. We currently have four to five techs on our solution.