Kaseya VSA Reviews

Primarily, we are using it for remote monitoring and management as an MSP. We are basically a reseller; we are a service provider, so Kaseya VSA is one of our tools which we use for our managed services.

The best features of Kaseya VSA are that it's lightweight over the machine and does not create any overhead over the machine resources, which we really appreciate.

I would improve their support system. They can improve their interface, as the GUI looks very outdated. Although they have many features, improvements in the GUI in terms of the front face and the front end would enhance things significantly.

I have been working with Kaseya VSA for almost three years.

I would rate their support five out of ten because most of the time they are not able to resolve the issues and we need to consult the knowledge bases and search the internet to resolve things on our own.

Neutral

We use the native version which comes with the VSA by default. I am working as a Senior Manager for Cloud Computing and Security Managed Services.

On a scale of 1-10, I rate Kaseya VSA an 8.

We use the solution as a remote control tool to help clients.

The unique thing I like most about Kaseya VSA is the quick indicators that tell us if a machine is idle, in use, powered off, etc. This allows us to handle client tasks when their machine is idle.

We're currently migrating from Kaseya VSA nine to ten. Nine's automation capabilities don't exist, which is the main reason we're upgrading to ten.

One area that could be improved is the documentation, which often contains errors that prevent you from following along, especially during migrations.

I have been using the product for ten years. 

The tool itself is pretty stable, but many add-ons are extremely unstable. Their backup products, especially the one built into Kaseya 365, are borderline unusable.

The solution has been scalable for 700 endpoints, but I can't speak to scaling beyond that.

Support often gives incorrect answers, and in a recent case, it took almost two months to get the correct answer, which was simply to wait for them to fix the issue.

Neutral

The tool was our first VSA. We've used NinjaOne and SolarWinds to address shortcomings like remote printing, which didn't work in Kaseya VSA nine but does work in Kaseya VSA ten. The main difference I noticed between NinjaOne and Kaseya VSA was the indicators that quickly showed if a machine was in use, idle, or powered off. This was unique to Kaseya VSA nine. Oddly, they didn't implement it in Kaseya VSA ten initially, but I'm told it will be added this upcoming month. That's why we're upgrading.

The initial setup is complex, mainly because you can't follow the documentation properly. The tool has people who can help with setup, but they're often scheduled months in advance. Deployment feels like an ongoing process. We started with the on-premise version and then migrated to SaaS for more features. Now, we're upgrading to Kaseya VSA ten for automation and integration capabilities.

We have one technician handling deployment on our end and three or four people from the solution's side. It primarily does maintenance.

I find Kaseya VSA's pricing extraordinarily expensive, with very limiting contracts. They discuss being flexible once you're locked in, but I haven't found that true. It is one of the most expensive tools in my arsenal and our highest expense to any company.

I would recommend Kaseya VSA to others but with caution. My main unhappiness is that the tools are focused on larger networks, while my clientele is individuals and very small networks. I ended up locked into contracts for expensive products that don't apply to me, which I'm not happy about.

Because of its killer features, I'd rate Kaseya VSA nine as an eight or nine out of ten. I hope Kaseya VSA ten will be a ten, but it's too soon.

We are a reseller. I am conducting some research since we are a vendor for the Kaseya solution. 

Regarding the patching and software management, for me, it's the best path. We have all the necessary modules for monitoring on the server and workstations. All modules are working well, and for me, it's a complete product.

The network monitoring module today is not the best one. If it can improve, it would be better.

I have used the solution for about ten years.

The solution is stable. For me, it's alright.

I have encountered scalability issues.

The customer service provides a fast response. I have had a chat with the technician.

Positive

The initial setup is easy. I would rate it an eight or nine out of ten.

I haven't documented the return on investment.

It's always expensive for the customer. However, I have no complaints about the price.

I want to understand the difference between NinjaOne and Kaseya.

I will recommend using Kaseya. The overall product rating is nine out of ten.

I am currently working with remote monitoring and management solutions, primarily for patch management. I could describe a few use cases for it, and I use it for that.

Kaseya VSA makes it easier for me to use, especially with the ability to control everything from the console. Kaseya VSA is more user-friendly, and I see key differences, both pros and cons, in comparison to other competitors in the market. So far, it is okay as there are no disadvantages of Kaseya VSA in comparison to other solutions because everything has been good since I have used Kaseya VSA longer than I tried to use Comodo.

So far, everything is good, but regarding automation scripts, I would like to see improved or enhanced scripting capabilities where I can create scripts based on automation by using AI. So far, everything is okay, and I want to point out there are no specific features missing that I would like to see included in the future.

I have been working with Kaseya VSA for three years.

I know something about the tech support, and I have escalated technical support tickets to the customer service team. I would evaluate them as most likely all good because they help me a lot, and they most likely solve my issue.

The initial setup is quite difficult as the allow port, everything is quite difficult, and especially you need to get the SSL to use if you use it for on-premises.

I don't know about the price because I'm not handling the pricing aspect of Kaseya VSA.

I will share my rich experience with Kaseya VSA with others, and I suggest using Kaseya VSA. I gave this review a rating of 9.

We're a small computer shop, so we use it as the remote control tool when clients call for help and ask us to walk them through something. But we've also got it set up to monitor Windows logs and notify us when an update fails to install or a hard drive is developing a bad block. The sort of thing that allows you to stay ahead of trouble. 

Also, little housekeeping things like hard drives filling up, so you empty the recycle bin, delete the temporary folders, that sort of thing. It's scripted, so it all happens automatically. We get a note saying, "Hey, there was a problem, but we took care of it," which is kinda nice.

As a small IT shop, the weird feature that the VSA has that I have not found anywhere else is they have these little colored dots that tell you the status of the machine. Is it offline and powered up? Is it actively being used? Is it idle? A lot of our clients ask us to do things for them, but, of course, they don't really want us to be underfoot. So we always look for, "Hey, there's an idle machine. We can work on that one now." And to say it makes it easy, we can do that at a glance. In any other tool we've looked at, you have to go several layers deep to see if the machine is in use, and you could spend your entire day just trying to find a machine that was idle, whereas, with Kaseya VSA, you can tell at a glance.

Moreover, Kaseya's got a new version coming out. We're waiting for a couple of features to be updated on it, but the big thing that they're providing in the next version is they'll also give us the ability to remotely help people with phones and tablets where now, if a client has a problem with the phone, which we frequently get, you know, hey, I need to change my password or I change my email password. Don't know how to do it on the phone, and we have to walk them through it or they just have to stop by my shop. Now we'll be able to take care of it for them.

Kaseya's remote control strengths are for a remote control tool. They're a remote tool lacks. Doesn't do terribly well with multiple monitor support. Doesn't do terribly well with remote printing. And there are other tools, like remote for multiple monitors, TeamViewer, and also remote printing TeamViewer does another job. But they are working on it. 

So there is room for improvement in the remote control strengths. 

I've been a Kaseya client for more than a decade.

I've been using it for more than a decade. It's fairly stable.

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.

Support can be frustrating.  Often they tell you how things are documented which ends up being different than how things work in reality.

Positive

The initial setup is fairly complex, but they're pretty good at walking you through things.

We were running an on-prem server until a year and a half ago when we switched to the online version, so they're taking care of all the maintenance for us now is much easier.

I will rate Kaseya on its ROI an eight out of ten. 

I'm sure there are cheaper products. They seem like a large expense to me, but they're also a large source of revenue because we have to pay just to be able to have access to help clients remotely. I do take the time to look at them. But I haven't found any of them that would work as well.

Be careful with your expectations.  They announced an included backup solution last May and truthfully it has failed to meet expectations until very recently.  That means that I paid for something that I truly was not able to fully use for ten months.  Recognition of this has been lackluster.  I doubt that I will renew my contract at this point.  Kaseya has ruined what used to be a very positive relationship.  Avoid the Kaseya contract nightmare and investigate purchasing their products through Techs Together instead.

I use the solution since it functions as a virtual system administrator that allows me to monitor our company's clients' networks, and the tool serves as an RMM solution. The product allows me to monitor our company's clients' networks and administer and make changes. The solution also allows me to deploy policies, especially in areas like patching or software updates. The tool serves as a single platform to manage everything with just a few clicks.

The most valuable features of the solution stem from the improvements made in the security area since the product dealt with the major security breach a few years ago. In the product, it is good that users need to change the passwords and reset them every 30 days. The solution just makes the administration of networks much easier, making it a cost saver for my company's customers because now they don't have to pay for my time to visit them since I can even send my technicians to see them.

The product's user interface is an area with certain shortcomings where improvements are required. N-central's user interface looks much prettier and is probably easier to navigate than the one provided by Kaseya VSA. Once users get the hang of how to use the Kaseya VSA's user interface, the features can help them customize reports and do a whole lot of things. Kaseya VSA's user interface or the initial landing page is not very pretty, but it is fine and works perfectly.

I have been using Kaseya VSA for around four years. My company provides services related to the product since we have a partnership with Kaseya VSA, which functions as the solution's MSP.

The tool has been stable since it crashed a few years ago. SolarWinds and then Kaseya crashed a few years ago, after which both the product work was done in areas like patching, software updates, and everything else.

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.

The product's support team is very quick to respond, especially because the tool's technical team operates in the same time zone where I am located. One of the challenges my company faced with SolarWinds stemmed from my organization and SolarWinds' technical team operating in different time zones. If my organization and Kaseya's support team are considered, there is only an hour or two between our time zones, which is fine for us. I haven't faced scenarios where I had to escalate certain issues and deal with the technical support team of the product.

I have experience with N-able N-central. I moved from N-able N-central to Kaseya VSA since the latter offered me a product called Network Detective PRO, which allows me to scan networks and produce reports that I can use to onboard customers or try to sell the product to the customers, even though N-able and Kaseya were available at the same prices. The aforementioned reasons prompted me to choose Kaseya tools.

In terms of the installation part of the product, I use the solution's remote version completely, so it is just a matter of sign-in, and there is nothing to install. All I need to do to onboard a customer is that I need to create the customer account on the portal, after which I download the agent, which is the tiny file, and then I deploy it on the customer's network, and the tool does the rest of the job by itself.

The solution's deployment process doesn't take much time. Depending on the network's size, users install the agent on one of their servers, after which it scans the network, and as the machines come live, it deploys the agent to those machines. In general, the deployment process doesn't take long since it can be done within a short period of time, especially if all the endpoints are present in an environment, because it can manage a network relatively quickly in around an hour, as it can pull up all the information.

The tool is meant for anyone who operates in a type of environment after the COVID-19 pandemic, where most people work remotely and face-to-face contact is minimized. Tools like Kaseya VSA are always the best since they ensure a good investment return.

Kaseya VSA can be described as a fairly priced product. The product's end customer is the one who has to ensure paying for the agent. If a user has 50 network nodes in their environment, then there is no need for them to pay for 50 nodes, so the price is an area that is passed on to the customer.

The tool is meant for customers looking to run an efficient service without employing an IT resource, which makes it a cheap resource, especially considering that I charge my customers for every device that I monitor and manage in their environment. The tool operates at a fraction of the cost when compared to the monetary resources needed to employ a full-time person.

I rate the overall solution a ten out of ten.

Kaseya VSA is used for maintaining laptops, patching the systems, and securing the platform.

The most valuable feature of Kaseya VSA is the ability to control laptops remotely. Kaseya VSA is a cheap and user-friendly solution.

The solution's automation capabilities are not very strong. Therefore, I am looking for another system. Kaseya VSA is not very strong for updating and monitoring.

The solution should have more third-party applications and a system for updating the applications. It's very difficult to update the third-party software on every device. It's very simple to patch the updates of the nodes, but it's not simple to update third-party software.

I would like to have the solution's features upgraded every year.

I have been using Kaseya VSA for more than ten years.

Approximately 100 users are using the solution in our organization.

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

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven out of ten.

Kaseya VSA can be very easily deployed in a few minutes.

The solution's pricing is reasonable.

You have to log in to a portal. I have an overview of all the devices and a brief view of the system malfunctions. With Kaseya VSA, what you see is what you get for that price. The solution saves me a lot of time by allowing me to help people remotely. It's very easy to add new devices via remote without disturbing the person.

Overall, I rate the solution a seven out of ten.

The product was basically used for remote-in support and monitoring for the ~1,500 endpoints that we manage. The intent was to use the integrations to be able to deploy group policies and updates and push down antivirus updates such as Windows updates and things like that. Our intent was to leverage all of these so-called features that never functioned at all and ended up just putting us in a really bad position, left scrambling to find a functional replacement on the fly.

Kaseya VSA resulted in the loss of multiple clients and thousands of dollars throughout the endeavor. It also caused much additional undue stress with a third-party collector harassing us.

What we were able to marginally use it for was when a client would need assistance, desktop assistance, remote-in, we could do that (most of the time). And managing however many servers we manage was possible so long as we didn't dare connect to more than a couple endpoints at a time. That said, any RMM product should be able to handle these functions as remote-in connectivity is the fundamental purpose of RMM.

They had a major issue that resulted at one point (the straw that broke the camel's back for us, although we'd been fighting with support for months by that point in time) in which every Kaseya VSA customer was offline for two weeks. This vulnerability pushed us over the edge.

It never functioned as intended. If it functioned as it was supposed to, it would've been fantastic. However, the previous solution we used just performed reliably and so much better. I can't say that there was anything positive about my experience.

The intent of the software, other than integrations, is to be able to just make an anytime secure direct connection to an endpoint. However, whenever we would connect, at least half the time, it would not record keystrokes properly, no matter what system we connected from. So if you're trying to enter a password, there'd be 2-3 seconds' latency in the response and then it would just spew out a bunch of letters and numbers you didn't type in. You would just try, try, try again to type in something, and just half the time it worked, half the time it didn't. If you brought up more than three or four endpoints simultaneously, it never worked. It was a major point of contention for us.

For us, at least, it just didn't work. It just was broken. Scripting didn't fire, reports didn't come back, and monitoring wasn't there. A server goes down or a router goes offline, no notification. Stuff like that. Bush league.

We used it for a little over a year before we were able to rid ourselves of it. Fourteen months is about as long as we were on it.

The stability was as poor as could be. I would honestly wager that 20% of the time at best I could sit down for an evening for scheduled maintenance/upgrades and actually get through it. 4 out of 5 times I ended up either not bothering at all and just driving to the client location or rescheduling. Very frustrating.

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 technical support, no resolution ever came about. We had one experience after the next having tickets marked as closed or completed when they were not satisfactorily closed or completed, and we'd have to reopen them. The support, however, was responsive. We just had an anomalous type of situation that they were unable to resolve. I'm an IT guy; I get that that can happen from time to time. Still, their unwillingness to just release us from their EULA and say, "Okay, you know what? We're sorry, we can't help you. We're going to give you a refund of a couple of months and leave you alone to move along and find another solution," instead of having to turn it into a complicated, harassing legal issue, that was my biggest problem. It was a very costly experience as far as support was concerned.

Negative

We used a previous RMM called NinjaRMM prior to that. With the promise of this new integration and all these features, we migrated to Kaseya VSA.

NinjaRMM was a little more basic; however, it did a lot of what we needed. It lacked some integration features, primarily with PowerShell scripting, which is why we made the choice to move anyway, and of course, we've moved on since then. It was a good experience for the most part. NinjaRMM we used for a couple of years and with good support when we needed it. Again, it was a very limited version of an RMM solution at the time. I understand it's evolved over the last few years. Still, in retrospect, I was very satisfied with it and our staff was very disappointed that we moved away from it.

The setup was pretty straightforward. We had a demonstration, a virtual machine that was set up for us, and we were given, 30 or maybe 45 days to play with it. It ran side by side with our, at the time, current RMM solution. We didn't get a real chance to push too many API integrations that the Kaseya VSA claimed it would make as that would have caused a conflict with what we were doing with our current RMM solution. 

Everything we attempted to do at the time, and we ran into a couple of these issues, were explained by the engineer that we worked with (as well as the sales representative) as just issues we were facing due to it running in a demo. After we voiced our concerns, we were told once it's at a full, paid version, that those issues will be resolved. From a technical standpoint, they seemed to have just taken our demo container and migrated it into a live version and never actually resolved any issues we had with the demo. Definitely one of those classic situations where the sales team was amazing and then, once you signed on the dotted line, they were nowhere to be found.

We used the NinjaRMM platform to push the installation for the VSA. The setup was within a month, within 30 days. In that time, we were able to push it out to all of our endpoints.

Maintenance and updates were all managed by our support contract. They would schedule times. Generally, it was 3:00 AM or 10:00 PM, and notified us a couple of weeks in advance, unless it was a critical topic. We were just made aware of scheduled maintenance in advance.

We had a consultant help with the initial setup. It was a really good experience in that regard. When sales is present, they make sure everything's right. Once that's over, then you're on your own with support, if you can get any. That part of the process was perfectly fine. I had a lot of high hopes for it at the time.

In a nutshell, simply due to the fact that our after-hours maintenance and emergency service were so affected, we went from positioning ourselves to be able to do full-scale implementations from home-based offices at night to literally in the middle of the winter in Northern Michigan, having to drive two hours one way and stay there till 11:00, 12:00 at night to do the work because we were unable to do it from our offices as we had always been able to. Therefore, we did not see any ROI. Not good on the marriage having to be gone until after midnight for something I should be able to do from the home office and wrap things up by 9pm.

On top of it never working, losing clients in the process, they refused to stop billing me for a solution that never worked, and it ended up becoming a complicated legal/collections issue. They have a three-year "contract", if you will, through their EULA, and it took me a great deal of headache and wasting even more of my valuable time providing dozens and dozens of support ticket threads to a legal team to be able to prove that they were not upholding their end of the EULA. Even then, the harassment continued. Therefore, on top of just the constant loss of time and resources and energy and frustration, they continued to hound me on the phone about a past bill that I refused to pay. It was the worst company to work with, and I've been doing this for 25 years. It's the worst vendor relationship I've ever experienced in my professional career.

Without the managed antivirus, it was about $2,000 a month for the team. It was quite reasonable in that sense. The industry standard is anywhere from $0.90 to $1.10 per endpoint for antivirus, depending on how many you have, so it was competitively priced.

In terms of pricing, based on my experience, on a scale from one to five, I would rate it pretty poorly as it didn't work. If I'm assuming that it functioned as it was intended to function, then I would give it probably a four. As it stood, I'd rate it a one for what I was paying for, for what I was getting.

Some SolarWinds products looked really solid, but too expensive for what we were looking for. Kaseya VSA was cost-effective at the time of research, which was a big selling point.

Mainly, I hope that somebody else gets a one-star review in front of them when they're making a decision so they don't have to go through the same mess that I did.

After being down for two weeks after a DDoS attack, and there were a lot of unhappy clients on our end. Due to this, maybe three or four customers decided to move away from us as we were unable to provide adequate support. Granted, they were customers we hadn't had for long and hadn't established long-term trust relationships with; however, we probably lost out on $25,000-$35,000 annually in contracts due to VSA's failure to perform.

I'd give it a two out of ten as their support always did endeavor to really help, even eventually escalating it all the way up to the chief engineer in England who, with his team and I, spent an hour on the phone with my demonstrating to him what was going on and his acknowledging and recognizing it. However, that's the only reason I wouldn't give it a one. It was a nightmarish year trying to get through it. It didn't help that it was in the middle of a pandemic. 

The solution can be deployed on-cloud, on-premise, and hybrid.

The most valuable features of Kaseya VSA are remote control, live connect, and automation.

The audit and KNM tools could improve.

In the next release, it would be useful to have an iOS and Android application to provide more visibility.

I have been using Kaseya VSA for approximately 12 years

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

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 support from Kaseya VSA could improve. We have multiple customers that have had delays in receiving a response from the agents for small issues. We have to find solutions ourselves after creating the tickets.

I rate support from Kaseya VSA a five out of ten.

Neutral

We have to understand the customer's requirements then we can map the correct deployment for them, such as retrieving the VSA applications, automation, and database. The full process including the configuration and licensing is one week.

I rate the setup of Kaseya VSA a ten out of ten.

Customers purchase the solutions because it is priced well. There are additional services that have an additional cost.

I rate the price of Kaseya VSA an eight out of ten.

We have compared this tool to others and it is good.

I rate Kaseya VSA a ten out of ten.

We actually use it for a few different purposes. We use it as remote control connectivity software, allowing us to troubleshoot and work with staff and customer computers on-site without having to travel to the locations. It is also used for patch management and software deployment. Instead of having to manually go out and do them on each computer, we run all of our Windows updates and Mac updates through Kaseya VSA.

When compared to what we were previously using, one of the most appealing features is that it combines remote control, patch management, and software management into a single portal. 

We had two different portals to do that with our previous software. We had a remote control software portal first, followed by an endpoint management portal. We would have to log into two different applications to accomplish the same task that we can do with just one portal with VSA which was one of several reasons we chose to use Kaseya VSA. 

Another major reason was with our previous version of patch management software that was primarily on-premises we were getting so much bloat on our hard drives from all the different patches being downloaded and saved that we were running out of space on those systems faster than we are on this cloud-based one.

One aspect we did lose when we moved from NetOp to VSA, is the ability to transfer sounds. In the past, if we connected to your machine and you were watching a video, we could hear exactly what was being played. Sound cannot be transferred using the cloud agent that they currently have. That is one area where we would like to see them improve.

The main difference would be the addition of audio transfer between the end-user and the remote connectivity software. That is the one critical piece that we are currently lacking.

The audio would be the only source of contention on that one.

We have been using Kaseya VSA since 2020.

So far, we haven't encountered any problems with it not working with anything. It's been extremely stable. Except for that one data breach, we haven't even experienced any downtime. Then we were offline for a week or a week and a half with that one.

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.

I would rate the technical support a five out of five.

They contacted me, did a screen share with me, and walked me through exactly where I needed to be. To make the change that I couldn't find myself.

Positive

Before VSA for the remote control aspect, we were using NetOp by Danware,  and for our software updates, we were using GFI LanGuard.

In terms of the initial setup, it's a bit of a mix. We had some help getting it set up. They assigned a team for us and walked us through our first deployment, getting everything set up. The complicated part was that there were a lot of menus at first, and some of the terminologies they used were a little different, and they're retiring some of them right now. For example, one of their areas is called Patch Management. A normal person would assume that's where I'm going to do all my patches. That is not the case. Patch Management was a legacy piece that they were trying to get rid of, it's all done under Software Management. There was a lot of stuff that this program can do at first, and being a newbie with it was a lot thrown at us right away. 

We have completed the training since then and are now VSA certified. Since the training and certification, a lot more of it makes sense as to why things are the way they are.

They built the backend, which includes our cloud portal, in a very short period of time. In order for us to deploy them, we probably had them up and running within two or three business days.

Overall, we estimate that our return on investment was around $2,300 per year.

We do a yearly license with them.

The cost appears to be determined by the number of computers on which the endpoints are placed.

We were looking at a price of $22.50 cents per user. That works out to $11,250 per year.

It was cost-saving, with our NetOp and GFI. It actually resulted in a $2,300 cost savings.

I understand that each case will be different. I would personally recommend VSA. There are many different pieces and modules that can be integrated into this. This would definitely be for a small to medium-sized or enterprise business, such as some of these home office businesses. I would not recommend this if there are less than ten computers in one location. There are probably cheaper items available for them that would serve them better. However, for an office with over a hundred users, multiple locations, and small IT tech teams, this has been an invaluable service for us to have.

I would rate Kaseya VSA a nine out of ten.

They do put a lot of things together. And they try to put everything on one portal, which is very convenient for the IT department because it allows them to see everything within the scope of one portal. I believe there is room for improvement in how they design their UI interface to make it more user-friendly. But, aside from that, everything has been great with them.