SaltStack Previous Solutions
Prior to this, we used Puppet/SaltStack open-source. The Puppet solution had scale issues, and SaltStack Open Source didn't have the SecOps product
View full review »JM
Jeremy Mcmillan
Systems Administrator, Deployment Specialist Consultant at a tech vendor with 1,001-5,000 employees
I have used Chef. Chef is harder to teach, so it is more difficult to build an internal community around the toolset.
View full review »This organization I work for used Altiris before, but we switched to Salt to scale into AWS.
View full review »Buyer's Guide
SaltStack
March 2024
Learn what your peers think about SaltStack. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,386 professionals have used our research since 2012.
I am not aware of any previous solutions.
View full review »We did not have a previous solution as we are new to using DevOps management tools, but we researched others before we decided on SaltStack as our tool of choice.
View full review »I did not previously use a different solution.
View full review »I was using more of a Frankenstein automation solution previously, and the reason for switching was the capability of SaltStack, performance, and ramp up time (ease of use).
View full review »I previously used Puppet. I switched because our shop here likes using Python solutions over Ruby ones.
View full review »I did not previously use a different solution.
View full review »We were not using any other solution for our configuration management.
View full review »SaltStack was my first choice because it is open source and was reviewed extensively as a good choice because of the low learning curve.
View full review »I previously used multiple solutions combined; harder to manage. Salt is easy to use and manage.
View full review »I've used Puppet at a previous job. Salt is the tool that was in place at my current job.
View full review »We evaluated Chef, CF Engine, and Puppet and we ultimately decided on SaltStack because:
- It is written in Python: Introspecting the code base, committing fixes and improving on the tools were easy for us to do.
- The amount of tools already baked in the product and the extensive list of formulas made available by the community.
I did not previously use a different solution.
View full review »We previously used CFEngine 2 and Chef; both solutions have a steep learning curve that requires a ton of domain-specific knowledge. Salt is configured from the ground up in YAML files and Python, so there's less domain-specific knowledge required and no hidden configuration files.
View full review »This is the first solution I have used.
View full review »We were previously using SCCM and SCOM. We have brought in SaltStack and it is slowly taking over those two spaces. SaltStack is a great orchestration tool, but not intended to be used for monitoring. We are looking at switching over to Zenoss for our monitoring solution.
View full review »I did not previously use a different solution.
View full review »This was our first foray into the configuration management space. Previously, it was a bunch of PowerShell scripts.
View full review »We previously used Puppet, which was not suited for my current workload. We chose SaltStack because Ruby wasn't the language used by my team and we needed a master-client solution as opposed to a master-less one.
View full review »I previously used Puppet and found SaltStack to be better in terms of configuration. It’s written in Python, which means easy integration, and the structure is YAML, which is very simple.
View full review »Buyer's Guide
SaltStack
March 2024
Learn what your peers think about SaltStack. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,386 professionals have used our research since 2012.