Octopus Deploy Reviews and Ratings

Use Cases and Deployment Scope

We use Octopus Deploy for Automated deployments of new releases through different lifecycles and environments.

We receive a signed off version update of the application which is packaged into a release. This release can be deployed then to all the relevant DEV/QA/TEST/PRE/PROD Environments.

The version cannot move from one environment to the next until approved and signed off.

Due to the nature of our product it is important the release remains consistent throughout the release lifecycle - Dev to Prod. Octopus Deploy ensures this consistency by removing manual steps such as packaging the release and the installation steps for each.

Likelihood to Recommend

Octopus Deploy is well suited for our requirements of deploying across multiple environments with one consistent release.

We are saving a lot of time by not having to package and move release files around. Our release process is more efficient and consistent with automation.

There are some parts that we could probably perform with existing tools such as DevOps and there are one or two features we have to workaround to fit for our setup such as the step templates to install websites. These are minor in our opinion.

Use Cases and Deployment Scope

We use the simplest Octopus use-case. We have multiple projects (websites, windows services, web apis) that we deploy to test and live servers using the octopus calamari client listener.

Everything just works as expected, and it makes deployments vanishingly simple. Also, the ease with which I can make a deployment, or re-deploy an old check-in means that rolling back is easy, which in turn makes all deployments much less stressful!

I cannot speak for the more advanced aspects of Octopus, but I cannot imaging working with a client on windows software and making live or test deployments without octopus. I would recommend it to any new client I meet.

Likelihood to Recommend

Once set up it enables non-technical users to fully deploy a complex site, meaning the test/integration team can control any deployments to live without having to go back to the development team.

Use Cases and Deployment Scope

We have used Octopus Deploy for many years now for our CI/CD (Continuous Integration/ Continuous Deployment) of roughly twenty projects. After a steep first learning curve and the initial investment of time and effort in the deployment projects, Octopus Deploy has saved us an uncountable number of hours in the past eight years. In all my career, I have seldom encountered such a versatile, powerful, and well-engineered software product. Support is also very responsive.

Likelihood to Recommend

Octopus Deploy fits in any scenario you could think of. There is literally nothing it can't do in terms of the intricacy of deployment logic.

Use Cases and Deployment Scope

Octopus Deploy is used within our organization to provide continuous deployment to the development environment with manual gates for production deployment. Octopus Deploy is able to handle any environment or application, from very old legacy applications deployed to Windows Scheduled Tasks all the way to cloud-native function and service applications.

Likelihood to Recommend

Octopus Deploy is a fantastic product. It shines particularly well in deployments, as the name would indicate. Our use case is for deployment and post-deployment automated usability testing, and the process steps provide a very clear mechanism to configure the runs. We have been able to deploy to machines of all kinds and operating systems, to jobs, and FaaS, all without too much effort or team stress. If you're just starting out with a deployment service or you're a veteran, Octopus Deploy is well worth investigating.

Use Cases and Deployment Scope

We use Octopus Deploy to deploy software across the whole estate and to ensure version control is adhered. Octopus has been great in allowing us to expand across the world and has become an important tool in our product cycle. It's a shame that their change in pricing structure for their cloud service is now pricing us out of continuing to use the service long term.

Likelihood to Recommend

I think for any business having to manage custom software at multiple endpoints there's not really anything better. It's just the new pricing model is pretty extreme and will price out any small to medium enterprises from their service. I love the product even with all the UI issues but yeah currently having trouble recommending it because the cost to service is now out of control.

Use Cases and Deployment Scope

Before we used Octopus Deploy, we used to deploy our websites to our servers manually. This was a time consuming, error prone process. Many late evenings were spent in the office purely for website deployments.

We moved our deployment process into Octopus Deploy, automated and standardized every step, and have scaled the same process out to more websites as we've worked on more projects. We're even able to schedule the deployments so they can happen after hours without someone needing to work late.

Likelihood to Recommend

Octopus Deploy has been able to do everything we've set out to make it do. Most of the time there are either built-in or community made step templates, but we've also authored a handful of our own. I have used it for deploying to Windows servers, Linux servers, and Docker containers in Azure. We've predominantly deployed applications written in dotnet and JavaScript.

Use Cases and Deployment Scope

We've been using Octopus to deploy our products to multiple environments customers and countries.

Likelihood to Recommend

Octopus starts being useful the first time you ever deploy but quickly becomes vital as soon as you start versioning or going to production. It's sure some work to set up but definitely worth it. The only time when we don't use it of for disposable PoCs.

Use Cases and Deployment Scope

Octopus Deploy is helping to solve bottlenecks in getting code changes out to our Cloud Environments, as well as helping us automate our DevOps Tooling around database housekeeping, environment automation and general DevOps. The granular permissions model lets us empower developers without handing them the keys to the entire cloud castle, and the detailed auditing gives us the agility we need with confidence we can trace problems back to their source.

We're also planning for a small number of quirky use cases where the polling tentacle forms a useful bridge between PaaS out in the cloud and disparate services running behind NATs and Firewalls.

Likelihood to Recommend

It's a brilliant deployment engine on the infrastructure side of a build pipeline. You _can_ shift it further left, but it is better used once your CI server has generated artifacts

Use Cases and Deployment Scope

We use it for creating automating release deployments. It has very intuitive User Interface which makes it easy for less technical user like business personnel use. It has a number of plugins to support most of the devops tools to integrate with. What I personally love about Octopus Deploy is its proactive support. We post our queries, issues or requirement via email and they almost respond within hour.

Likelihood to Recommend

Octopus Deploy is specifically suited if you have a very specific requirement for your release pipeline, it gives the option to create a runbook too where you can have steps that need to run after deployment step is run successfully. It also provides tenants option, if you want to deploy same application with different vendor with minor changes.

Use Cases and Deployment Scope

CI/CD Pipeline is an essential component for DevOps practice and the overall Software Delivery Life Cycle. We use Octopus Deploy in the Continuous Deployment part in our CI/CD pipeline. It helps us deploy code changes quickly and reliably.

Likelihood to Recommend

Ocotpus Deploy is good where the CI server doesn't have a deploy functionality.