Automox is an endpoint management platform built for the era of autonomous operations. It provides a cloud-native foundation that unifies automation, speed, visibility, and trust.
$1
per month per endpoint
Ansible
Score 9.2 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
$5,000
per year
Pricing
Automox
Red Hat Ansible Automation Platform
Editions & Modules
No answers on this topic
Basic Tower
5,000
per year
Enterprise Tower
10,000
per year
Premium Tower
14,000
per year
Offerings
Pricing Offerings
Automox
Ansible
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Automox can patch macOS, Windows, and Linux endpoints with PatchOS, an offering at $1 per endpoint/ month with an annual commitment.
The Automate Essentials or Automate Enterprise packages are for scaling IT automation, endpoint configuration, and software updates.
Modules are available with Automox Assist, a one-on-one remote endpoint control and assistance for helpdesk technicians.
It's less overhead compared to running Puppet and Ansible awx. It also provides more visibility as those tools are primarily Configuration Management, which can handle patching but not patching specifically. Reporting is something you'd have to configure yourself. Automox wins …
I was able to update browsera like edge and chrome which have updates every few days, automatically. No more emails to ask people to update edge or chrome. Display drivers and dell drivers are not visible for users, having Automox update them make it much easier for users as not all of the users are technical.
Red Hat Ansible automates server management, configuration updates, and deployments across our server infrastructure, keeping everything consistent, reducing human error, and saving time. Also provides detailed reports on what is done and uses role-based access controls to keep systems secure by controlling who can make changes.
It reduces custom scripting efforts because everything can be scripted in simple, human-readable YAML playbooks.
Not only servers, but also network devices, VMs, Containers, Kubernetes clusters, etc., can be automated via Ansible, showcasing its extensive list of supported devices.
It is agentless, which makes it lightweight and allows for easy integration into CI/CD and GitOps pipelines.
Many Tier-1 telcos use Ansible for Day 0/1/2 automation of RAN, transport, and core infrastructure (e.g., network function lifecycle management, NE configuration push, patching VNFs).
Server patching orchestration. There is no way to patch and reboot systems in order of importance, such as database servers before application servers.
Worklets for patching .net core and similar.
Worklets for removing unwanted Java installs or other unwanted software.
Integration with Tenable Vulnerability Management.
AI script development should be included at no additional cost; GPT or Gemini can be used instead for free and pasted into Automox. Why charge when others are free?
Official worklets are slow to be added or updated.
I can't think of any right now because I've heard about the Lightspeed and I'm really excited about that. Ansible has been really solid for us. We haven't had any issues. Maybe the upgrade process, but other than that, as coming from a user, it's awesome.
This is a software that just works. Once configured its a set and forget kind of tool that keeps things up to date and alerts me if something is wrong. I was able to work through an expansion project to deploy an additional 500 devices in almost no time and create a robust self-patching environment.
Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.
It's great at what it does. We're able to veiw endpoints that are online in real time, and run scans on them to ensure they're still compliant. The software itself is very easy to use and set up on end points, with the main admin portal having a clean and very easy to understand set up
It's overall pretty easy to use foe all the applications I've mentioned before: configuring hosts, installing packages through tools like apt, applying yaml, making changes across wide groups of hosts, etc. Its not a 10 because of the inconveinience of the yaml setup, and the time to write is not worth it for something applied one time to only a few hosts
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
I did not need to reach out to support often but when I did the answers were relatively correct and they were answered quickly. The only thing I might "ding" their support on was their lack of understanding of OS's different from Windows and especially Linux. Other than that I was satisfied
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
Implementing Automox successfully starts with a clear strategy for organizing and grouping devices based on operating systems, environments, or business criticality. This ensures that patching and configuration policies can be applied with precision. A phased rollout approach is essential—beginning with a pilot group allows teams to test patching schedules, reboot behaviors, and custom Worklets before scaling across the organization. Leveraging Worklets from the start can significantly boost automation by enforcing security baselines and performing routine system tasks. Integration with existing SOC tools, such as SIEMs, enhances visibility and response time by correlating patch compliance with threat intelligence. Additionally, aligning patching schedules with operational downtimes minimizes disruptions, and consistent monitoring and reporting helps maintain compliance and prepare for audits. Overall, Automox offers a streamlined and effective solution, but its true value is unlocked through thoughtful planning, testing, and integration with existing IT and security workflows.
We felt that Automox provided us with the functionality our MSP offered, including OS and device patching, as well as remote control capabilities, but in a better and more manageable way. We also felt the usability of the tool gave us the ability to be effective in our way of working, as well as integrating with Rapid7 was a massive benefit for us.
AAP compares favorably with Terraform and Power Automate. I don't have much experience with Terraform, but I find AAP and Ansible easier to use as well as having more capabilities. Power Platform is also an excellent automation tool that is user friendly but I feel that Ansible has more compatibility with a variety of technologies.
Being a start up, we have pivoted our strategies a number of times. The pay as you go model has worked very well for us, and has prevented us from overprovisioning
The time saved pulling reports to provide to auditors has been well worth our small spend on the solution
We have no need to maintain a scanning tool or invest in hardware thanks to the SaaS nature of Automox
POSITIVE: currently used by the IT department and some others, but we want others to use it.
NEGATIVE: We need less technical output for the non-technical. It should be controllable or a setting within playbooks. We also need more graphical responses (non-technical).
POSITIVE: Always being updated and expanded (CaC, EDA, Policy as Code, execution environments, AI, etc..)
