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
 

Categories and Ranking

Automox
Ranking in Patch Management
14th
Average Rating
8.8
Number of Reviews
10
Ranking in other categories
Vulnerability Management (46th), Endpoint Protection Platform (EPP) (55th), Enterprise Mobility Management (EMM) (18th)
Kaseya VSA
Ranking in Patch Management
5th
Average Rating
7.8
Number of Reviews
31
Ranking in other categories
Remote Monitoring and Management (RMM) (2nd)
 

Mindshare comparison

As of November 2024, in the Patch Management category, the mindshare of Automox is 4.0%, up from 3.4% compared to the previous year. The mindshare of Kaseya VSA is 4.5%, down from 5.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Patch Management
 

Featured Reviews

Jack Leung - PeerSpot reviewer
Mar 24, 2023
Easy to use and deploy agents but needs more stability
We primarily use it on the endpoint management and on the server It is very simple and straightforward to use.  Technical support is helpful. They can scale well. It's easy to deploy agents to endpoints.  They need to improve the automation features.  It could be more stable.  I've been using…
Ben Blissett - PeerSpot reviewer
Jan 4, 2024
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

"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."
"It's easy to deploy agents to endpoints."
"The fact that it's just one product that can patch multiple operating systems is really great."
"It's super easy to use and we haven't found anything easier."
"Coming from prior solutions that were a lot more effort, Automox's patch management abilities are transformational. When I took over patching at my company, they were using on-premise architecture to patch. As the workforce shifted from being in the office into their home offices, I was able to lift and shift with no effort other than deploying the new agent out into the environment."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"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 flexibility in creating tools to make changes on remote machines is most valuable to me. The reporting feature is also fantastic because on any given day I can bring up a list of machines that don't have patches, for example. Or I can bring up a list of machines that are in my environment on a certain day. The solution helps me with not only my own role, and what I look for internally myself, but it also helps during audits. I can go in and look at the number of machines in there, and their owners and timelines. It certainly helps tell a story for anything that IT requires."
"I like the remote control, audit, inventory, patch management, software management, and monitoring features."
"The training that we received was quite good."
"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 solution was scalable."
"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."
"The most valuable piece of the puzzle for me is what they call Live Connect. It is the piece that allows you to support an end-user without having to take the keyboard and mouse."
"Kaseya VSA's best features are auditing and reporting."
"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."
 

Cons

"The stability has come a long way from what it was like when it started and now it's really good."
"They need to improve the automation features."
"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."
"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."
"It should have integrated workstation access. So, there should be a remote desktop feature."
"The biggest area they need to fix, without a doubt, is the ability to copy and sync profiles and worklets between all of the organizations you manage, and the ability to have top-level user access control across all of the companies that you manage."
"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."
"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."
"I believe we should include a VSA license to provide complete endpoint management."
"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."
"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."
"Our main concern is related to security. Kaseya had a ransomware attack a few months ago, and it was a big concern for us because Kaseya was the main RMM tool that we were using. We faced a lot of difficulties accessing our users and systems. So, security is our main concern."
"One area that could be improved is the documentation, which often contains errors that prevent you from following along, especially during migrations."
"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."
"The UI could be streamlined. The menu has 18 options, but we only use three. It has a lot of redundant stuff. Software management, software deployment, patch management, etc., all do the same thing, but they're different programs and licenses."
"There is room for improvement in the integrated mobile device management, MDM."
 

Pricing and Cost Advice

"We are on the premium licensing, which is the one that has the API capability that we use."
"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."
"The product is a great value."
"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."
"The cost is very reasonable compared to the competition."
"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.""
"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."
"There are no additional costs in addition to the extended licensing fees with Automox. You get your support and your per endpoint license with what you purchased."
"Licensing is available on a yearly basis and is priced per node."
"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 is, in my opinion, competitive in the market. It is determined by the number of users and licenses needed. Depending on the license count of users, the price ranges from $10 to $80 USD."
"The solution is robust and the price is good for the features that are provided."
"The dollar exchange rate in Brazil is very high, so the price should be better for our country."
"I think it costs more than ManageEngine."
"We use annual licensing, but we also have a special agreement."
"Kaseya's come down in pricing when I compare it to TeamViewer or other cheaper RMMs like LogMeIn."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
814,649 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Manufacturing Company
8%
Financial Services Firm
8%
Government
7%
Computer Software Company
16%
Non Profit
6%
Manufacturing Company
6%
Construction Company
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?
One area that could be improved is the documentation, which often contains errors that prevent you from following along, especially during migrations.
What is your primary use case for Kaseya VSA?
We use the solution as a remote control tool to help clients.
 

Comparisons

 

Learn More

 

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: October 2024.
814,649 professionals have used our research since 2012.