Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Octopus Deploy
Octopus Deploy

202
137
+ 1
106
Salt
Salt

294
206
+ 1
136
Add tool

Octopus Deploy vs Salt: What are the differences?

Octopus Deploy: Automated deployment for .NET. Octopus works with your build server to enable reliable, secure, automated releases of ASP.NET applications and Windows Services into test, staging and production environments, whether they are in the cloud or on-premises; Salt: Fast, scalable and flexible software for data center automation. Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more..

Octopus Deploy belongs to "Deployment as a Service" category of the tech stack, while Salt can be primarily classified under "Server Configuration and Automation".

Some of the features offered by Octopus Deploy are:

  • Deploy on-premises or to the cloud, securely
  • Built for .NET developers
  • Configuration and scripting

On the other hand, Salt provides the following key features:

  • Remote execution is the core function of Salt. Running pre-defined or arbitrary commands on remote hosts.
  • Salt modules are the core of remote execution. They provide functionality such as installing packages, restarting a service, running a remote command, transferring files, and infinitely more
  • Building on the remote execution core is a robust and flexible configuration management framework. Execution happens on the minions allowing effortless, simultaneous configuration of tens of thousands of hosts.

"Powerful" is the primary reason why developers consider Octopus Deploy over the competitors, whereas "Flexible" was stated as the key factor in picking Salt.

Salt is an open source tool with 10.1K GitHub stars and 4.59K GitHub forks. Here's a link to Salt's open source repository on GitHub.

Lyft, LinkedIn, and Hulu are some of the popular companies that use Salt, whereas Octopus Deploy is used by Starbucks, Olo, and Huddle. Salt has a broader approval, being mentioned in 110 company stacks & 20 developers stacks; compared to Octopus Deploy, which is listed in 47 company stacks and 15 developer stacks.

- No public GitHub repository available -

What is Octopus Deploy?

Octopus Deploy helps teams to manage releases, automate deployments, and operate applications with automated runbooks. It's free for small teams.

What is Salt?

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Octopus Deploy?
Why do developers choose Salt?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Octopus Deploy?
    What companies use Salt?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Octopus Deploy?
    What tools integrate with Salt?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Octopus Deploy and Salt?
    Jenkins
    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
    Ansible
    Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
    TeamCity
    TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
    Chef
    Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.
    Bamboo
    Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
    See all alternatives
    Decisions about Octopus Deploy and Salt
    StackShare Editors
    StackShare Editors
    Ansible
    Ansible
    Puppet Labs
    Puppet Labs
    Salt
    Salt

    By 2014, the DevOps team at Lyft decided to port their infrastructure code from Puppet to Salt. At that point, the Puppet code based included around "10,000 lines of spaghetti-code,” which was unfamiliar and challenging to the relatively new members of the DevOps team.

    “The DevOps team felt that the Puppet infrastructure was too difficult to pick up quickly and would be impossible to introduce to [their] developers as the tool they’d use to manage their own services.”

    To determine a path forward, the team assessed both Ansible and Salt, exploring four key areas: simplicity/ease of use, maturity, performance, and community.

    They found that “Salt’s execution and state module support is more mature than Ansible’s, overall,” and that “Salt was faster than Ansible for state/playbook runs.” And while both have high levels of community support, Salt exceeded expectations in terms of friendless and responsiveness to opened issues.

    See more
    Interest over time
    Reviews of Octopus Deploy and Salt
    Review ofSaltSalt

    For automating deployment or system admin tasks, Shell/Perl are more than enough. Specially Perl one liners, that I use heavily, even to make changes in xml files. But quite often the need is to just check the state of system and run scripts without fear. Thats where I actually needed some scripting language with "state mechanism" associated with it. Salt provided me above similar kind of experience. I tested salt first on a small scenario. Installation of 60 RPMS on a machine. I was pleased that I could achieve that in around 25 lines of code using salt. And eventually I was also able to keep data and code separate. This was another plus point. henceforth I was able to use salt to deploy a large potion Datacenter (apps deployment). I am still working towards orchestration and finding it quite promising. The use of pure python whenever needed to deal with more complex scenario is awesome.

    Review ofOctopus DeployOctopus Deploy

    Using this in an environment with about 10 separate development teams. All the teams love this product and how easy it is to get started. It's very well put together, elegant, simple UI that is powerful to use, easy to understand and follow. I HIGHLY recommend this product to any shop.

    It says it's for .NET and it's geared for that. But you could use it for just about any type of deployment given it's capabilities to deploy via FTP.

    How developers use Octopus Deploy and Salt
    Avatar of David Flynn
    David Flynn uses Octopus DeployOctopus Deploy

    This is our CD platform. We use TFS for gated-checks and release builds. A release build packages all our components, pushes these packages to Octopus and triggers a release into our Development environment. A suite of integration tests are run and finally if all is successful the team gets a notification on Slack that a new release is available. This can then get promoted through all our non-production environments, Finally, we use offline deployments as we are not yet allowed to promote all the way to production from Octopus. Offline deployments are great as they allow us to retain our tried and tested deployment process but instead, humans become the tentacles when deploying in prod and pre-prod.

    Avatar of Refractal
    Refractal uses SaltSalt

    When it comes to provisioning tens to hundreds of servers, you need a tool that can handle the load, as well as being extremely customisable. Fortunately, Salt has held that gauntlet for us consistently through any kind of issue you can throw at it.

    Avatar of FAELIX
    FAELIX uses SaltSalt

    We've built something using SaltStack and Debian Linux to help us deploy and administer at scale the servers we provide for our part- and fully-managed hosting customers.

    Avatar of Runbook
    Runbook uses SaltSalt

    Everything is deployed via Salt. From configurations to Docker container builds.

    Avatar of Aspire
    Aspire uses SaltSalt

    Simple configuration of vagrant for development environments.

    Avatar of SAP Hybris
    SAP Hybris uses SaltSalt

    configuration manager and orchestrator for deployment

    Avatar of Valery Sntx
    Valery Sntx uses Octopus DeployOctopus Deploy

    Continious Deployment

    Avatar of One Legal
    One Legal uses Octopus DeployOctopus Deploy

    Deployment tool.

    How much does Octopus Deploy cost?
    How much does Salt cost?
    Pricing unavailable
    News about Octopus Deploy
    More news
    News about Salt
    More news