Need advice about which tool to choose?Ask the StackShare community!
Deployer vs Octopus Deploy: What are the differences?
Developers describe Deployer as "Deployment Tool for PHP". A deployment tool written in PHP with support for popular frameworks out of the box. On the other hand, Octopus Deploy is detailed as "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.
Deployer belongs to "Continuous Deployment" category of the tech stack, while Octopus Deploy can be primarily classified under "Deployment as a Service".
Some of the features offered by Deployer are:
- Simple setup process and a minimal learning curve
- Ready to use recipes for most frameworks
- Parallel execution without extensions
On the other hand, Octopus Deploy provides the following key features:
- Deploy on-premises or to the cloud, securely
- Built for .NET developers
- Configuration and scripting
"Simply to use" is the top reason why over 7 developers like Deployer, while over 26 developers mention "Powerful" as the leading cause for choosing Octopus Deploy.
Deployer is an open source tool with 6.94K GitHub stars and 986 GitHub forks. Here's a link to Deployer's open source repository on GitHub.
According to the StackShare community, Octopus Deploy has a broader approval, being mentioned in 47 company stacks & 15 developers stacks; compared to Deployer, which is listed in 8 company stacks and 5 developer stacks.
Pros of Deployer
- Simply to use8
- Easy to customize7
- Easy setup6
Pros of Octopus Deploy
- Powerful30
- Simplicity25
- Easy to learn20
- .Net oriented17
- Easy to manage releases and rollback14
- Allows multitenancy8
- Nice interface4
Sign up to add or upvote prosMake informed product decisions
Cons of Deployer
Cons of Octopus Deploy
- Poor UI4
- Config & variables not versioned (e.g. in git)2
- Management of Config2