Automox
Automation and Speed That Patch Our Entire Org Fast
Automox Makes Endpoint Patching Simple with Powerful Built-In Automation
Automation has transformed server patching and reporting and continues to save our team time
What is our primary use case?
My main use case for Automox involves patching Windows and Linux servers, Windows endpoints, and maintaining configurations.
A specific example of how I use Automox for patching and maintaining configurations is that we have monthly schedules to patch all of our servers in multiple phases, and we also have schedules to maintain endpoints that are not on our Active Directory domains.
What is most valuable?
The best features that Automox offers are its automation, as the scheduling is super easy to set up, policies are easy to configure, and the software discoverability.
The automation and scheduling specifically help my team day-to-day because we can push a set of patches reliably, which saves us a lot of time.
Automox has positively impacted my organization through the ability to automate patch schedules and generate reports on it, as well as create worklets to handle any one-off needs.
The automated reports and worklets have made things easier and more efficient for my team, as the reporting has been particularly useful, allowing us to double-check and make sure all the machines are patched and see if there are any recurring issues, while the worklets are also great for remediating something that cannot just be patched.
What needs improvement?
I cannot think of anything specific for how Automox can be improved. An AI worklet builder would be a possibility, but even at that, the worklet catalog is very robust and useful.
For how long have I used the solution?
I have been using Automox for four years.
What do I think about the stability of the solution?
Automox appears to be very stable.
What do I think about the scalability of the solution?
Automox's scalability is excellent, as it scales very well, and it is easy to deploy new agents, while the company makes it easy to buy more licenses.
How are customer service and support?
The customer support has been very great over the time we have used Automox.
Which solution did I use previously and why did I switch?
We did not previously use a different solution.
What was our ROI?
We have not seen any relevant metrics for return on investment, but we have definitely saved time, as instead of patching four evenings a month, we only have to patch two due to the automation and reliability.
What's my experience with pricing, setup cost, and licensing?
Our experience with pricing, setup cost, and licensing was very pleasant.
Which other solutions did I evaluate?
Before choosing Automox, we evaluated SCCM and NinjaOne.
What other advice do I have?
My primary advice to others looking into using Automox would be to double-check compatibility with any endpoint protection you are using. I give this review a rating of 9.
Effortless Agent-Based Patching Across Mac and Windows—Even Off-Network
Centralized patching has streamlined test environments and keeps endpoints consistently updated
What is our primary use case?
My main use case for Automox is helping maintain and manage the test environments I work with, ensuring test machines have the required operating system and security patches, keeping endpoints up to date, and reducing environment-related issues that could affect testing. It is also useful for having better visibility into the configuration and patch status of devices.
In my day-to-day work, I use Automox to check the patch and update status of test machines before I start testing. For example, I can verify whether a device is compliant, identify missing patches, and make sure the environment is up-to-date before executing test cases, which helps reduce issues caused by outdated software or inconsistent test environments.
What is most valuable?
The best features for me are the centralized patch management, clear visibility into device status, and automation. I particularly appreciate being able to quickly check whether a test environment is up-to-date and identify missing patches. Support across Windows, macOS, and Linux from one console is another strong advantage for me.
The feature I rely on the most is centralized patch management, as it gives me a quick overview of the patch status of test machines and helps ensure the environment is up-to-date before I start testing. This is especially useful because it reduces environment-related issues and saves time that would otherwise be spent checking and updating machines manually.
Automox has had a positive impact on my organization by reducing the amount of manual effort needed to keep our test environments patched and consistent. It gives the team better visibility into endpoint status and helps us identify and address outdated software more quickly. From a QA perspective, this means fewer environment-related issues and more reliable testing, allowing us to spend more time focusing on the application itself.
What needs improvement?
I think Automox can be improved by providing more advanced reporting and analytics, with greater customization of dashboards and compliance reports. It would also be helpful to have more granular control over patch scheduling and notifications. From a QA perspective, better visibility into patch history and endpoint changes would make it easier to troubleshoot environment-related issues and track changes over time.
For how long have I used the solution?
I have been working in my current field for about seven years.
What do I think about the scalability of the solution?
Automox scales well for our needs; adding new endpoints is straightforward and the centralized management approach makes it easy to apply consistent policies as the environment grows.
How are customer service and support?
Overall, the customer support has been good; responses are generally timely, and the support team is helpful when troubleshooting issues or clarifying how a feature works. The documentation and knowledge base are also useful for resolving common questions independently, making the support experience reliable, although response times can vary depending on the complexity of the issue.
Which solution did I use previously and why did I switch?
We have not used a different solution.
How was the initial setup?
Overall, the pricing and licensing were straightforward; the setup cost was reasonable compared with the time savings from automated patch management and endpoint maintenance. I would recommend reviewing the licensing tiers carefully to ensure that the cost scales appropriately with the number of endpoints.
What was our ROI?
We have seen a positive return on investment mainly through time savings, as automating patching and routine endpoint maintenance has reduced manual effort by roughly around twenty to thirty percent for these tasks. It also reduced the number of environment-related issues that required manual investigation; although we have not reduced headcount, the team can spend more time on higher-value QA and technical work instead of repetitive endpoint maintenance.
Which other solutions did I evaluate?
We evaluated a few alternatives such as Microsoft Intune, ManageEngine Endpoint Central, and a couple of traditional patch management tools. Automox stood out because of its cloud-based approach, straightforward setup, automation capabilities, and ease of managing patches across different operating systems.
What other advice do I have?
I would rate Automox an eight out of ten overall, as it has made endpoint and patch management much more efficient and provides good visibility into device status. This automation is particularly valuable for keeping test environments consistent, and I would give it a higher rating with more advanced reporting, customization, and granular controls for certain workflows. I would give customer support a seven to eight out of ten. I would recommend Automox to teams looking to simplify endpoint patch management and reduce manual maintenance. Before adopting it, I suggest evaluating your number of endpoints, operating systems, and specific patching requirements, and comparing the licensing costs with the amount of time your team currently spends on manual maintenance.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automox Makes Cross-Platform Patch Management Effortless from One Portal
Automox Worklets and Cross-Platform Patching Made Easy
Other thing which I like about them is their cross platform support like windows MacOS and even Linux which help you to easily deploy their light weight agent and then sync the endpoint on management console which is SaaS based.
Apart from that there are still small hiccups like if there any app which are not supported you would have to spend time with Worklets to write custom scripting.
Helpful Reboot & Status Tracking
Streamlined Patching and Clear Vulnerability Reporting with Automox
Automox comes with wide variety of features like software configuration on multiple machines at the same time along with easy deploymengt of the agents which are light weight agent consuming very low resources and computation.
Automox Streamlines Endpoint Management with Best-in-Class Patch & Vulnerability Control
Automox features best in industry standards with patch and vulnerability management solution along with system state and software configurations. Easy to use along with managing IT resources and failure systems are easy to manage and control from one single centralized locations.
Compliance reporting, its AI usage that even help us to troubleshoot lot of stuff during failure occurrence is an important part of our benefits we use Automox for.