GetWhy vs. Salt Project

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
GetWhy
Score 0.0 out of 10
N/A
GetWhy (formerly Sonar) is a platform that helps solve three challenges in video based research: 1) how to write the questions that will get needed answers, 2) how to process, analyse and organise data to be able to create insights, 3) how to store, search and share insights across the organisation.N/A
Salt
Score 7.8 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
GetWhySalt Project
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
GetWhySalt
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details——
More Pricing Information
Community Pulse
GetWhySalt Project
Top Pros

No answers on this topic

Top Cons

No answers on this topic

Best Alternatives
GetWhySalt Project
Small Businesses
Jotform
Jotform
Score 8.7 out of 10
HashiCorp Vagrant
HashiCorp Vagrant
Score 9.9 out of 10
Medium-sized Companies
Jotform
Jotform
Score 8.7 out of 10
Ansible
Ansible
Score 8.9 out of 10
Enterprises
Qualtrics
Qualtrics
Score 7.4 out of 10
Ansible
Ansible
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GetWhySalt Project
Likelihood to Recommend
-
(0 ratings)
8.0
(10 ratings)
Support Rating
-
(0 ratings)
8.2
(1 ratings)
User Testimonials
GetWhySalt Project
Likelihood to Recommend
GetWhy
No answers on this topic
Open Source
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.
Read full review
Pros
GetWhy
No answers on this topic
Open Source
  • 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.
Read full review
Cons
GetWhy
No answers on this topic
Open Source
  • Managing network hardware should be more native and easy
  • SaltStack should buffer jobs and, when a client returns, make sure it is executed proberly
  • SaltStack should provide basic pillar and states structures to help get newbies started
Read full review
Support Rating
GetWhy
No answers on this topic
Open Source
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.
Read full review
Alternatives Considered
GetWhy
No answers on this topic
Open Source
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.
Read full review
Return on Investment
GetWhy
No answers on this topic
Open Source
  • 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.
Read full review
ScreenShots