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

Automox vs Ivanti Neurons Patch for Intune 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
13th
Average Rating
9.0
Reviews Sentiment
2.4
Number of Reviews
11
Ranking in other categories
Vulnerability Management (29th), Endpoint Protection Platform (EPP) (37th), Enterprise Mobility Management (EMM) (11th)
Ivanti Neurons Patch for In...
Ranking in Patch Management
17th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the Patch Management category, the mindshare of Automox is 2.9%, down from 3.9% compared to the previous year. The mindshare of Ivanti Neurons Patch for Intune is 1.6%, down from 2.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Patch Management Market Share Distribution
ProductMarket Share (%)
Automox2.9%
Ivanti Neurons Patch for Intune1.6%
Other95.5%
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.
DddGgggg - PeerSpot reviewer
Allows us to set maintenance windows and deliver patches
We can set a maintenance window and push the patch. I prefer writing scripts, doing software deployment, pushing it, and distributing applications in servers for the corner of the whole location. We download patches from Ivanti, and it collaborates with more than 700 products. For third-party applications, we download the patches, set a role in our environment, and push it using the maintenance window time and activation date. For software deployment, we receive the service request to install and prepare scripts and then push it in many locations according and relevant to the service request for each location. The group or collection devices are affected by the policy.

Quotes from Members

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

Pros

"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."
"It's easy to deploy agents to endpoints."
"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."
"Its flexibility is most valuable."
"It's super easy to use and we haven't found anything easier."
"The fact that it's just one product that can patch multiple operating systems is really great."
"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 biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"The solution is a good product and I have heard that the interface is more friendly than that of Windows."
"We use the solution for security patching of Windows devices."
"We can set a maintenance window and push the patch."
"The technical support from Ivanti is good."
"I like the product's Peer to Peer patching feature."
"Ivanti Patch's most valuable features are the patch module and the package distribution."
"The most valuable features are device management and support for upgrading applications."
"I have found the interface and ease of use valuable features. Additionally, it is very easy to patch VMs and other systems, such a Linux. We are able to do patches even without the internet manually."
 

Cons

"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."
"They need to improve the automation features."
"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. \"
"The product's support and configuration need to improve. It needs to be more scalable."
"I tried to be a partner of Ivanti and, from this vantage point, the quotes are, perhaps, a bit high."
"There are times when there is an update that causes some issues. These issues should be sorted out before the release."
"I would like to have better support for the application."
"Customers sometimes ask about non-existent features, and we pass these requests on to Ivanti."
"It's a difficult configuration because you need to install many servers in a location, and you have to install the primary server in the main location."
"Ivanti Patch could be improved with better integration with other cloud solutions."
"In terms of improvement, I would recommend better documentation. During the time I used it, there were issues with up-to-date patching, and the documentation around those specific errors was quite confusing."
 

Pricing and Cost Advice

"The product is a great value."
"We are on the premium licensing, which is the one that has the API capability that we use."
"Its licensing for a year was nine grand. There was no additional fee."
"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."
"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."
"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."
"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."
"For the one that works with SCCM, it is relatively inexpensive at $8 USD per node, yearly. The standalone product has two versions; the one that patches servers is about $45 USD annually and the version that patches workstations is about half that price at $22 USD."
"The license can get expensive if you have a lot of nodes."
"The solution is affordable."
"The solution is expensive compared to other products."
"While the price is a bit high, it may be equitable with the features one gets with the product, such as that involving the interface."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
11%
Government
9%
Financial Services Firm
7%
Manufacturing Company
7%
Computer Software Company
18%
Government
9%
Manufacturing Company
8%
Non Profit
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise3
Large Enterprise1
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise4
Large Enterprise5
 

Questions from the Community

What needs improvement with Automox?
I wouldn't be able to tell you how Automox can be improved; it seems to work very nicely already.
What is your primary use case for Automox?
We use Automox to maintain the software on all our computers. We were using Qualys before and we're still using it, but we found Qualys to be a little bit lacking since it wasn't really eliminating...
What advice do you have for others considering Automox?
Since switching over from Qualys, we have seen no positive impacts for our organization other than being able to update the applications on an endpoint. We haven't used Automox's reporting capabili...
What do you like most about Ivanti Patch for Windows?
We use the solution for security patching of Windows devices.
What needs improvement with Ivanti Patch for Windows?
In terms of improvement, I would recommend better documentation. During the time I used it, there were issues with up-to-date patching, and the documentation around those specific errors was quite ...
What advice do you have for others considering Ivanti Patch for Windows?
The only downside I found regarding technical support was the time zone difference. Since we are two hours behind, we occasionally had to wait until the next morning for assistance. I would rate th...
 

Also Known As

No data available
Ivanti Patch for Windows, Patch for Windows, Shavlik Patch for Windows
 

Overview

 

Sample Customers

Information Not Available
Presbyterian Church
Find out what your peers are saying about Automox vs. Ivanti Neurons Patch for Intune and other solutions. Updated: September 2025.
868,787 professionals have used our research since 2012.