Try our new research platform with insights from 80,000+ expert users

Automox vs Kaseya VSA comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Automox
Ranking in Patch Management
17th
Average Rating
8.8
Reviews Sentiment
8.1
Number of Reviews
10
Ranking in other categories
Vulnerability Management (50th), Endpoint Protection Platform (EPP) (61st), Enterprise Mobility Management (EMM) (18th)
Kaseya VSA
Ranking in Patch Management
8th
Average Rating
7.6
Reviews Sentiment
4.6
Number of Reviews
32
Ranking in other categories
Remote Monitoring and Management (RMM) (2nd)
 

Mindshare comparison

As of April 2025, in the Patch Management category, the mindshare of Automox is 3.6%, down from 3.6% compared to the previous year. The mindshare of Kaseya VSA is 3.5%, down from 4.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Patch Management
 

Featured Reviews

Jack Leung - PeerSpot reviewer
Easy to use and deploy agents but needs more stability
We just need to deploy the agent to the endpoints. We don't need to set up anything. For a single agent, it takes one or two minutes. However, we deployed globally, and you need to take into consideration the time it will take to deploy across each endpoint. It's very simple to deploy. We had three or four engineers take care of the implementation.
Ben Blissett - PeerSpot reviewer
Broken from the beginning and never functioned as anticipated
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's super easy to use and we haven't found anything easier."
"It's easy to deploy agents to endpoints."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"Previously, we would run a report, scan it, and compare it. We were spending 15 to 30 minutes a month on each machine on this stuff because you would find stuff that wasn't up to date, then you had to fix it. This solution takes that time down to minutes. Automox saves us easily many hours a month."
"Its flexibility is most valuable."
"They've been adding some new features lately, which I'm not nearly as familiar with, but the ability to just deploy patches and exempt certain machines from certain patches is helpful. For instance, for our servers, we may not want to roll out zero-day patches. We are able to exempt those and make sure that they don't get those policies. We've got certain servers that have to run a particular version of Java, and being able to exempt those servers from receiving Java updates is pretty fantastic."
"The fact that it's just one product that can patch multiple operating systems is really great."
"Among the most valuable features are its ease of use and the Worklets. Both of them are time-savers. Worklets enable us to customize things for a given environment. It's something like when Apple lets other people create applications. Other peoples' Worklets can be used in our environment and in our customers' environments. That saves a lot of time, and it's really cool."
"Kesaya is highly configurable."
"Provides efficient automation."
"The most valuable features of this solution are automation, inventory, and patch management."
"We can schedule the patching of the endpoints."
"The most valuable feature of Kaseya VSA is the ability to control laptops remotely."
"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."
"The patching is very efficient and we can rely on the alerts that we receive."
"The patch management and the remote support are very good, especially the remote support. There is a module built into the solution which allows remote control without necessarily interrupting the user. We could manage things in the background without them seeing or interacting with anything, which is a very useful feature."
 

Cons

"It should have integrated workstation access. So, there should be a remote desktop feature."
"There should be better inventory capabilities. Right now, they only allow you to have insight into software out-of-the-box. It would be nice to also extend that into custom inventory that can be modified and managed by the practitioner."
"The only thing that we've ever truly wanted is an onsite repository. Currently, all updates are provided directly from the internet. So, if you have 1,000 devices, all 1,000 devices go directly out to the internet. We would love the option of being able to put the updates on local storage so that we're not consuming as much bandwidth. That is literally the only thing that we've ever wanted."
"We would like to see additional detailed reporting for Service providers like us. We had to build our own reports via their APIs to meet our needs."
"The stability has come a long way from what it was like when it started and now it's really good."
"As concerns the patching concepts, there's a bit of a learning curve in terms of working out how Automox wants you to work within the console, not only splitting up everything into groups, but then having the various policies assigned."
"When we bring on a new client, we need to go into that client and manually set up my account, my chief engineer's account, three technicians' accounts, and a billing person's account all over again, which is annoying. We have probably up to 15 or 16 of our clients on Automox now. For every single one of those, we have had to go in and set this up. Then, if anything changes, we have to remember to go to Automox and change it 15 or 16 times. So, we just want inheritable permissions, and that is it. We have talked to them about this, and they are like, "Yeah, we hear a lot of complaints about it." I am thinking, "Guys, I have been complaining about this for a year and a half. When are you going to do it?" It must be some tricky thing or not an easy fix, because I can only assume if it were easy, then they would have done it by now."
"Asset management would be a great feature to add to Automox. We would run easier scripts or more out of the box scripts that would help us in audits. \"
"One area that could be improved is the documentation, which often contains errors that prevent you from following along, especially during migrations."
"The agent-based monitoring solution can be improved."
"The audit and KNM tools could improve."
"The product's user interface is an area with certain shortcomings where improvements are required."
"Its scripting language kind of sucked. They have their own version of PowerShell inside VSA. if you want to reach out and grab endpoint information, for instance, to know how many end devices have a program installed, you actually have to write a script for that. It wasn't like how it is in CrowdStrike where you can just do a search, and it just happened. In VSA, you have to write your own script to do it. In terms of new features, an integrated MDM for mobile devices would be awesome."
"It's very difficult to update the third-party software on every device."
"There should be more Mac support. Whenever a new Mac operating system comes out, the support is very limited. It takes them a while to get things up to date. We're seeing more and more people move to Mac from the Windows environment for various reasons, but their support for Mac is very limited. A lot of it might have to do with Mac itself, but there are ways to improve upon that. That would be my biggest thing for improvement."
"The reporting feature in Kaseya VSA could improve by being more user-friendly. The reporting overview is too wordy or the representation can be better."
 

Pricing and Cost Advice

"The pricing and licensing costs have been great for us... My advice to others who are evaluating or thinking of implementing Automox is to give it a shot. If a free trial is still available, definitely use it, because it makes life a lot easier."
"For all these software tools, it is usually a subscription model. There is a monthly charge that we need to pass along to our clients because we are doing all this for their benefit. It is only a couple of bucks a month per computer, and that is a low enough price point where our clients, without exception, have accepted it, and said, "This is great. We will pay that. It sounds like a worthwhile thing.""
"The cost is very reasonable compared to the competition."
"We're doing it annually directly through Automox. It is per endpoint. It is $2 and some change per endpoint, but I believe the cost is right around $28,000. Everything is covered in this fee."
"We are on the premium licensing, which is the one that has the API capability that we use."
"The product is a great value."
"Its licensing for a year was nine grand. There was no additional fee."
"Automox just charges us a set amount per user, per month, for using the product. That is very important to us. Because it's a cloud-native solution, you're saving on the cost of hosting an on-premises solution on your servers."
"I think it costs more than ManageEngine."
"The solution is robust and the price is good for the features that are provided."
"We pay a monthly fee, but it's a three-year contract divided by 36. They don't offer a true SaaS plan where you can add licenses monthly as you go. The cost is $7 per person per month, and we are paying about $1,700 a month."
"It depends on what products you want. Kaseya loves packages, and if you are packaging, it is more affordable. If you're not packaging, it tends to be a little bit more expensive than others."
"Without the managed antivirus, it was about $2,000 a month for the team. It's 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 fairly priced."
"You're going to pay for this solution, but you're going to get so much more out of it in reporting, asset management, and the ability to manage your clients. I would recommend giving Kaseya serious consideration and I would recommend implementing it."
"It is not expensive. Anyone can afford it. Most of the time, we get a discount for licenses. We had about 5,000 agents, and we received a discount on the price. There is only the licensing cost. If you use the on-prem version, you also have the infrastructure cost."
"Customers purchase the solutions because it is priced well. There are additional services that have an additional cost."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
846,617 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
8%
Government
8%
Manufacturing Company
7%
Computer Software Company
13%
Educational Organization
6%
Healthcare Company
6%
Financial Services Firm
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Automox?
It's easy to deploy agents to endpoints.
What is your experience regarding pricing and costs for Automox?
We do pay a monthly licensing fee. I'd rate the pricing as average. It's not cheap yet not too expensive. You can also pay for more support if you require them to provide consultancy services.
What needs improvement with Automox?
They need to improve the automation features. It could be more stable.
What do you like most about Kaseya VSA?
The most valuable feature of Kaseya VSA is the ability to control laptops remotely.
What needs improvement with Kaseya VSA?
The network monitoring module today is not the best one. If it can improve, it would be better.
What is your primary use case for Kaseya VSA?
We are a reseller. I am conducting some research since we are a vendor for the Kaseya solution.
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
Sage UK, MSP, CodeBlue Ltd, Connect Work Place Solutions, All Covered, 501cTech, Chairo Christian School, Green Duck
Find out what your peers are saying about Automox vs. Kaseya VSA and other solutions. Updated: March 2025.
846,617 professionals have used our research since 2012.