
# Octopus Server

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

Canonical page: https://launchinyourcloud.com/directory/octopus-server/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Octopus Server

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

- Listing: https://launchinyourcloud.com/directory/octopus-server/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary Free tier or annual Professional and Enterprise licenses.
- Licensing model: commercial-only
- Installation: Windows MSI, Docker or Docker Compose, or the official Helm chart on Kubernetes
- Architecture: Customer-operated stateful Octopus Server nodes with SQL Server and persistent storage.
- Operations: Customer operates the server or cluster, SQL database, persistent storage, backups, security, upgrades and availability configuration.
- Product website: https://octopus.com/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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.

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 runs as a Windows service or Linux container and depends on SQL Server plus persistent package, artifact, task-log and configuration storage.


### Category fit

- devops: Continuous delivery, release orchestration and operational runbook automation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://octopus.com/docs/installation (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes (checked 2026-11-17). 


### Cloud deployment evidence

- Octopus Server container on AWS ECS or EKS (aws): https://octopus.com/docs/installation
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Octopus Server in customer Kubernetes clusters with AKS and GKE guidance (azure, gcp): https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install Octopus Server: https://octopus.com/docs/installation

- Run Octopus Server in Kubernetes: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes

- Octopus Server installation requirements: https://octopus.com/docs/installation/requirements

- SQL database requirements: https://octopus.com/docs/installation/sql-database/

- Octopus licensing and purchasing FAQ: https://octopus.com/pricing/faq

- Octopus Server downloads: https://octopus.com/downloads

- Octopus SA2026-19: https://advisories.octopus.com/post/2026/sa2026-19/

- Octopus SA2026-22: https://advisories.octopus.com/post/2026/sa2026-22/

- Octopus SA2026-28: https://advisories.octopus.com/post/2026/sa2026-28/

### Licensing sources

- https://octopus.com/pricing/faq

- https://octopus.com/free

### Infrastructure sources

- https://octopus.com/docs/installation

- https://octopus.com/docs/installation/sql-database/


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The purchasing FAQ distinguishes Octopus Cloud and Server licences. A current Marketplace offer explicitly delivering/entitling self-hosted Server was not established. Scope: Reviewed public evidence for Octopus Server; unresolved within this edition/deployment. Source: https://octopus.com/pricing/faq (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Server purchasing terms did not establish an eligible offer or qualifying fees against an existing cloud commitment agreement. Scope: Reviewed public evidence for Octopus Server; unresolved within this edition/deployment. Source: https://octopus.com/pricing/faq (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. 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. Scope: Self-hosted Octopus authentication. Source: https://octopus.com/docs/security/authentication/ (reviewed 2026-11-17).

- SCIM provisioning: Edition-dependent. 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. Scope: Self-hosted SCIM, supported provider and licence required. Source: https://octopus.com/docs/security/authentication/scim/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. 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. Scope: Self-hosted PCI controls versus independent certification. Source: https://octopus.com/docs/security/pci-compliance-and-octopus-deploy (reviewed 2026-11-17).

- Security controls: Documented. 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. Scope: 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: https://advisories.octopus.com/post/2026/sa2026-28/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://octopus.com/docs/security/authentication/. Supporting source: SA2026-19 — https://advisories.octopus.com/post/2026/sa2026-19/. Supporting source: SA2026-22 — https://advisories.octopus.com/post/2026/sa2026-22/.

- Air-gapped operation: Sources checked — unresolved. 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. Scope: Server isolation versus an offline deployment target. Source: https://octopus.com/docs/installation/isolated-octopus-deploy-servers/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. 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. Scope: Octopus Server in customer Kubernetes. Source: https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. 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. Scope: Vendor small-workload baseline; not the total HA topology. Source: https://octopus.com/docs/administration/managing-infrastructure/performance/ (reviewed 2026-11-17).

- License pricing: Documented. 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. Scope: Octopus Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://octopus.com/pricing/faq (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. 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. Scope: 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: https://octopus.com/docs/administration/managing-infrastructure/performance/ (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. 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. Scope: Octopus Server 2026.2 and 2026.3 maintained lines. Source: https://advisories.octopus.com/2026/ (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Octopus Server November 2026 privilege and authentication fixes (security-advisory): 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. Conditions: 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. Source: https://advisories.octopus.com/post/2026/sa2026-28/; reviewed 2026-11-18. Supporting source: SA2026-19 — https://advisories.octopus.com/post/2026/sa2026-19/. Supporting source: SA2026-22 — https://advisories.octopus.com/post/2026/sa2026-22/.



