
Work Here?
Octopus Deploy provides a deployment automation platform that helps DevOps teams manage software releases and deployments across cloud, data centers, and hybrid IT environments. It integrates with popular CI systems like Jenkins, Azure DevOps, and TeamCity, so teams can coordinate builds and deployments in one place. The platform supports consistent deployment processes, environment-specific variables, and automated runbooks for routine operations, with capabilities for rolling, blue-green, and canary deployments, detailed audit logs, and role-based access control. It targets everything from small software teams to large enterprises, aiming to simplify release orchestration and ensure reliable, scalable software delivery across diverse infrastructures.
Industries
Enterprise Software
Cybersecurity
Company Size
201-500
Company Stage
Growth Equity (Venture Capital)
Total Funding
$202.5M
Headquarters
Brisbane, Australia
Founded
2012
Help us improve and share your feedback! Did you find this helpful?
Total Funding
$202.5M
Above
Industry Average
Funded Over
2 Rounds
Health Insurance
Dental Insurance
Vision Insurance
401(k) Retirement Plan
401(k) Company Match
Stock Options
Parental Leave
Unlimited Paid Time Off
Paid Vacation
Paid Sick Leave
Flexible Work Hours
Hybrid Work Options
Remote Work Options
Wellness Program
Mental Health Support
Phone/Internet Stipend
Home Office Stipend
Professional Development Budget
Conference Attendance Budget
Policies are now generally available. Today Octopus Software Inc. is excited to announce the launch of Policies to all Enterprise customers. Policies enable users to easily enforce deployment standards across their Octopus instance without manual effort. What are policies? Policies in Octopus are designed to ensure compliance and governance by default, making it easier to enforce deployment controls at scale. This approach allows you to shift compliance left, alleviating the burden of manual audits and enabling you to maintain high standards across your organization. With policies, you can enforce organization-wide compliance across teams and regions, moving governance out of Confluence docs and Slack threads and into the heart of your delivery pipeline. Using Rego, you can write custom policy checks that align with your requirements, block non-compliant deployments, and access detailed audit logs of policy evaluation events. This method ensures compliance is not an afterthought; it is embedded within every deployment pipeline, providing a seamless and efficient way to uphold governance standards across all activities. Why use policies? Policies streamline the enforcement of standards across all deployments by automating compliance checks and governance measures. * You want to ensure that every deployment conforms to predefined standards without manual effort. * You wish to manage these standards centrally, allowing for consistent application across your organization and easy updating of standards. While policies may not be necessary in every deployment scenario, they are invaluable if maintaining compliance and security is a priority. By embedding policies into your deployments, you can minimize risks and ensure that all teams are aligned with your organizational standards. What policies can I enforce? Check that a deployment step is present when deploying to production This policy can check that any step (Octopus step, Custom step template, Community Step template, or Process Template) exists in a deployment process (or runbook process), and: * Is not skipped * Is enabled * Is at a certain position in the deployment process (or runbook process) * Is a certain version (for custom step templates, community step templates, and process templates) * Isn't run in parallel with another step. Example: I can check that all deployments to production must have my "Security-Scan" process template present at the end of every deployment and is of version 2.0.0. Check that a package, container image, or deployment process from a version-controlled deployment process is from the main / master branch when deploying to production. * Package * Container Image * Deployment process from a version-controlled process are from the main / master branch when deploying to any environment. I want to ensure that all deployment processes in my version controlled project are from the main / master branch so that only approved deployment processes are being used to deploy to production. To get started, please visit its documentation, which contains examples of common scenarios that you can use as a reference. Policies are now available to all Enterprise customers. If you are on Enterprise Cloud, you can click the Platform Hub icon to get started. If you are using a self-hosted version of Octopus, please upgrade to the 2025.4 server release to adopt Policies.
London, 11th November 2025 – Octopus Energy has snapped up Kuppa, a smart home-energy software startup, further strengthening its position as a clean tech giant and enabling it to make low-carbon home upgrades faster, easier and cheaper than ever.
Announcing Process Templates Public Preview. Today, Octopus Software Inc. is excited to introduce Process Templates Public Preview, a powerful new feature designed to help teams harmonize their pipelines and reduce duplication across projects and teams. Process Templates enable you to easily create reusable, standardized deployment process building blocks. What are Process Templates? Process Templates are reusable sets of deployment steps that can be shared across multiple Spaces in Octopus Deploy. Instead of copying and pasting deployment processes across teams and applications, which often leads to configuration drift, unnecessary duplication, and operational debt, you create a single source of truth that any project can consume. By abstracting your best practices for deployments into Process Templates, you make it easy for teams to follow standards and accelerate delivery. Why use Process Templates? * Reduce duplication: Update Process Templates from one place, Platform Hub, and have the changes reflected everywhere. * Consistency at scale: Keep your pipelines consistent no matter how many teams or projects use them. * Safe and secure delivery: Centralizing important deployment patterns in Process Templates ensures that your developers automatically deploy safely and securely whenever they use a Process Template. * Faster onboarding: Developers no longer need to worry about mis-configuring deployment processes. They can consume a trusted, version-controlled Process Template that they can rely on to be updated with best practices. * Shared responsibility: Empower teams with ownership over their process, maintaining flexibility while reusing best practices, ensuring a collaborative approach to deployments. How to get started with Process Templates. There are several common use cases for Process Templates that show how this feature improves your deployments. Templating part of a deployment process. Platform engineers may expect that each project includes manual approval or email notification steps in every process. Each team might build its manual approval steps and email notifications from scratch or copy them from another project. Over time, these steps diverge in configuration, leading to drift and deployment errors. Keeping these governance steps consistent across multiple pipelines requires repetitive work and is prone to errors. With Process Templates, Platform Engineers can create a template containing the correct approval steps for every deployment process and share it with every Space. This template can be consumed in any project and added to an existing deployment process. The Process Template is customized to fit the project's needs and will receive updates as it is updated in Platform Hub, ensuring developers can easily stay aligned with best practices. Templating an entire deployment process. Some companies may use a microservices architecture, which is replicated across multiple projects with only the configuration changing. Even though the deployment steps are identical, platform teams must create and maintain separate processes for each service, customizing configuration values. Over time, these processes drift as it isn't easy to update every pipeline with the latest changes. With Process Templates, Platform Engineers define the entire deployment process once, with parameterized values for all configuration differences (such as Docker image names, environment variables, or secrets). Each microservice project then consumes this template, supplying its configuration through parameters on the Process Template. Self-Service deployment processes for application teams. Your company may have many application teams building new business components such as Web APIs, Frontend applications, or Storage components. You want to empower your application teams to go from zero to production-ready deployments in minutes, without waiting on team members or copying and pasting reference projects.With Process Templates, the platform team can create a library of standardized templates for each supported component type. These templates encode best practices for deploying business components. Application teams can pick the template matching their component type, fill out information that tailors the template to their project, and be ready to deploy to production with ease. * For more information on use-cases, please visit its use-cases page on its website. * For a demo of process templates, you can watch its Youtube video. How do Process Templates work in Octopus? Process Templates are simple to set up and work similarly to a regular deployment process. * You must be on an Enterprise license. * You must visit Platform Hub and connect Octopus to a Git repository. * Add a Process Template from the Process Templates interface in Platform Hub. * Add an Octopus built-in step to your deployment process. This step is similar to the existing Process Editor in your project. * You can use a value or a parameter when filling out a step. To set up a parameter, visit the "Add Parameter" experience on a Process Template. * After you've added steps and configured parameters, you'll need to commit, publish, and share the template. You must commit and publish a new version each time you change the template. * To use a Process Template in a project, you must add it via the "Add Step" experience. You can select the relevant Process Template from the dropdown and set what updates you'd like to receive. * In the Parameters tab, fill in the required parameters for the Process Template, and your Process Template is ready for deployment. If your current Platform Engineering approach involves building and maintaining everything yourself, Octopus Software Inc. believe process templates are a more effective solution. Process Templates are available to all Octopus Enterprise Tier customers. An installation guide for self-hosted customers can be found on its installation guide docs page.
Brisbane-based software firm Octopus Deploy received a $172.5 million investment from US venture capital firm Insight Partners in April 2021. Following this, the company adopted a less conservative fiscal approach, leading to significant revenue growth. Recently, Octopus Deploy secured an additional $30 million investment from Insight Partners to fund its first major acquisition. The firm's accounts from 2020 to 2024 reflect this strategic shift.
The partnership, announced June 9th, connects Octopus Deploy's continuous delivery platform with Datadog's monitoring and security platform to give development teams a unified view of their entire software pipeline.
Find jobs on Simplify and start your career today
Industries
Enterprise Software
Cybersecurity
Company Size
201-500
Company Stage
Growth Equity (Venture Capital)
Total Funding
$202.5M
Headquarters
Brisbane, Australia
Founded
2012
Find jobs on Simplify and start your career today