OpenText AccuRev vs. Salt Project

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
OpenText AccuRev
Score 4.3 out of 10
N/A
AccuRev, a software configuration management offering, is now owned and supported by Micro Focus since the December 2013 acquisition, and now by OpenText.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
OpenText AccuRevSalt Project
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
OpenText AccuRevSalt
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeOptionalNo setup fee
Additional Details——
More Pricing Information
Best Alternatives
OpenText AccuRevSalt Project
Small Businesses
Salt
Salt
Score 7.8 out of 10
HashiCorp Vagrant
HashiCorp Vagrant
Score 9.9 out of 10
Medium-sized Companies
Salt
Salt
Score 7.8 out of 10
Ansible
Ansible
Score 8.9 out of 10
Enterprises
Perforce Helix Core
Perforce Helix Core
Score 6.3 out of 10
Ansible
Ansible
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
OpenText AccuRevSalt Project
Likelihood to Recommend
1.0
(4 ratings)
8.0
(10 ratings)
Likelihood to Renew
6.1
(3 ratings)
-
(0 ratings)
Availability
7.0
(1 ratings)
-
(0 ratings)
Support Rating
-
(0 ratings)
8.2
(1 ratings)
User Testimonials
OpenText AccuRevSalt Project
Likelihood to Recommend
OpenText
Very slow and not intuitive; it would be my last choice for version control systems.The UI is a little confusing at times and seems a little outdated. It needs a lot of improvement. It is suited for small projects and fewer number of projects. But if there are huge projects and many projects to be maintained in a portfolio, its a little hard to manage.
Read full review
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
OpenText
  • One place for most recent code with history, avoid any conflict/confusion among other team/members.
  • Stream/Workflow approach to control approval process betwen all the teams, which I couldn't find in other version control tools I worked.
  • Bundle our code in a small group (called, Issues in Accurev) to differentiate between different projects.
Read full review
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
OpenText
  • Ability to zoom in/out for stream-view. We currently have many streams/substreams and unable to view the entire workflow. Zooming in/out would benefit.
  • Being a designer, I use Adobe Flash and SWF files. When updating the SWF files, Accurev does not see these files as being changed and you will be unable to promote. In order to push changes, you must totally rename the SWF file.
Read full review
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
Likelihood to Renew
OpenText
We will renew because it is part of our build process.
Read full review
Open Source
No answers on this topic
Support Rating
OpenText
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
OpenText
In my view, accurev ranks very low compared to other tools I have used. Microsoft TFS is the best in the industry as of today as it's a complete ALM solution. It does code version, bug tracking, user story documentation, and has easy integration with other external tools supporting many languages. So I would definitely recommend TFS to anyone.
Read full review
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
OpenText
  • Better team coordination.
  • Avoid confusion by having one place for all documentation and code.
  • Better project management by having different work streams.
Read full review
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