Automox is an endpoint management solution used to keep desktops, laptops, and servers updated and ready for users anywhere in the world. Using automation, IT can fix critical vulnerabilities and boost user productivity.
$1
per month per endpoint
Salt
Score 6.7 out of 10
N/A
Built on Python, Salt is an event-driven automation tool and framework to deploy, configure, and manage complex IT systems. Salt is used to automate common infrastructure administration tasks and ensure that all the components of infrastructure are operating in a consistent desired state.
N/A
Pricing
Automox
Salt Project
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Automox
Salt
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.
The reason I would score it a nine is because of the inability to “run as.” Since it only runs as a system, this makes some tasks impossible. It would be beneficial to have an encrypted set of credentials in the UI that we can use to “run as,” and also the ability to run as the current user with elevated permissions would be nice. In terms of patching, Automox does a good job, and being able to use Automox to run PowerShell on a computer without needing to open up ports for WinRM is a great feature.
SaltStack is a very well architected toolset and framework for reliably managing distributed systems' complexity at varied scale. If the diversity of kind or number of assets is low, or the dependencies are bounded and simple, it might be overkill. Realization that you need SaltStack might come in the form of other tools, scripts, or jobs whose code has become difficult, unreliable, or unmaintainable. Rather than a native from-scratch SaltStack design, be aware that SaltStack can be added on to tools like Docker or Chef and optionally factor those tools out or other tools into the mix.
Targeting is easy and yet extremely granular - I can target machines by name, role, operating system, init system, distro, regex, or any combination of the above.
Abstraction of OS, package manager and package details is far advanced beyond any other CRM I have seen. The ability to set one configuration for a package across multiple distros, and have it apply correctly no matter the distrospecific naming convention or package installation procedure, is amazing.
Abstraction of environments is similarly valuable - I can set a firewall rule to allow ssh from "management", and have that be defined as a specific IP range per dev, test, and prod.
I would like to see more detailed error messages when a patch fails. Perhaps at which step it failed at, downloading, installing, etc.
It would be helpful if we could see what stage of installing or downloading a patch is at through a percentage or status bar instead of a vague "Installing..." message
It would also be helpful to have a way to kill or end scripts that are stuck instead of waiting 24 hours for them to automatically end. Something like an "End all actions" button for endpoints on our side would be extremely helpful when testing a script that had a bad line or action in it.
Automox has excellent dashboards that help to identify key performance indicators of where your patching program stands, what to prioritize, and what issues you have. Where Automox struggles is easily identifying what issues are preventing successful patching, seeing what manual patches are successfully installing/not installing, and easily remediating issues with installation issues.
In my experience, they were responsive but the fixes were more like bandaids than a fix for the underlying problems which they admitted were on their end.
We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.
Automox is able to scale better than PDQ Deploy. We were happier with the 3rd party software patching since we have a lot of different software we use across departments. PDQ deploy required a lot more manual intervention to stay on top of deployments. Automox just ended up being a timesaver for us in the end.
We moved to SaltStack from Puppet about 3 years ago. Puppet just has too much of a learning curve and we inherited it from an old IT regime. We wanted something we could start fresh with. Our team has never looked back. SaltStack is so much easier for us to use and maintain.
We used to use a different patching solution and since switching to Automox, I have been able to cut the amount of time I spend on vulnerability management by 50% or more. I love how "set it and forget it" some of the policies can be. I love how simple it is to keep an eye on things.
We manage two complex highly available self-healing (all infrastructure and systems) environments using SaltStack. Only one person is needed to run SaltStack. That is a HUGE return on investment.
Building tooling on top of SaltStack has allowed us to share administrative abilities by role - e.g. employee X can deploy software Y. No need to call a sysadmin and etc.
Recovery from problems, or time to stand-up new systems is now counted in minutes (usually under eight) rather than hours. This is a strategic advantage for rolling out new services.
