We performed a comparison between NinjaOne and Automox based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison results: Based on the parameters we compared, Automox comes out ahead of NinjaOne. While both solutions offer valuable patch management and monitoring, NinjaOne’s inflexible backup features, the way it handles reports, as well as its high price, leave room for improvement.
"It's easy to deploy agents to endpoints."
"Its flexibility is most valuable."
"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 biggest improvement to our organization involves the reduction in its man hours... We've probably saved hundreds of hours."
"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."
"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 best feature of NinjaOne is the SLA system. Every IT person can check their performance, how long it takes to resolve an issue, and how many SLAs are breached."
"NinjaOne's best feature is its monitoring."
"We can use it for remote monitoring, and it also works great as a troubleshooting tool. We are able to open up a command line or a PowerShell session remotely without having to disrupt the user. They have a limited network device monitoring capability, but for workstation servers, we have the event logs. We can do performance monitoring, system changes, software deployment, and patch management. We can also push scripts. It has a very simple web interface. There are no additional things to do there. Security is also pretty good. It does the same things that the other competitor's tools do. One of the advantages of Ninja is that they have a more capable mobile app, which allows you to see the alerts immediately. I get alerted to major critical issues."
"The most important aspect of this tool is the security it provides our company."
"The tool's most valuable feature is third-party application updates."
"The solution's most valuable feature is related to its remote access...I know that NinjaOne's technical support is good."
"It helps us to be able to have visibility into the overall performance of the servers, laptops, and desktops that we are managing currently."
"Good at managing updates and for remote support."
"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."
"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."
"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."
"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."
"It should have integrated workstation access. So, there should be a remote desktop feature."
"I want NinjaOne to improve the reports."
"The ticketing system in NinjaOne is not the best."
"NinjaOne's reporting module is cumbersome."
"NinjaOne's pricing and user interface needs improvement."
"The remote connectivity could be better. It works most of the time, but sometimes, there are issues."
"The solution could improve by optimizing the internet connection being used."
"NinjaOne's dashboard could be easier to use."
"The graphical user interface could be improved."
Automox is ranked 11th in Patch Management with 10 reviews while NinjaOne is ranked 5th in Patch Management with 15 reviews. Automox is rated 8.8, while NinjaOne is rated 8.0. The top reviewer of Automox writes "Monitors our devices irrespective of the location and the environment, allows us to exempt certain machines from certain patches, and has perfect patch management abilities". On the other hand, the top reviewer of NinjaOne writes "A tool that helps with a lot of configurations and creates automation processes that work perfectly". Automox is most compared with Microsoft Intune, BigFix, Microsoft Configuration Manager, Tanium and Qualys VMDR, whereas NinjaOne is most compared with Atera, N-able N-central, Microsoft Configuration Manager, ConnectWise Automate and ServiceNow. See our Automox vs. NinjaOne report.
See our list of best Patch Management vendors.
We monitor all Patch Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.