Get Advice Icon

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

Capistrano
Capistrano

851
467
+ 1
232
Salt
Salt

294
206
+ 1
136
Add tool

Capistrano vs Salt: What are the differences?

Capistrano: A remote server automation and deployment tool written in Ruby. Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows; 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..

Capistrano and Salt belong to "Server Configuration and Automation" category of the tech stack.

Some of the features offered by Capistrano are:

  • Reliably deploy web application to any number of machines simultaneously, in sequence or as a rolling set
  • Automate audits of any number of machines (checking login logs, enumerating uptimes, and/or applying security patches)
  • Script arbitrary workflows over SSH

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.

"Automated deployment with several custom recipes" is the top reason why over 122 developers like Capistrano, while over 41 developers mention "Flexible" as the leading cause for choosing Salt.

Capistrano and Salt are both open source tools. Capistrano with 11.1K GitHub stars and 1.71K forks on GitHub appears to be more popular than Salt with 10.1K GitHub stars and 4.59K GitHub forks.

According to the StackShare community, Capistrano has a broader approval, being mentioned in 293 company stacks & 81 developers stacks; compared to Salt, which is listed in 110 company stacks and 20 developer stacks.

What is Capistrano?

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

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 Capistrano?
Why do developers choose Salt?

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

    Be the first to leave a con
      Be the first to leave a con
      Jobs that mention Capistrano and Salt as a desired skillset
      What companies use Capistrano?
      What companies use Salt?

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

      What tools integrate with Capistrano?
      What tools integrate with Salt?

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

      What are some alternatives to Capistrano and Salt?
      Fabric
      Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.
      Shipit
      Shipit is an automation engine and a deployment tool written for node / iojs. Shipit was built to be a Capistrano alternative for people who don't know ruby, or who experienced some issues with it. If you want to write tasks in JavaScript and enjoy the node ecosystem, Shipit is also for you.
      Docker
      The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
      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.
      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.
      See all alternatives
      Decisions about Capistrano 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
      Kir Shatrov
      Kir Shatrov
      Production Engineer at Shopify · | 13 upvotes · 25K views
      atShopifyShopify
      kubernetes-deploy
      kubernetes-deploy
      Capistrano
      Capistrano
      Heroku
      Heroku
      Shipit
      Shipit
      #PlatformAsAService
      #ApplicationHosting
      #ContainerTools
      #BuildTestDeploy

      Shipit, our deployment tool, is at the heart of Continuous Delivery at Shopify. Shipit is an orchestrator that runs and tracks progress of any deploy script that you provide for a project. It supports deploying to Rubygems, Pip, Heroku and Capistrano out of the box. For us, it's mostly kubernetes-deploy or Capistrano for legacy projects.

      We use a slightly tweaked GitHub flow, with feature development going in branches and the master branch being the source of truth for the state of things in production. When your PR is ready, you add it to the Merge Queue in ShipIt. The idea behind the Merge Queue is to control the rate of code that is being merged to master branch. In the busy hours, we have many developers who want to merge the PRs, but at the same time we don't want to introduce too many changes to the system at the same time. Merge Queue limits deploys to 5-10 commits at a time, which makes it easier to identify issues and roll back in case we notice any unexpected behaviour after the deploy.

      We use a browser extension to make Merge Queue play nicely with the Merge button on GitHub:

      Both Shipit and kubernetes-deploy are open source, and we've heard quite a few success stories from companies who have adopted our flow.

      #BuildTestDeploy #ContainerTools #ApplicationHosting #PlatformAsAService

      See more
      Interest over time
      Reviews of Capistrano 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.

      How developers use Capistrano and Salt
      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 Cyrus Stoller
      Cyrus Stoller uses CapistranoCapistrano

      For deploying to a VPS like DigitalOcean. This pairs nicely with https://github.com/cyrusstoller/gardenbed.

      Avatar of GeniusLink
      GeniusLink uses CapistranoCapistrano

      Deployment automation all of the websites and apps are deployed to linux via capistrano.

      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 Nick De Cooman
      Nick De Cooman uses CapistranoCapistrano

      Before Docker, I used Capistrano to deploy all web projects.

      Avatar of douglasresende
      douglasresende uses CapistranoCapistrano

      I use do make deploy my applications into many servers.

      Avatar of SAP Hybris
      SAP Hybris uses SaltSalt

      configuration manager and orchestrator for deployment

      Avatar of Cyril Duchon-Doris
      Cyril Duchon-Doris uses CapistranoCapistrano

      Deployment to remote AWS auto-scaled infrastructure.

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