Octopus Server

Deployment automation and runbook platform installed on servers or Kubernetes infrastructure you operate.

9 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Octopus Server November 2026 privilege and authentication fixes

SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation.

Scope: CVE-2026-96414, CVE-2026-116835, and CVE-2026-116288; fixed builds differ between the 2026.2 and 2026.3 lines.

Authentication configuration, OIDC use, and delegated roles determine exposure. SA2026-28 has no mitigation.

Action: Upgrade to the branch-specific fixed build or vendor-recommended 2026.3.16117 and review privileged sessions and delegated roles.

Primary source · SA2026-19 · SA2026-22 · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    Windows MSI, Docker or Docker Compose, or the official Helm chart on Kubernetes

  2. Operated by

    Your team

    Customer operates the server or cluster, SQL database, persistent storage, backups, security, upgrades and availability configuration.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodWindows MSI, Docker or Docker Compose, or the official Helm chart on Kubernetes
InfrastructureServers / containers
Octopus Server runs as a Windows service or Linux container and depends on SQL Server plus persistent package, artifact, task-log and configuration storage.
Licensing modelCommercial Only
Octopus Server is proprietary software governed by the Octopus Customer Agreement. Its no-cost Free tier is usage-limited and license-key activated; Professional and Enterprise are paid annual tiers.
LicenseProprietary Free tier or annual Professional and Enterprise licenses.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 7 documented · 5 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

The purchasing FAQ distinguishes Octopus Cloud and Server licences. A current Marketplace offer explicitly delivering/entitling self-hosted Server was not established.

Reviewed public evidence for Octopus Server; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

Server purchasing terms did not establish an eligible offer or qualifying fees against an existing cloud commitment agreement.

Reviewed public evidence for Octopus Server; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

Octopus Server documents external identity providers and OpenID Connect. Provider compatibility and licence features vary; disabling a user in the IdP does not immediately revoke an already active Octopus session.

Self-hosted Octopus authentication · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

SCIM 2 is documented for the Microsoft Entra ID authentication provider with a licence including SCIM, such as Enterprise. The IdP needs inbound HTTPS access to the Octopus API.

Self-hosted SCIM, supported provider and licence required · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The PCI guidance describes deployment controls and network separation, not an attestation covering a customer-operated Server environment. Obtain the applicable report and deployment scope.

Self-hosted PCI controls versus independent certification · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

External authentication creates an Octopus session cookie; immediate revocation also requires disabling the user in Octopus. Scope API keys and configure HTTPS, server encryption and target communication separately. Current advisory review: SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. Upgrade to the branch-specific fixed build or vendor-recommended 2026.3.16117 and review privileged sessions and delegated roles.

Server sessions and access revocation CVE-2026-96414, CVE-2026-116835, and CVE-2026-116288; fixed builds differ between the 2026.2 and 2026.3 lines. · Source ↗ · Prior security-controls source ↗ · SA2026-19 ↗ · SA2026-22 ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

The isolated-server guide covers separate networks and offline package-drop targets. It does not by itself establish a complete no-internet Server licensing, dependency and update workflow for the selected licence.

Server isolation versus an offline deployment target · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The vendor supplies a Server Linux-container Kubernetes deployment workflow, with separate persistent storage and SQL database configuration. Pin compatible server images and configure the selected cluster and secrets.

Octopus Server in customer Kubernetes · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The small 5–10 concurrent-task baseline is one Server with 2 cores/4 GB RAM plus SQL Server Express with 2 cores/4 GB, or Azure SQL with 25–50 DTUs. HA servers, workers, database and task load require separate sizing.

Vendor small-workload baseline; not the total HA topology · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Octopus Server is proprietary software governed by the Octopus Customer Agreement. Its no-cost Free tier is usage-limited and license-key activated; Professional and Enterprise are paid annual tiers.

Octopus Server: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Confirm HA Server replicas, workers, concurrent tasks and a supported SQL Server HA/licensing design. The small single-server task baseline does not establish the requested HA topology. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Octopus recommends 2026.3.16117 after November security advisories. Branch-specific minimum fixes include 2026.2.13487/2026.3.15875, 2026.2.13503/2026.3.15894, and 2026.2.13526/2026.3.15909.

Octopus Server 2026.2 and 2026.3 maintained lines · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

This entry covers self-hosted Octopus Server, not Octopus Cloud. Octopus Server requires SQL Server 2016 or later or Azure SQL and a license key, including for the Free tier. The Linux container is stateful and needs persistent storage and monitoring. Self-hosted releases trail the cloud product by at least one quarter; each self-hosted major.minor release receives critical patches and support for six months. Octopus advisories SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. The last issue has no mitigation; Octopus recommends current 2026.3.16117, with branch-specific fixed builds also documented.

Category fit

DevOps
Continuous delivery, release orchestration and operational runbook automation.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Octopus Server container on AWS ECS or EKS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Octopus explicitly lists Amazon ECS and EKS among supported underlying technologies for the Server Linux container. This is the server application in customer-operated AWS infrastructure.

    • Octopus Server in customer Kubernetes clusters with AKS and GKE guidance ↗ · Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Octopus documents hosting the full Server application in the customer's Kubernetes cluster and calls out provider-specific AKS and GKE considerations. Customers supply supported database and storage architecture.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory