Announcing the Octopus Intelligence Agent app integration with GitHub. For years, developer productivity focused on writing code faster. Today, speed is just the default with agents such as Copilot contributing huge amounts of code and generally being the top contributor by commit volume in many enterprises. The challenge is that AI code contributions mean that the focus is now shifting towards how teams understand, manage, secure, and deploy software throughout its entire lifecycle, while having to handle multiple agents along the way. That's why the strategic partnership between Octopus Deploy and GitHub is so significant. While many organizations view AI as a coding assistant, GitHub and Octopus are helping teams unlock something more powerful: an AI-enabled software delivery platform that connects development, deployment, operations, and most importantly governance into a single intelligent workflow. As partners, Octopus Software Inc. made steps in this direction by contributing to major innovations such as Copilot Extensions back in 2024, then Custom Agents in 2025 and now being again a launch partner for Agent Apps within GitHub. No more context switching and more control over your agents. The launch of Agent HQ at GitHub Universe made it already possible to access coding agents from Anthropic, OpenAI, Google, Cognition and xAI directly within the GitHub interface. Because regardless of how powerful they are, more agents will not improve efficiency, but rather generate complexity and loss of control unless properly governed. But writing code is only one part of the journey. The real challenge for enterprise teams begins after the pull request is merged: * Understanding deployment status * Managing complex release pipelines and troubleshooting production issues * Coordinating multi-tenant deployments and identifying issues while operating software at scale * Maintaining security and compliance controls Historically, these activities have required developers to switch between multiple tools, dashboards, and operational systems. But every context switch creates friction, every disconnected workflow slows delivery or, even more importantly, delays recovery when something goes wrong. This is precisely the problem Octopus and GitHub are solving together by bringing the Octopus Intelligence to Agent HQ. When deployment information becomes accessible through natural language, organizations can unlock knowledge that was previously only accessible to specialist teams and take action quicker when necessary, avoiding downtime. "The future of software development won't be shaped by any single agent, but by an ecosystem of specialized ones. Our partners are defining what that looks like by embedding Agent apps into the GitHub workflows where developers build and ship." Mario Rodriguez, Chief Product Officer at GitHub By combining the Octopus MCP Server with specialized skills, the Octopus Intelligence Agent enables a seamless, automated workflow. This integration allows the agent to interact directly with Octopus Deploy from the GitHub interface, surfacing key data and executing tasks as directed. Here is an example use case for the Octopus Intelligence Agent, directly within GitHub Agent HQ: * Show the deployment status of a PR, and when it was deployed to a specific tenant * Investigate and diagnose why it has failed * Use the appropriate runbook to fix the failure * Redeploy to tenant See it in action! The demo video below shows how the Octopus Intelligence agent helps diagnose and recover from failed tenant deployments without leaving GitHub. When reviewing a PR, you can check the deployment status across tenants, investigate failures, and trigger the appropriate runbook to fix the root cause - then redeploy directly to the affected tenant once resolved. Its strategic partnership. Octopus Deploy and GitHub share a long standing committed partnership, focused on shaping a best-of-breed enterprise CI/CD landscape. GitHub is where developers collaborate, build, and innovate. Octopus is where organizations orchestrate complex deployments across hybrid infrastructure, including Kubernetes, cloud-native platforms, or legacy systems, with enterprise governance in mind. And Octopus Software Inc. is not stopping there. By aligning its GitHub and Microsoft partnerships, Octopus Software Inc. is able to bring the next level of DevOps innovation to its customers. Together, Octopus Software Inc. create a connected software delivery experience that helps teams move faster and securely despite the increasing complexity. If you are interested in using Octopus together with GitHub, you can now register for a free account - the agentic features are included! Octopus Deploy can be purchased via the Microsoft Marketplace and is Azure benefit eligible. Happy deployments!

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.