Salt Project vs. Visual SourceSafe (Discontinued)

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
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
Visual SourceSafe (Discontinued)
Score 1.0 out of 10
N/A
Visual SourceSafe is a discontinued source control software offering, from Microsoft.N/A
Pricing
Salt ProjectVisual SourceSafe (Discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
SaltVisual SourceSafe (Discontinued)
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
Best Alternatives
Salt ProjectVisual SourceSafe (Discontinued)
Small Businesses
HashiCorp Terraform
HashiCorp Terraform
Score 8.6 out of 10
Salt
Salt
Score 7.8 out of 10
Medium-sized Companies
Ansible
Ansible
Score 8.9 out of 10
Salt
Salt
Score 7.8 out of 10
Enterprises
Ansible
Ansible
Score 8.9 out of 10
Perforce Helix Core
Perforce Helix Core
Score 6.3 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Salt ProjectVisual SourceSafe (Discontinued)
Likelihood to Recommend
8.0
(10 ratings)
1.0
(4 ratings)
Usability
-
(0 ratings)
3.8
(2 ratings)
Support Rating
8.2
(1 ratings)
4.2
(2 ratings)
User Testimonials
Salt ProjectVisual SourceSafe (Discontinued)
Likelihood to Recommend
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
Microsoft
I would not recommend Visual SourceSafe to anyone out there as there are so many better, more modern solutions that do what it does and much more. Visual SourceSafe should be retired in most cases.
Read full review
Pros
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
Microsoft
  • At this point in its lifecycle there are not many things VSS does well
  • Its main strength would be its ability to be self contained on a local drive
  • It is a basic Code repository
Read full review
Cons
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
Microsoft
  • The system stability could be improved. Often we get file corrupted errors.
  • The User Interface is not modern and not user-friendly.
  • Concurrent check-outs could be added, allowing more people to work on the same file at the same time.
  • Add conflict resolution, files comparison, blame file, features that any modern source control program should have.
Read full review
Usability
Open Source
No answers on this topic
Microsoft
The current status of Visual SourceSafe is not usable. There are many things that are just so out of the date that it should be retired and not looked at any longer. If you have an existing application that is stored in it, I'd consider migrating it to a modern tool.
Read full review
Support Rating
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
Microsoft
It's a Microsoft product so the customer support is great. The program has been around a long time so there are plenty of places on line to get assistance. Also almost any development shop you go to will have at least one developer who has used this product extensively in their career.
Read full review
Alternatives Considered
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
Microsoft
Read full review
Return on Investment
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
Microsoft
  • When we started using it, it allowed us to do source code versioning and store the code in a centralized location and not locally.
  • We are using it for very few projects with few developers that still maintain those applications and do not have time to merge the source code to Git.
Read full review
ScreenShots