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

Automox vs Ivanti Patch for Endpoint Manager 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
19th
Average Rating
9.0
Reviews Sentiment
2.4
Number of Reviews
11
Ranking in other categories
Vulnerability Management (50th), Endpoint Protection Platform (EPP) (58th), Enterprise Mobility Management (EMM) (20th)
Ivanti Patch for Endpoint M...
Ranking in Patch Management
15th
Average Rating
7.6
Reviews Sentiment
7.5
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2025, in the Patch Management category, the mindshare of Automox is 3.1%, down from 3.9% compared to the previous year. The mindshare of Ivanti Patch for Endpoint Manager is 2.2%, up from 1.2% 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.
PraveenRajan - PeerSpot reviewer
Smoothly handles software patching and scheduling, enabling monthly patch distribution across multiple projects
We face some challenges, particularly with non-domain-joined macOS devices. Patching, updating, and syncing with the server can be tricky for them. So, the major challenges are macOS updates, patching, and backups. And for drawbacks, I wish Patch management was cloud-based instead of hosted on our own server. If Ivanti Patch had a cloud-based option instead of requiring an on-premises server and software. Hosting it in the cloud would simplify management, eliminating dependence on VPNs or other connectivity issues. Similar to Microsoft's EMS licensing, offering a cloud-based solution like Azure Active Directory or Endpoint Management Suite (EMS) would be ideal. EMS allows us to manage policies, batching, and software distribution entirely through the cloud, minimizing server downloads. If Ivanti considered a cloud-based approach, it would be hugely beneficial in today's hybrid work environment, where employees use desktops, laptops, and various locations. It's not just about patching office PCs anymore; mobile workers and backups need seamless access as well. Cloud-based patching would be much easier in a hybrid environment. Imagine updates coming directly from the cloud instead of relying on individual VPN connections. It would streamline the entire process.

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 super easy to use and we haven't found anything easier."
"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."
"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."
"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."
"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."
"The biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"When it comes to Ivanti Patch for endpoints, I find peer-to-peer patching valuable. Having a peer-to-peer patching capability is highly beneficial for us."
"It's been doing a lot for us, especially with third-party software patching and scheduling. We create multiple projects for monthly patch distribution and manage it all well."
"The product is easy to use, easy to implement, and easy to manage."
"Clear visibility regarding the status of the endpoint."
 

Cons

"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."
"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."
"It should have integrated workstation access. So, there should be a remote desktop feature."
"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 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."
"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."
"The stability has come a long way from what it was like when it started and now it's really good."
"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 would be great to have an easier way to patch Linux machines within the product."
"The UI must be more user-friendly."
"Inability to configure a rule-based management."
"The major challenges are macOS updates, patching, and backups. And for drawbacks, I wish Patch management was cloud-based instead of hosted on our own server."
 

Pricing and Cost Advice

"We are on the premium licensing, which is the one that has the API capability that we use."
"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."
"The product is a great value."
"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.""
"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."
"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."
"Its licensing for a year was nine grand. There was no additional fee."
"In terms of pricing, it is on the expensive side."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Government
8%
Manufacturing Company
8%
Financial Services Firm
7%
Government
11%
Computer Software Company
11%
Manufacturing Company
8%
University
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about Ivanti Patch for Endpoints?
It's been doing a lot for us, especially with third-party software patching and scheduling. We create multiple projects for monthly patch distribution and manage it all well.
What is your primary use case for Ivanti Patch for Endpoints?
We use the solution to patch Windows and Linux machines. We download the patches and implement them. We get vulnerability reports after patching.
 

Also Known As

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

Overview

 

Sample Customers

Information Not Available
InfoPro Digital, Cypress-Fairbanks Independent School District
Find out what your peers are saying about Automox vs. Ivanti Patch for Endpoint Manager and other solutions. Updated: July 2025.
865,384 professionals have used our research since 2012.