Octopus, with its many tentacles, maintains a tight grip on your deployment process

Octopus Deploy is used in our Information Technology department to automate the deployment of more than 60 applications, both internal and public-facing. Octopus Deploy allows us to be more consistent with how applications are deployed to four different lifecycle environments (Dev, QA, Stage, and Production). It allows us to have an easy fallback strategy if an application makes it to one of the environments and has an issue. It allows us to securely store sensitive information for these deploys (passwords, connection strings, keys, etc.) as opposed to saving these values in source code or environment variables. It allows us to easily and securely maintain the multitude of SSL certificates on the servers where we deploy. It saves the organization time and money by making this step of the dev-ops process more efficient and consistent. The deploys that were done with Octopus Deploy minimize and virtually eliminate downtime and its effect on our users.

Because many of our deployments are close to zero downtime, we can deploy as soon as an application change makes it through our QA and approval process. Prior to utilizing Octopus Deploy, most deploys had to wait until after hours or scheduled downtimes.

Once a project is set up in Octopus Deploy, the time spent on deployment by developers has been minimized. However, the initial setup of some of our more complex projects takes some extra time. Most of the projects are simple and are easy to set up using another project as a template or a guide.