
# DevOps

Source control and delivery tooling.

Canonical page: https://launchinyourcloud.com/categories/devops/
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.


Source control and delivery tooling.

28 listings.


## Argo CD

GitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.

- Listing: https://launchinyourcloud.com/directory/argo-cd/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Argo CD. Commercial management platforms and support offerings are separate.
- Licensing model: open-source
- Installation: Install the official release Kubernetes manifests into a cluster; upstream releases provide standard and high-availability installation manifests.
- Architecture: Customer-operated Kubernetes API service, repository server and application controller, using Git repositories as desired-state sources
- Operations: Customer manages Kubernetes capacity, repository and cluster credentials, RBAC, identity integration, network exposure, application policies, backups and supported-version upgrades.
- Product website: https://argo-cd.readthedocs.io/
- Source review: 2026-11-20; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Argo CD runs in Kubernetes and needs credentials for the clusters and repositories it manages. Git hosting, identity providers, image registries and target applications may reside outside the account. The listing covers upstream Argo CD rather than commercial management services or the separate Argo Workflows product. Argo CD patches v3.6.2, v3.5.8, and v3.4.14 update the bundled regexp2 library for CVE-2026-77299. Apply the patch for the deployed minor line and check the application version bundled in any Helm chart or provider package.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

The official manifests deploy continuously running Argo CD services and controllers to a Kubernetes cluster. The upstream release page includes separate high-availability manifests.


### Category fit

- devops: Declarative continuous delivery for Kubernetes: compares deployed application state with Git-defined desired state and supports synchronization, health visibility and rollback operations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/awslabs/cdk-eks-blueprints/blob/main/docs/addons/argo-cd.md (checked 2026-11-12). 


### Cloud deployment evidence

- Self-managed Argo CD through AWS EKS Blueprints (aws): https://github.com/awslabs/cdk-eks-blueprints/blob/main/docs/addons/argo-cd.md
  AWS EKS Blueprints installs the Argo CD Helm chart and its components in the customer EKS cluster. This is distinct from the managed Amazon EKS capability. Configure administrator credentials, repository secrets, upgrades and application cleanup before cluster deletion.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Argo is a CNCF Graduated project. The upstream Argo CD release page records version 3.6.1 on 4 November 2026 and supported-series maintenance releases. A 2026 CNCF Adobe case study specifically describes operationalizing Argo CD within its enterprise delivery platform; the Argo CD repository also maintains named adopters.

Reviewed 2026-11-10.

- CNCF Argo maturity and governance context: https://www.cncf.io/projects/argo/

- Recent upstream Argo CD releases: https://github.com/argoproj/argo-cd/releases

- Adobe enterprise Argo CD case study: https://www.cncf.io/case-studies/adobe/

- Argo CD adopter list: https://github.com/argoproj/argo-cd/blob/master/USERS.md

### Sources

- Official installation and first application: https://argo-cd.readthedocs.io/en/stable/getting_started/

- Argo CD component architecture: https://argo-cd.readthedocs.io/en/stable/operator-manual/architecture/

- Release manifests and maintenance: https://github.com/argoproj/argo-cd/releases

- Upstream Apache-2.0 license: https://github.com/argoproj/argo-cd/blob/master/LICENSE

- Argo CD v3.6.2 patch release: https://github.com/argoproj/argo-cd/releases/tag/v3.6.2

- Argo CD v3.5.8 backport: https://github.com/argoproj/argo-cd/releases/tag/v3.5.8

- Argo CD v3.4.14 backport: https://github.com/argoproj/argo-cd/releases/tag/v3.4.14

### Licensing sources

- https://github.com/argoproj/argo-cd/blob/master/LICENSE

### Infrastructure sources

- https://argo-cd.readthedocs.io/en/stable/getting_started/

- https://github.com/argoproj/argo-cd/releases


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Argo CD documents bundled Dex connectors or an existing OIDC provider for UI/CLI sign-in. Identity-provider claims and Argo CD RBAC require explicit configuration; Core-only installs omit the UI/SSO components. Scope: Full Argo CD installation, not Core-only mode. Source: https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official getting-started guide installs upstream Kubernetes manifests. The stable branch reference moves; pin a release for controlled deployment and configure certificates, identity and RBAC. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://argo-cd.readthedocs.io/en/stable/getting_started/ (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml. Artifact reference: stable (moving branch; select a release tag).

- Minimum footprint / sizing: Documented. The official HA manifests require at least three distinct Kubernetes nodes because of anti-affinity and deploy additional components including HA Redis. CPU/memory depend on managed applications, repositories, rendering and reconciliation concurrency; this topology floor is not a fixed workload capacity guarantee. Scope: Upstream HA topology floor; component sizing requires measurement. Source: https://argo-cd.readthedocs.io/en/stable/operator-manual/high_availability/ (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/argoproj/argo-cd/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Argo CD v3.6.2 updates regexp2 for CVE-2026-77299. The v3.5.8 and v3.4.14 release notes document the corresponding backports. Scope: Upstream Argo CD application; chart and provider package versions may differ. Source: https://github.com/argoproj/argo-cd/releases/tag/v3.6.2 (reviewed 2026-11-20).




### Security and lifecycle reviews

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

- Argo CD regexp2 dependency update (security-advisory): Argo CD updated regexp2 to address CVE-2026-77299. Scope: Upstream Argo CD releases v3.6.2, v3.5.8, and v3.4.14 contain the documented fix. Conditions: The cited release notes establish a regexp2 dependency fix, not an Argo-specific exploit path or complete affected-version range. Helm charts and provider packages have separate versions; inspect their underlying Argo CD application version. Action: Apply the patched release for the deployed minor branch and follow the upstream upgrade guidance for cross-minor changes. Source: https://github.com/argoproj/argo-cd/releases/tag/v3.6.2; reviewed 2026-11-20. Supporting source: Argo CD v3.5.8 backport — https://github.com/argoproj/argo-cd/releases/tag/v3.5.8. Supporting source: Argo CD v3.4.14 backport — https://github.com/argoproj/argo-cd/releases/tag/v3.4.14.




## Azure DevOps Server

Source control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.

- Listing: https://launchinyourcloud.com/directory/azure-devops-server/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary; Express is free for up to five active users, while paid Server use requires server and user entitlements plus Windows licensing.
- Licensing model: commercial-only
- Installation: Windows installer on an Azure VM with SQL Server, Azure SQL Database or Azure SQL Managed Instance
- Architecture: Customer-operated Windows application tier and SQL data tier.
- Operations: Customer operates the Azure VMs, Windows, SQL data tier, backups, patches, upgrades and Azure DevOps Server configuration.
- Product website: https://azure.microsoft.com/en-us/products/devops/
- 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 Azure DevOps Server, not Microsoft-hosted Azure DevOps Services. Microsoft's Azure configuration installs the server on an Azure VM and can use Azure SQL Database or Azure SQL Managed Instance. Advanced configuration is unavailable on Azure VMs; use Basic or Azure configuration. SQL Server on Linux is unsupported. Only Azure receives a badge because current first-party documentation does not establish equivalent AWS or Google Cloud server deployments. Azure DevOps Server 2022.2 Patch 9, published October 13, 2026, includes security fixes and is recommended by Microsoft. Confirm the exact server generation and prerequisite patch sequence before applying it.

Azure DevOps Server is proprietary Microsoft software. Express is a no-cost license limited to five active users, not an open-source edition; broader use requires paid server/CAL or eligible Visual Studio and Azure DevOps entitlements.

Azure DevOps Server runs on customer-operated Windows application-tier VMs and requires a supported SQL Server or Azure SQL data tier.


### Category fit

- devops: Self-hosted repositories, pipelines, test plans and artifact management.

- project-management: Azure Boards provides work-item tracking, backlogs and planning within the same server.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server (checked 2026-11-17). 


### Cloud deployment evidence

- Azure DevOps Server on an Azure VM with Azure SQL (azure): https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server
  Microsoft requires Azure DevOps Server on an Azure VM for the documented Azure SQL topology and supplies Azure VM identity, networking, firewall and database steps. Application and data tiers remain in the customer's Azure environment.
  Source type: provider-guide; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install and configure Azure DevOps Server: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- Use Azure SQL with Azure DevOps Server: https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server

- Azure DevOps Server requirements: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server

- Azure DevOps Server pricing and licensing: https://azure.microsoft.com/en-us/pricing/details/devops/server/

- Azure DevOps Server release notes: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server

### Licensing sources

- https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- https://azure.microsoft.com/en-us/pricing/details/devops/server/

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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. Server installation media and server/CAL licensing are documented. A current first-party Marketplace offer delivering this self-hosted Server edition was not established. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Azure DevOps Services billing and Azure VM charges do not establish Marketplace commitment treatment for Server licences/CALs. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Single sign-on: Documented. Microsoft distinguishes Server Windows authentication from Services Microsoft Entra authentication. Use Windows integrated authentication for the self-hosted server; Services service-principal and managed-identity patterns do not establish Server support. Scope: Azure DevOps Server identity boundary. Source: https://learn.microsoft.com/en-us/azure/devops/organizations/security/authentication-guidance?view=azure-devops (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The Server authentication guidance establishes Windows authentication and supported PAT/client-library paths, not a SCIM lifecycle endpoint. Microsoft Entra provisioning for Azure DevOps Services cannot be transferred to Server. Scope: Azure DevOps Server; SCIM unconfirmed. Source: https://learn.microsoft.com/en-us/azure/devops/organizations/security/authentication-guidance?view=azure-devops (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Azure DevOps Server material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://learn.microsoft.com/en-us/azure/devops/server/architecture/key-concepts?view=azure-devops (reviewed 2026-11-17).

- Security controls: Documented. Use the documented Windows/domain identity and permission boundaries and restrict service accounts and database access. Server security requirements are distinct from the Microsoft-hosted Services security posture. Current advisory review: Microsoft's Patch 9 for Azure DevOps Server 2022.2 includes security fixes and is recommended for affected installations. Apply Patch 9 or a later applicable supported update after checking prerequisites. Scope: Self-managed Server identity and authorization Azure DevOps Server 2022.2; other server generations require their own patch guidance.. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://learn.microsoft.com/en-us/azure/devops/server/architecture/key-concepts?view=azure-devops.

- Air-gapped operation: Sources checked — unresolved. The self-hosted installer and Windows/SQL dependencies are documented, but a complete disconnected activation, extension/feed and security-update workflow was not established. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Microsoft documents installing Server on a supported Windows host and configuring the application/database tiers. The Azure SQL topology requires Azure VMs; this is an installer/configuration workflow, not a pinned IaC artifact. Scope: Self-managed Windows Server installation. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Microsoft recommends an eight-core machine, 16 GB RAM and SSD for a single-server deployment. HA application tiers and SQL availability add servers; repository size, builds and usage can require more. Scope: Server hardware recommendation; not an HA minimum. Source: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server (reviewed 2026-11-17).

- License pricing: Documented. Azure DevOps Server is proprietary Microsoft software. Express is a no-cost license limited to five active users, not an open-source edition; broader use requires paid server/CAL or eligible Visual Studio and Azure DevOps entitlements. Scope: Azure DevOps Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Only Azure deployment is confirmed here. An AWS estimate would assume an unevidenced cloud path; obtain an Azure topology and Server/CAL/Windows/SQL licensing quote. 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://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Azure DevOps Server 2022.2 Patch 9 was published October 13, 2026 and includes security fixes. Match the patch to the exact installed server generation and prerequisites. Scope: Azure DevOps Server 2022.2. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Azure DevOps Server 2022.2 Patch 9 security update (security-advisory): Microsoft's Patch 9 for Azure DevOps Server 2022.2 includes security fixes and is recommended for affected installations. Scope: Azure DevOps Server 2022.2; other server generations require their own patch guidance. Conditions: Installed server generation and prerequisite patch level determine applicability. Action: Apply Patch 9 or a later applicable supported update after checking prerequisites. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server; reviewed 2026-11-18.




## Bitbucket Data Center

Commercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.

- Listing: https://launchinyourcloud.com/directory/bitbucket-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Bitbucket Data Center term license; eligible existing customers must transition to the Bitbucket Hybrid License to continue self-managed use beyond March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Bitbucket application nodes with Git storage or Mesh, an external database, load balancer, shared home and search services
- Operations: Customer manages Kubernetes or hosts, Git and shared storage, Mesh where used, database, search, networking, TLS, identity, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/bitbucket/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Bitbucket Data Center. Atlassian documents EKS, AKS and GKE with its supported Helm chart; the older AWS Quick Start and Azure Resource Manager templates are no longer maintained. Bitbucket and Bamboo are exempt from the retirement of the other affected Data Center products. Continued self-managed use after March 28, 2029 requires the Bitbucket Hybrid License; without transitioning, existing subscription instances become read-only. Atlassian plans availability in early 2027 for eligible existing Bitbucket or Bamboo Data Center/Server customers. The license also includes cloud services, but Atlassian states that the self-managed environment can remain in place without a data transfer. Atlassian rates CVE-2026-21589 critical (9.3). All Bitbucket Data Center versions before the fixed 9.4.26, 10.2.8, or 10.5.1 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Bitbucket URL-rewrite mitigation to every application and mirror node. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

Bitbucket is exempt from the end-of-life retirement of Jira and Confluence Data Center. Atlassian says eligible existing Bitbucket or Bamboo Data Center/Server customers can move to the Bitbucket Hybrid License, planned for early 2027, to retain self-managed Bitbucket beyond March 28, 2029. The existing standalone license route ends in 2029; without the Hybrid License transition, instances become read-only. Confirm eligibility, availability and renewal terms.

Bitbucket Data Center runs persistent application and Git-storage services with durable database, shared-home and repository storage.


### Category fit

- devops: Provides self-managed Git repository hosting, pull requests, code review, permissions and software-delivery integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (checked 2026-11-16). 


### Cloud deployment evidence

- Bitbucket Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html
  Atlassian documents Bitbucket Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Product-specific AWS and Azure pages also direct customers to the Helm path because the older templates are no longer maintained.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Run Bitbucket Data Center on Kubernetes: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html

- Bitbucket Data Center supported platforms: https://confluence.atlassian.com/display/BitbucketServer/Supported%2Bplatforms

- Bitbucket Data Center deployment on AWS: https://confluence.atlassian.com/security/deploy-bitbucket-data-center-in-aws-1402669978.html

- Bitbucket Data Center deployment on Azure: https://confluence.atlassian.com/security/deploy-bitbucket-data-center-in-azure-1402669984.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian Data Center end-of-life exceptions: https://www.atlassian.com/licensing/data-center-end-of-life

- Bitbucket Hybrid License eligibility and transition: https://www.atlassian.com/migration/bitbucket-hybrid-license

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

- https://www.atlassian.com/migration/bitbucket-hybrid-license

### Infrastructure sources

- https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html

- https://confluence.atlassian.com/display/BitbucketServer/Supported%2Bplatforms


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 documented, 1 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Bitbucket 7.12+; authentication does not assign application access or permissions. Scope: Bitbucket 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Bitbucket Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The Bitbucket 10.4 platform guide specifies x86-64, at least 2 CPU cores and 3 GB available RAM, including memory for Git operations. Repository activity, concurrency, database, shared storage and Mesh nodes require separate sizing. Scope: Bitbucket 10.4 application-host baseline; not a production cluster total. Source: https://confluence.atlassian.com/bitbucketserver104/supported-platforms-1822592149.html (reviewed 2026-11-16).

- License pricing: Documented. Bitbucket is exempt from the end-of-life retirement of Jira and Confluence Data Center. Atlassian says eligible existing Bitbucket or Bamboo Data Center/Server customers can move to the Bitbucket Hybrid License, planned for early 2027, to retain self-managed Bitbucket beyond March 28, 2029. The existing standalone license route ends in 2029; without the Hybrid License transition, instances become read-only. Confirm eligibility, availability and renewal terms. Scope: Bitbucket Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life. Supporting source: Edition and license conditions — https://www.atlassian.com/migration/bitbucket-hybrid-license.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 10.2.9, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/stash.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Data+Center+10.2+release+notes.




### Security and lifecycle reviews

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

- Bitbucket Hybrid License transition (lifecycle): Bitbucket remains self-managed beyond 2029 through the Hybrid License. Atlassian plans availability in early 2027 for eligible existing Bitbucket/Bamboo customers. Scope: Bitbucket Data Center licensing; separate from the retirement of Jira and Confluence Data Center. Conditions: Eligibility and exact launch date must be confirmed; existing license availability changes on March 28, 2029. Action: Review the required license transition with Atlassian; do not infer unrestricted new-customer availability. Source: https://www.atlassian.com/migration/bitbucket-hybrid-license; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## CircleCI Server

Commercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.

- Listing: https://launchinyourcloud.com/directory/circleci-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial CircleCI Server license required.
- Licensing model: commercial-only
- Installation: Official Terraform-assisted infrastructure setup and Helm installation on Amazon EKS or Google GKE
- Architecture: Kubernetes-hosted CircleCI services with persistent data services, object storage, networking and machine-execution capacity
- Operations: Customer manages Kubernetes, networking, object storage, databases, secrets, TLS, execution capacity, backups, upgrades and the CircleCI Server license.
- Product website: https://circleci.com/pricing/server/
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers CircleCI Server, not CircleCI Cloud or cloud-connected self-hosted runners. EKS and GKE are the tested cloud environments; CircleCI labels Azure and DigitalOcean as untested. GKE Autopilot is unsupported. CircleCI Server currently supports GitHub Enterprise Cloud and GitHub Enterprise Server as version-control providers.

CircleCI Server is an enterprise self-hosted offering that requires a commercial license supplied during installation.

CircleCI Server runs persistent application and data-service workloads in a customer Kubernetes cluster and uses cloud object storage and provisioned execution capacity.


### Category fit

- devops: Provides self-hosted continuous integration and delivery pipelines, execution environments, policy controls and build infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://circleci.com/docs/server-admin/latest/installation/phase-1-gcp-prerequisites/ (checked 2026-11-16). 


### Cloud deployment evidence

- CircleCI Server on Amazon EKS (aws): https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/
  CircleCI documents preparing AWS networking, an EKS cluster, storage, permissions and other prerequisites before installing CircleCI Server with its Helm chart.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 4.10.

- CircleCI Server on Google GKE (gcp): https://circleci.com/docs/server-admin/latest/installation/phase-1-gcp-prerequisites/
  CircleCI documents preparing a customer GCP project, VPC, GKE cluster, Cloud Storage and workload identity before installing CircleCI Server. The guide states that GKE Autopilot is unsupported.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 4.10.


### Sources

- CircleCI Server 4.10 overview: https://circleci.com/docs/server-admin/latest/overview/circleci-server-overview/

- CircleCI Server AWS prerequisites: https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/

- CircleCI Server GCP prerequisites: https://circleci.com/docs/server-admin/latest/installation/phase-1-gcp-prerequisites/

- CircleCI Server installation reference: https://circleci.com/docs/server-admin/latest/installation/installation-reference/

- CircleCI Server plan and hosting model: https://circleci.com/pricing/server/

### Licensing sources

- https://circleci.com/pricing/server/

- https://circleci.com/docs/server-admin/latest/installation/installation-reference/

### Infrastructure sources

- https://circleci.com/docs/server-admin/latest/overview/circleci-server-overview/

- https://circleci.com/docs/server-admin/latest/installation/installation-reference/


### Buyer diligence


Research coverage: 11/12 fields (92%); 7 documented, 4 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 reviewed vendor AWS listing is titled Cloud-Hosted CICD, while its description also mentions Server and customized packages. The public terms do not establish the exact self-hosted Server entitlement; confirm a Server-specific contract before purchase. Scope: Mixed-offering Marketplace description; Server contract coverage remains unresolved. Source: https://aws.amazon.com/marketplace/pp/prodview-puu7lb34aqr66 (reviewed 2026-11-16).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Server uses GitHub or GitHub Enterprise as its identity provider. GitHub Enterprise can federate authentication through SAML; configure that upstream identity boundary rather than assuming a direct CircleCI SAML integration. Scope: CircleCI Server 4.10; GitHub identity integration. Source: https://circleci.com/docs/server-admin/latest/operator/operator-overview/ (reviewed 2026-11-16).

- SCIM provisioning: Sources checked — unresolved. The operator guide describes SCIM at the GitHub Enterprise identity-provider layer. It does not establish a direct CircleCI SCIM endpoint or the full lifecycle behavior inside Server. Scope: Delegated GitHub Enterprise provisioning; direct Server SCIM remains unconfirmed. Source: https://circleci.com/docs/server-admin/latest/operator/operator-overview/ (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. CircleCI publishes corporate SOC 2/FedRAMP claims and offers security reports. The public page does not establish the current report period or assurance scope for a customer-operated Server deployment; obtain the report and map the customer’s responsibilities. Scope: Vendor security-program claims versus the customer-operated CircleCI Server boundary. Source: https://circleci.com/security/ (reviewed 2026-11-16).

- Security controls: Documented. The Server hardening guide recommends private resources, permits VPN-only access without public IPs, and requires Nomad client/server mTLS. Job SSH exposure and firewall/security-group rules need deliberate configuration; the documentation is guidance, not proof the installed cluster already enforces it. Scope: Server 4.10 Kubernetes/Nomad/VM network hardening. Source: https://circleci.com/docs/server-admin/latest/installation/hardening-your-cluster/ (reviewed 2026-11-16).

- Air-gapped operation: Documented. CircleCI documents a disconnected installation with a local container registry, Kubernetes, S3-compatible storage, GitHub Enterprise and Nomad VMs. Transfer all required release images and charts before installation; follow the remaining configuration and test phases. Scope: CircleCI Server documented air-gapped installation. Source: https://circleci.com/docs/server-admin/latest/air-gapped-installation/phase-1-prerequisites/ (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The Helm chart is distributed through cciserver.azurecr.io. The linked helper enumerates chart images for transfer to a private registry; it is not the chart or a complete infrastructure template. Select a compatible Server/chart release and use CircleCI-provided registry credentials. Scope: Server 4.10 air-gap preparation; guide example chart 4.10.1. Source: https://circleci.com/docs/server-admin/latest/air-gapped-installation/phase-1-prerequisites/ (reviewed 2026-11-16). Deployment artifact: https://github.com/CircleCI-Public/server-scripts/blob/main/air-gap/extract-images-from-helm-chart.sh. Artifact reference: main (moving branch; guide example chart 4.10.1).

- Minimum footprint / sizing: Documented. The Server 4.10 AWS guide specifies at least four Kubernetes nodes, 24 CPU cores and 90 GB total RAM below 500 daily active users; 500+ users require six nodes, 48 cores and 240 GB. Job-execution capacity and external services require separate sizing. Scope: Server 4.10 control/application cluster on AWS; not a total build-fleet or cost estimate. Source: https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/ (reviewed 2026-11-16).

- License pricing: Documented. CircleCI Server is an enterprise self-hosted offering that requires a commercial license supplied during installation. Scope: CircleCI Server: software license terms; infrastructure and operating costs are separate. Source: https://circleci.com/pricing/server/ (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://circleci.com/docs/server-admin/latest/installation/installation-reference/.

- Operating cost estimate: Sources checked — unresolved. The vendor identifies execution workers, per-job machine instances, Kubernetes capacity, artifacts/caches and block storage as cost drivers, and recommends retention, tagging and budget monitoring. It does not establish a workload- and region-specific operating total; concurrency, job duration, instance choices, retention and staffing still need a budget model. Scope: Public cost-driver guidance; no dated infrastructure-and-operations estimate. Source: https://circleci.com/docs/server-admin/latest/operator/resource-consumption-cost-management/ (reviewed 2026-11-16).

- Release snapshot / cadence: Documented. The reviewed vendor release is 4.10.1, published 2026-08-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Scope: CircleCI Server release; review MongoDB and other upgrade prerequisites; source supplies a publication day, not a timestamp. Source: https://circleci.com/changelog/server-release-4-10-1/ (reviewed 2026-11-16).







## CloudBees CI on Modern Cloud Platforms

Enterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.

- Listing: https://launchinyourcloud.com/directory/cloudbees-ci-modern-cloud-platforms/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial CloudBees CI license required.
- Licensing model: commercial-only
- Installation: CloudBees Helm chart on EKS, AKS or GKE
- Architecture: CloudBees operations center and managed controllers in the customer Kubernetes cluster.
- Operations: Customer provisions and operates Kubernetes, storage, networking, ingress, DNS, certificates and upgrades; CloudBees supports the licensed application within documented boundaries.
- Product website: https://www.cloudbees.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 CloudBees CI on modern cloud platforms, not plain Jenkins or a CloudBees-hosted service. CloudBees publishes separate EKS, AKS and GKE paths and a strict platform/version support matrix. Each standalone controller requires a valid license. CloudBees CI 2.580.2.38435 is the October 29 security release. Java 17 has been unsupported since 2.555.1.36485, so migrate controllers and agents to Java 21; Blue Ocean and Team controllers reached end of life in July 2026.

CloudBees CI is proprietary licensed software; operations center and standalone controllers require valid CloudBees licensing. Upstream Jenkins is a separate product.

The application runs as persistent Kubernetes workloads, including an operations center and managed controllers, in the customer's cluster.


### Category fit

- devops: Centrally managed enterprise continuous integration and delivery environment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (checked 2026-11-17). 


### Cloud deployment evidence

- CloudBees CI installation on EKS, AKS and GKE (aws, azure, gcp): https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro
  CloudBees provides product installation guides for Amazon EKS, Azure AKS and Google GKE, and its supported-platform matrix lists all three. The customer operates the Kubernetes cluster.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- CloudBees CI installation index: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro

- Modern cloud platform onboarding: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-onboarding

- Supported Kubernetes platforms and versions: https://docs.cloudbees.com/docs/cloudbees-common/latest/supported-platforms/cloudbees-ci-cloud

- CloudBees CI administration and licensing: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/

- CloudBees CI release notes: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/

### Licensing sources

- https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/

### Infrastructure sources

- https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro

- https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-onboarding


### 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: Documented. CloudBees identifies CI availability through AWS Marketplace, including a separate GovCloud marketplace route. Confirm the CI offer, subscription and delivery terms rather than substituting CodeShip or Unify listings. Scope: Vendor CI procurement statement; offer details must be selected. Source: https://www.cloudbees.com/partners/platform/aws (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The AWS partnership page establishes CI procurement availability, but not qualifying charges or committed-spend treatment under a buyer agreement. Scope: Reviewed public evidence for CloudBees CI on Modern Cloud Platforms; unresolved within this edition/deployment. Source: https://www.cloudbees.com/partners/platform/aws (reviewed 2026-11-17).

- Single sign-on: Documented. CloudBees CI documents SAML authentication with the supported SAML plugin and IdP metadata. Group attributes can inform RBAC, but the plugin does not synchronize external groups or roles. Scope: CloudBees CI SAML security realm. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The SAML guide explicitly separates authentication and group assertions from external group/role synchronization. A supported CI SCIM lifecycle endpoint was not established; CloudBees Unify or generic Jenkins plugins are insufficient evidence. Scope: CloudBees CI, not Unify or community plugins. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed CloudBees CI on Modern Cloud Platforms material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup (reviewed 2026-11-17).

- Security controls: Documented. Configure the SAML security realm and CloudBees RBAC separately; signing/encryption and IdP attributes must match the configured trust. Use supported plugins and current security fixes. Current advisory review: CloudBees CI 2.580.2.38435 contains security updates and is on the Java 21-supported line. Upgrade to 2.580.2.38435 or later, migrate to Java 21, and retire end-of-life controller types. Scope: CI authentication and authorization configuration CloudBees CI modern cloud platforms release 2.580.2.38435; component applicability follows the vendor release notes.. Source: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup.

- Air-gapped operation: Sources checked — unresolved. CloudBees documents an update-center mirror for plugin management in air-gapped environments. That establishes a plugin-transfer mechanism, but not every licensing, image, agent and upgrade dependency for a fully isolated deployment. Scope: CI plugin mirror; complete offline deployment remains to be established. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/casc-plugin-management/alternate-plugin-download-site (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The modern-platform installation index provides Helm deployment paths for EKS, AKS and GKE. The AWS partnership page also links a CI EKS Blueprints add-on; configure storage, ingress and controllers for the selected supported platform. Scope: CloudBees CI modern cloud platforms. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The AWS reference architecture sizes operations center, managed controllers and build agents separately. Its examples are recommendations rather than universal requirements; build concurrency and agent workloads drive capacity. Scope: AWS Kubernetes reference architecture; not an HA capacity guarantee. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-reference-architecture/ra-for-aws/ (reviewed 2026-11-17).

- License pricing: Documented. CloudBees CI is proprietary licensed software; operations center and standalone controllers require valid CloudBees licensing. Upstream Jenkins is a separate product. Scope: CloudBees CI on Modern Cloud Platforms: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm controllers, operations center, build agents, concurrency and licence/support scope. Worker VM hours and artifact storage cannot be inferred from a 100-user headcount. 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://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-reference-architecture/ra-for-aws/ (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. CloudBees CI 2.580.2.38435 was released October 29, 2026 with security updates. Java 21 is required for supported current releases; Blue Ocean and Team controllers are end of life. Scope: CloudBees CI modern cloud platforms. Source: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/ (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- CloudBees CI October 2026 security update (security-advisory): CloudBees CI 2.580.2.38435 contains security updates and is on the Java 21-supported line. Scope: CloudBees CI modern cloud platforms release 2.580.2.38435; component applicability follows the vendor release notes. Conditions: Installed plugins, controller type, and Java runtime determine applicability and upgrade sequencing. Action: Upgrade to 2.580.2.38435 or later, migrate to Java 21, and retire end-of-life controller types. Source: https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/; reviewed 2026-11-18.




## GitHub Enterprise Server

Customer-operated GitHub software-development platform deployed as a licensed virtual appliance.

- Listing: https://launchinyourcloud.com/directory/github-enterprise-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial GitHub Enterprise license required.
- Licensing model: commercial-only
- Installation: Official virtual-machine image on AWS, Azure or Google Cloud
- Architecture: Customer-operated appliance VM with persistent data storage and optional high-availability nodes
- Operations: Customer provisions infrastructure and manages networking, storage, backups, upgrades, monitoring and high availability.
- Product website: https://github.com/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers GitHub Enterprise Server, not GitHub Enterprise Cloud. A valid license file is required. Review supported instance types, storage, backup utilities, upgrade paths and version support before deployment. GitHub Enterprise Server 3.22.4 fixes critical Active Storage file-read and remote-code-execution CVE-2026-66066, several high-severity Git vulnerabilities, and Brotli CVE-2026-111497. Upgrade to 3.22.4 or a later supported patch. GitHub Enterprise Server 3.22.5 adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Follow the documented upgrade path and reapply custom firewall rules when required.

GitHub Enterprise Server requires a purchased GitHub Enterprise license file that controls access and licensed users.

The platform runs as one or more persistent virtual-machine appliances with attached data storage. Customer-cloud placement does not remove appliance sizing, backup, upgrade or availability responsibilities. GHES upgrades remove custom firewall rules; reapply any custom rules after upgrading.


### Category fit

- devops: Provides customer-operated source control, pull requests, collaboration and software delivery workflows as a licensed virtual appliance.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform (checked 2026-11-14). 


### Cloud deployment evidence

- GitHub Enterprise Server on AWS (aws): https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws
  GitHub documents launching its published appliance image on EC2 and attaching an EBS data volume in the customer's AWS account.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- GitHub Enterprise Server on Azure (azure): https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure
  GitHub documents deploying the appliance to a supported Azure VM with premium storage in the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- GitHub Enterprise Server on Google Cloud (gcp): https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform
  GitHub documents deploying its appliance image to a supported Compute Engine VM with persistent disks in the customer's project.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- GitHub Enterprise Server overview: https://docs.github.com/en/enterprise-server@latest/admin/overview/about-github-enterprise-server

- AWS installation: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws

- Azure installation: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure

- Google Cloud installation: https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform

- Enterprise Server license files: https://docs.github.com/en/enterprise-server@latest/billing/concepts/enterprise-billing/ghes-license-files

- GitHub Enterprise Server 3.22 release notes: https://docs.github.com/en/enterprise-server@3.22/admin/release-notes

### Licensing sources

- https://docs.github.com/en/enterprise-server@latest/billing/concepts/enterprise-billing/ghes-license-files

### Infrastructure sources

- https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance

- https://docs.github.com/en/enterprise-server@latest/admin/overview/about-github-enterprise-server

- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The versioned appliance overview documents external authentication with CAS, LDAP or SAML. Authentication, identity-provider reachability and account lifecycle need configuration. Scope: GitHub Enterprise Server 3.22 appliance; not GitHub.com Enterprise Cloud. Source: https://docs.github.com/en/enterprise-server@3.22/admin/overview/about-github-enterprise-server (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official AWS guide deploys the GitHub Enterprise Server appliance AMI into a customer VPC with configured instance, storage and security groups. Select the release-specific regional AMI and supply the Enterprise licence; this is a vendor appliance deployment guide rather than a public Terraform module. Scope: Official GHES 3.21 AWS appliance installation. Source: https://docs.github.com/en/enterprise-server%403.21/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws (reviewed 2026-11-20). Deployment artifact: https://enterprise.github.com/releases. Artifact reference: Release-specific regional image; choose a supported GHES version.

- Minimum footprint / sizing: Documented. The GHES 3.21 AWS guide recommends 8 x86-64 vCPUs, 48 GB RAM, 400 GB root and 500 GB data disk at 3,000 IOPS for up to 1,000 user licences. Its 4-vCPU/32-GB tier is trial/demo or ten light users. Actions, code security, growth and HA replicas require extra resources. Scope: GHES 3.21 AWS sizing by licensed users; feature and HA overhead additional. Source: https://docs.github.com/en/enterprise-server%403.21/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws (reviewed 2026-11-20).

- License pricing: Documented. A GitHub Enterprise account can include both Server and Cloud under enterprise licensing, with unique users counted across deployments when usage is synchronized. The appliance requires a licence file; agree seats, billing model and optional security products. This is not a hosting or runner-cost quote. Scope: GitHub Enterprise licensing across Server/Cloud; infrastructure additional. Source: https://docs.github.com/en/enterprise-server@3.21/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. GitHub Enterprise Server 3.22.5 was released November 17, 2026. It adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Scope: GitHub Enterprise Server 3.22 appliance line. Source: https://docs.github.com/en/enterprise-server@3.22/admin/release-notes (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- GitHub Enterprise Server appliance security patch (security-advisory): GHES 3.22.4 patches Active Storage file-read/code-execution, Git and Brotli vulnerabilities. Scope: GitHub Enterprise Server 3.22.4 security release; other supported lines need their own branch-specific patch guidance. Conditions: Appliance component and network exposure determine applicability. The release notes also identify dependency updates that are only partial remediations. Action: Install a patched supported appliance release, follow the upgrade sequence and reapply custom firewall rules where required. Source: https://docs.github.com/en/enterprise-server@3.22/admin/release-notes; reviewed 2026-11-17.




## GitLab Self-Managed

Source control and CI/CD on infrastructure you operate.

- Listing: https://launchinyourcloud.com/directory/gitlab/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, oci, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Free and paid tiers
- Licensing model: open-source
- Installation: Linux package, container or Helm chart
- Architecture: Customer-operated application and storage
- Operations: Your team operates, upgrades and backs up the installation.
- Product website: https://about.gitlab.com/
- Source review: 2026-11-20; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.

Community Edition uses MIT terms; Enterprise Edition adds components under a more restrictive commercial license.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- devops: Source control and CI/CD on infrastructure you operate.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab (checked 2026-11-12). 


### Cloud deployment evidence

- GitLab Self-Managed cloud installation guides (aws, azure, gcp): https://docs.gitlab.com/install/cloud_providers/
  The upstream installation index links full GitLab Self-Managed deployment on AWS, Azure and Google Cloud. Choose the Linux package, chart or reference architecture appropriate to the selected edition, scale and supported release; a GitLab Runner alone is not the GitLab application.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- GitLab Community Edition on Alibaba Cloud ECS (alibaba): https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab
  Alibaba documents GitLab Community Edition Docker deployment on Alibaba Cloud Linux 3 ECS as well as older package-based examples. Use the Community Edition path for this listing; JiHu GitLab is a separately distributed edition and old CentOS examples are not a current production recommendation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Oracle GitLab application deployment in an OCI tenancy (oci): https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html
  Oracle explicitly documents the GitLab application VM, customer tenancy, region, compartment, compute and VCN configuration, and administrator login. This confirms the provider deployment model. Its linked quick-start architecture has been retired, so these instructions do not establish a currently maintained one-click stack; validate the installer and supported GitLab release before using the legacy automation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- GitLab cloud installation: https://docs.gitlab.com/install/cloud_providers/

- Alibaba Cloud deployment: https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab

- Licensing and edition terms: https://docs.gitlab.com/development/licensing/

- Oracle GitLab application deployment in an OCI tenancy: https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html

- GitLab critical patch release for CVE-2026-105437: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/

- GitLab 19.5.6 security patch release: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/

- GitLab 19.6.1 critical Ruby patch announcement: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1

- Upstream Ruby security advisory: https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/

### Licensing sources

- https://docs.gitlab.com/development/licensing/

### Infrastructure sources

- https://docs.gitlab.com/install/cloud_providers/

- https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab

- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/


### Buyer diligence


Research coverage: 10/12 fields (83%); 10 documented, 0 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: Edition-dependent. GitLab documents AWS Marketplace self-service/private offers and Google Cloud Marketplace private offers for paid subscriptions. Delivery/billing does not by itself change where a selected GitLab installation runs. Scope: Premium/Ultimate subscription procurement; self-hosting and SaaS offers must be distinguished. Source: https://about.gitlab.com/cloud-partner-marketplaces/ (reviewed 2026-11-14).

- Cloud commitment eligibility: Edition-dependent. GitLab states eligible cloud-marketplace purchases can count toward committed spend on AWS or Google Cloud. Confirm the specific offer, billing account and buyer agreement; this is not an unconditional credit guarantee. Scope: Vendor procurement statement; actual provider commitment terms govern eligibility. Source: https://about.gitlab.com/cloud-partner-marketplaces/ (reviewed 2026-11-14).

- Single sign-on: Documented. Instance-wide SAML SSO is documented for Self-Managed Free, Premium and Ultimate. Group SAML and advanced group mapping have separate tier requirements. Scope: GitLab Self-Managed instance authentication; not GitLab.com group SSO. Source: https://docs.gitlab.com/integration/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. SCIM is documented for Self-Managed Premium and Ultimate, with SAML configured. The API implements part of RFC7644; verify the supported identity provider and operations. Scope: GitLab Self-Managed / Dedicated, Premium and Ultimate. Source: https://docs.gitlab.com/administration/settings/scim_setup/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Documented. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series. Scope: GitLab Self-Managed CE/EE, including Linux packages, containers and self-compiled installations. The separate bundled Git fix has its own requirements.. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1 (reviewed 2026-11-20). Supporting source: Upstream Ruby security advisory — https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/.

- Air-gapped operation: Edition-dependent. Self-Managed Free, Premium and Ultimate have an offline installation workflow. Transfer the correct packages/images and handle scanners, AI and update dependencies separately. Scope: Documented offline Self-Managed configuration, not default online installation. Source: https://docs.gitlab.com/topics/offline/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The official self-managed guide publishes Compose YAML for versioned Community or Enterprise images with persistent configuration, logs and data. It warns against placing the all-in-one Docker image in Kubernetes; use the Helm chart/operator there. Configure hostname, TLS, secrets, backups and runner capacity separately. Scope: Official self-managed Docker/Compose installation. Source: https://docs.gitlab.com/install/docker/installation/ (reviewed 2026-11-20). Deployment artifact: https://docs.gitlab.com/install/docker/installation/#install-gitlab-by-using-docker-compose. Artifact reference: Select explicit version-ce.0 or version-ee.0 image tag.

- Minimum footprint / sizing: Documented. The single-node baseline is 8 vCPU and 16 GB RAM. A memory-constrained configuration can use at least 8 GB; distributed sizing is component- and workload-specific. Scope: Self-Managed single-node baseline; not a total production cost estimate. Source: https://docs.gitlab.com/install/requirements/ (reviewed 2026-11-14).

- License pricing: Documented. GitLab Self-Managed offers tier-based subscriptions applying to the whole instance; all instance users share the selected features. A GitLab.com subscription cannot be transferred to Self-Managed. Select the required tier, seats and add-ons; this does not establish a complete hosting/support cost. Scope: GitLab Self-Managed instance-wide commercial tiers. Source: https://docs.gitlab.com/subscriptions/choosing_subscription/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. GitLab published 19.6.1 on November 20, 2026, with parallel Ruby security patches 19.5.8 and 19.4.10. Scope: GitLab Self-Managed Community and Enterprise editions. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1 (reviewed 2026-11-20).




### Security and lifecycle reviews

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

- GitLab bundled Git command-execution advisory (security-advisory): CVE-2026-105437 concerns a Git heap-write flaw that can reach command execution inside Gitaly. Scope: GitLab CE/EE 16.2 to before 19.3.8, 19.4 to before 19.4.6, and 19.5 to before 19.5.4. Conditions: All installation types are covered unless the vendor identifies an exception. Source builds need both Gitaly-embedded Git and git.bin_path checked. Action: Install the patched release for the deployed branch. Rebuild the required Git binaries for source installations, or use a distribution fix for the CVE. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/; reviewed 2026-11-17.

- GitLab 19.5.6 security update (security-advisory): GitLab 19.5.6, 19.4.8, and 19.3.9 fix a high-severity cross-site scripting issue and authorization weaknesses in CI/CD and workspaces. Scope: GitLab CE/EE patch lines 19.3, 19.4, and 19.5; consult the vendor table for the affected versions. Conditions: Impact depends on enabled features, user roles, and exposed endpoints. This record does not replace the separate bundled-Git CVE review. Action: Upgrade to 19.5.6, 19.4.8, or 19.3.9 for the deployed branch, or a later supported patch. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/; reviewed 2026-11-18.

- GitLab critical bundled Ruby security update (security-advisory): GitLab updated bundled Ruby for CVE-2026-132825 and related upstream Ruby security issues. Scope: Self-managed GitLab CE/EE releases before 19.4.10, 19.5 releases before 19.5.8, and 19.6 releases before 19.6.1, per GitLab. Conditions: Official Linux packages and container images carry the fixed Ruby. Self-compiled installations manage Ruby separately. Action: Upgrade to 19.6.1, 19.5.8, or 19.4.10 as appropriate. For source builds, rebuild GitLab’s Ruby with 3.3.14, 3.4.13, or a later patch in the same minor series. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1; reviewed 2026-11-20. Supporting source: Upstream Ruby security advisory — https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/.




## Harbor

Container and OCI artifact registry for managing software images within customer-operated infrastructure.

- Listing: https://launchinyourcloud.com/directory/harbor/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Harbor.
- Licensing model: open-source
- Installation: Install Harbor on a Docker-capable host or use the documented high-availability Helm deployment on Kubernetes.
- Architecture: Customer-operated registry, API/UI and supporting database/storage services
- Operations: Customer manages artifact storage, database, TLS, identity, scanner configuration, replication, backups and upgrades.
- Product website: https://goharbor.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scanning, signing and replication depend on the components and endpoints configured. Sending images to a remote registry or scanner changes data boundaries. Harbor v2.15.5 bounds audit and manifest request bodies, enforces actual decompression byte limits, redacts sensitive pagination and upload locations in rejection errors, and updates dependencies for high-severity CVEs. Operators on the 2.15 line should upgrade to v2.15.5 or a later supported patch.

Apache License 2.0 for upstream Harbor. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated registry, API/UI and supporting database/storage services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- devops: Private registry for container and OCI artifacts with project permissions, artifact policies, replication and optional security integrations.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/harbor (checked 2026-11-12). Source: https://github.com/gridalpha/harbor-railway/blob/main/core/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Harbor community deployment on Railway (railway): https://railway.com/deploy/harbor
  The community recipe provisions Harbor core, portal, job service, registry, registry control, scanner and proxy roles with PostgreSQL, Redis and object storage. Its component wrappers derive from upstream Harbor images. Review consistent image versions, TLS, authentication, registry storage and scanning/update operations; community packaging does not imply CNCF or project support.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the Harbor Railway core wrapper (railway): https://github.com/gridalpha/harbor-railway/blob/main/core/Dockerfile
  The inspected core wrapper derives from the upstream goharbor/harbor-core image (v2.15.2). Review the corresponding versions and configuration of every Harbor component before deploying the full community template.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Harbor is a CNCF Graduated project with documented foundation oversight and continuing upstream release maintenance.

Reviewed 2026-11-10.

- CNCF graduation and project governance: https://www.cncf.io/projects/harbor/

- Current release history: https://github.com/goharbor/harbor/releases

### Sources

- Official installation and runtime: https://goharbor.io/docs/latest/install-config/

- Upstream project and capabilities: https://github.com/goharbor/harbor

- Current upstream license: https://github.com/goharbor/harbor/blob/main/LICENSE

- Registry functionality: https://goharbor.io/

- Harbor v2.15.5 security hardening and dependency updates: https://github.com/goharbor/harbor/releases/tag/v2.15.5

### Licensing sources

- https://github.com/goharbor/harbor/blob/main/LICENSE

### Infrastructure sources

- https://goharbor.io/docs/latest/install-config/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Harbor 2.15 documents OIDC browser login and group claims. Choose the authentication mode before adding ordinary local users; Docker/Helm clients use a CLI secret rather than interactive OIDC redirects. Scope: Harbor 2.15 OIDC UI and separate registry CLI authentication. Source: https://goharbor.io/docs/2.15.0/administration/configure-authentication/oidc-auth/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Harbor documents both a Docker-host installer and Kubernetes Helm deployment. Configure HTTPS, image storage and the supported dependency versions; HA has separate prerequisites. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://goharbor.io/docs/latest/install-config/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The Docker-host prerequisites list 2 CPUs, 4 GB RAM and 40 GB disk minimum, with 4 CPUs, 8 GB and 160 GB recommended. Image volume, scanning, retention and HA affect actual sizing. Scope: Harbor deployment prerequisites; not per-node HA sizing or a cost estimate. Source: https://goharbor.io/docs/latest/install-config/installation-prereqs/ (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/goharbor/harbor/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v2.15.5, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream goharbor/harbor release record; commercial editions and deployment packages may differ. Source: https://github.com/goharbor/harbor/releases/tag/v2.15.5 (reviewed 2026-11-14).







## HashiCorp Consul Enterprise

Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/hashicorp-consul-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Consul Enterprise license required for the selected validated design.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud
- Architecture: Customer-operated Consul server quorum and clients with provider load balancers, KMS, secrets and snapshot storage.
- Operations: Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.
- Product website: https://www.hashicorp.com/en/products/consul
- 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 Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.

Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.

Consul Enterprise runs persistent server and client agents on customer infrastructure with consensus state, snapshots and network dependencies.


### Category fit

- backend-platforms: Provides service discovery, configuration, connectivity and service-mesh control for distributed application platforms.

- devops: Automates service networking, health discovery and policy across deployment environments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (checked 2026-11-17). 


### Cloud deployment evidence

- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform
  HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Consul Enterprise using Terraform on AWS, Azure and Google Cloud: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform

- Consul pricing and editions: https://www.hashicorp.com/en/products/consul/pricing

- HCSEC-2026-49: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914

- HCSEC-2026-50: https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915

### Licensing sources

- https://www.hashicorp.com/en/products/consul/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 reviewed Enterprise pricing and Terraform deployment establish the licensed product, but not a current Consul Enterprise-specific Marketplace offer. HCP procurement is separate. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Consul Enterprise price/edition material did not establish qualifying Marketplace charges and commitment treatment for the buyer agreement. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The OIDC authentication method requires self-managed Consul Enterprise 1.8.0+. It supports browser-based UI/CLI login through a configured IdP, with ACL tokens and claim mappings. Scope: Self-managed Consul Enterprise, not HCP account SSO. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise OIDC exchanges claims for ACL tokens; it does not establish a SCIM user/group lifecycle endpoint. HCP account SCIM was excluded. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Consul Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Security controls: Documented. The Enterprise Terraform workflow configures cluster secrets and cloud permissions. Apply ACL, TLS/gossip, backup and key-management requirements rather than treating provisioning completion as a security review. Current advisory review: HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Scope: Consul Enterprise deployment controls Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Consul Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/consul/docs/enterprise/license/reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design provides provider-specific Terraform deployment for Consul Enterprise on AWS, Azure and Google Cloud. Configure the licence, secrets, network access and snapshot storage before production use. Scope: Self-managed Enterprise validated Terraform deployment. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The design deploys a fault-tolerant Consul server cluster; service count, agent placement, traffic, mesh gateways and availability requirements determine total capacity. Human-user count does not size the service mesh. Scope: Consul topology and workload boundary. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- License pricing: Documented. Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement. Scope: HashiCorp Consul Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify service/agent count, mesh traffic, gateways and Enterprise server topology. Human users and 1 TB application data do not size a Consul service mesh. 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://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.0+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-22. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/consul/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/consul/2.1.0+ent/.




### Security and lifecycle reviews

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

- HashiCorp Consul authorization-bypass updates (security-advisory): HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Scope: Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18. Conditions: Health-check registration permissions and Kubernetes component ACL binding rules determine exposure. Action: Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914; reviewed 2026-11-18. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.




## HashiCorp Nomad Enterprise

Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules where available or manual package and binary installation
- Architecture: Customer-operated Nomad server quorum and client nodes with persistent state, networking and workload drivers.
- Operations: Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/nomad
- 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 scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.

Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.

Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.


### Category fit

- devops: Schedules and operates application, batch and system workloads across customer infrastructure.

- workflow-orchestration: Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment
  HashiCorp's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Nomad validated cloud deployment: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment

- Nomad pricing and editions: https://www.hashicorp.com/en/products/nomad/pricing

- HCSEC-2026-51: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929

- HCSEC-2026-52: https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930

- HCSEC-2026-53: https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931

### Licensing sources

- https://www.hashicorp.com/en/products/nomad/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. Nomad documents OIDC SSO through external IdPs with ACL policies, roles and binding rules. Human and machine authentication are different flows; short-lived ACL tokens replace distributing static tokens. Scope: Self-managed Nomad Enterprise identity design. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Nomad OIDC maps identity claims to short-lived ACL tokens. A Nomad Enterprise SCIM lifecycle service was not established; HCP Terraform SCIM is a different product. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Nomad Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Security controls: Documented. The validated identity design requires appropriate ACL policies and mapped roles. Protect management tokens, configure TLS/gossip and snapshot recovery, and isolate workload client permissions from server administration. Current advisory review: HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Upgrade the installed maintained Enterprise branch to the listed fixed or later build. Scope: Nomad customer-managed cluster controls Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929 (reviewed 2026-11-18). Supporting source: Identity and access management — https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management. Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Nomad Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/nomad/docs/enterprise/license/utilization-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design documents customer-cloud Nomad installation on AWS, Azure and Google Cloud with servers, clients, networking and enterprise licensing. Review the design and pin the chosen deployment tooling before applying it. Scope: Self-managed Enterprise validated cloud design. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The cloud design separates voting/non-voting servers from workload clients across availability zones. Server count alone does not size user jobs, 1 TB application data, storage plugins or client failover capacity. Scope: Nomad cluster topology versus workload capacity. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- License pricing: Documented. Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support. Scope: HashiCorp Nomad Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 864.96/month. Six 4-vCPU/16-GiB server VMs follow the validated three-voting/three-non-voting design, with 50 GB gp3 each. This prices the control plane only; workload clients and their 1 TB data are unpriced. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Nomad Enterprise server control-plane subtotal; 100 identities do not size jobs, task concurrency or workload clients. Price applications and replicated workload storage separately.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-29. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/nomad/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/nomad/2.1.1+ent/.




### Security and lifecycle reviews

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

- HashiCorp Nomad Enterprise October 2026 security updates (security-advisory): HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Scope: Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18. Conditions: Namespace permissions, dispatch payload writes, allocation migration, and symlink handling determine exposure. Action: Upgrade the installed maintained Enterprise branch to the listed fixed or later build. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929; reviewed 2026-11-18. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.




## Jenkins

Automation server for building, testing and delivering software through configured pipelines.

- Listing: https://launchinyourcloud.com/directory/jenkins/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses.
- Licensing model: open-source
- Installation: Run the official Jenkins Docker image or supported server package and attach appropriately isolated build agents.
- Architecture: Customer-operated Jenkins controller and build agents with persistent configuration
- Operations: Customer manages controller and agents, plugins, secrets, job permissions, storage, backups and security updates.
- Product website: https://www.jenkins.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Pipeline code, agents and plugins can access external source hosts, registries and deployment targets. A controller installed in an account does not contain every pipeline integration. Jenkins weekly 2.591 enables Content Security Policy enforcement on the Jenkins UI by default. Test installed plugins and custom UI integrations before adopting this weekly release; compatibility is tracked upstream. Administrators can use report-only mode while resolving incompatibilities, but disabling enforcement removes the protection.

MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Jenkins controller and build agents with persistent configuration. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- devops: Automation server for continuous integration, build, test and delivery pipelines; agents and plugins provide workload-specific integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/developer/jenkins/configure-on-linux-vm (checked 2026-11-12). 


### Cloud deployment evidence

- Jenkins installation on AWS (aws): https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/
  The Jenkins project documents installing the Jenkins server on a customer EC2 instance, not merely deploying build output to AWS.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Jenkins installation on an Azure Linux VM (azure): https://learn.microsoft.com/en-us/azure/developer/jenkins/configure-on-linux-vm
  Microsoft documents installing Jenkins on an Ubuntu VM in the customer subscription. Harden public access and review the current Jenkins and Java versions rather than copying old version pins.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Jenkins publishes community governance, contributor recognition and a release changelog updated in November 2026; these show sustained maintenance and community participation.

Reviewed 2026-11-10.

- Project governance: https://www.jenkins.io/project/governance/

- Current release changelog: https://www.jenkins.io/changelog/

- Community contributor recognition: https://www.jenkins.io/

### Sources

- Official installation and runtime: https://www.jenkins.io/doc/book/installing/docker/

- Upstream project and capabilities: https://github.com/jenkinsci/jenkins

- Current upstream license: https://www.jenkins.io/license/

- Jenkins weekly 2.591 release: https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.591

- Jenkins CSP default and upgrade guidance: https://github.com/jenkinsci/jenkins/pull/27727

### Licensing sources

- https://www.jenkins.io/license/

### Infrastructure sources

- https://www.jenkins.io/doc/book/installing/docker/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The security guide documents delegating authentication to an external identity provider using SAML/OIDC. The relevant plugins are not necessarily installed; match supported plugin/controller versions and configure authorization separately. Scope: Jenkins plugin-based security realm; not automatic core federation. Source: https://www.jenkins.io/doc/book/security/managing-security/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The installation guide identifies the official Jenkins image and persistent controller home. Build agents, privileged Docker access, plugins and workload resources require a separate security/capacity plan. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.jenkins.io/doc/book/installing/docker/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/jenkins/jenkins. Artifact reference: select an LTS or weekly versioned image tag.

- Minimum footprint / sizing: Documented. The guide lists 256 MB RAM and 1 GB disk as basic minima, with 10 GB suggested for Docker. A small team is recommended 4 GB+ RAM and 50 GB+ disk; build-agent resources are separate. Scope: Controller baseline, not total CI/build infrastructure. Source: https://www.jenkins.io/doc/book/installing/docker/ (reviewed 2026-11-14).

- License pricing: Documented. Jenkins core is MIT licensed. Plugins and bundled components have their own licences; commercial distributions, support, agents and infrastructure are separate costs. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/jenkinsci/jenkins/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is jenkins-2.591, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream jenkinsci/jenkins release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.591 (reviewed 2026-11-17).







## JFrog Artifactory Self-Hosted

Universal artifact repository installed on Kubernetes clusters or servers you operate.

- Listing: https://launchinyourcloud.com/directory/jfrog-artifactory-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source Artifactory OSS; commercial Pro X, Enterprise X and Enterprise+ editions.
- Licensing model: open-source
- Installation: Helm chart, Docker or Docker Compose, or native OS package or archive
- Architecture: Customer-operated Artifactory service with persistent filestore and database.
- Operations: Customer operates the cluster or servers, database, filestore, backups, upgrades and availability configuration.
- Product website: https://jfrog.com/artifactory/
- 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 Artifactory, not JFrog SaaS. Edition capabilities differ substantially: Artifactory OSS is limited and does not include cloud object storage, while high availability and broader repository, security and platform capabilities require the applicable commercial entitlement. Production deployments should use an external PostgreSQL database and durable filestore. The separate Amazon ECS path is single-node, limited to 16 vCPUs and cannot connect to Xray or Distribution. CVE-2026-82329 is a critical unauthenticated authentication bypass under default configuration. JFrog lists fixed builds across maintained branches, including 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21; move to a fixed or later supported build.

JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits.

Artifactory runs as server or container workloads with persistent database and filestore dependencies; the listed Helm path uses customer-operated Kubernetes infrastructure.


### Category fit

- devops: Artifact, package and container registry for software delivery pipelines.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Artifactory Helm installation on EKS, AKS and GKE (aws, azure, gcp): https://docs.jfrog.com/installation/docs/helm-charts
  JFrog's current Artifactory Helm guide explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as cluster types and documents installation into the customer's cluster. Provider storage, database, ingress and support details vary by edition.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Artifactory installation with Helm charts: https://docs.jfrog.com/installation/docs/helm-charts

- Artifactory installation methods and Amazon ECS limits: https://docs.jfrog.com/installation/docs/installing-artifactory

- Self-managed edition feature comparison: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds

- JFrog open-source offerings: https://jfrog.com/community/open-source/

- JFrog security advisories: https://docs.jfrog.com/releases/docs/jfrog-security-advisories

- Artifactory release notes: https://docs.jfrog.com/releases/docs/artifactory-release-notes

### Licensing sources

- https://jfrog.com/community/open-source/

- https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds

### Infrastructure sources

- https://docs.jfrog.com/installation/docs/helm-charts

- https://docs.jfrog.com/installation/docs/installing-artifactory


### Buyer diligence


Research coverage: 12/12 fields (100%); 10 documented, 2 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: Edition-dependent. The self-hosted subscription agreement explicitly permits procurement through supported cloud marketplaces, with fees and terms in the offer/order form. This is software procurement, not proof that a SaaS offer deploys in the buyer account. Scope: Self-hosted subscription procurement. Source: https://jfrog.com/self-hosted-terms-and-conditions-10-01-2024/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Edition-dependent. JFrog states approved cloud Marketplace purchases can draw down committed spend. Obtain confirmation for the self-hosted offer and buyer agreement; this is a conditional procurement statement, not universal credit eligibility. Scope: JFrog Marketplace purchasing; provider contract and selected offer govern. Source: https://jfrog.com/cloud/ (reviewed 2026-11-17). Supporting source: Self-hosted Marketplace contracting — https://jfrog.com/self-hosted-terms-and-conditions-10-01-2024/.

- Single sign-on: Edition-dependent. SAML SSO is included from Pro X, including Enterprise X and Enterprise+; it is excluded from the non-commercial editions in the reviewed matrix. Scope: Self-managed Artifactory edition matrix. Source: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds (reviewed 2026-11-17). Supporting source: SAML configuration — https://docs.jfrog.com/administration/docs/saml-sso.

- SCIM provisioning: Edition-dependent. SCIM identity management is included in Enterprise X and Enterprise+, and excluded from Pro X and non-commercial editions. The API uses the Access SCIM v2 endpoint and a restricted identity-management token. Scope: Self-managed Enterprise X / Enterprise+. Source: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds (reviewed 2026-11-17). Supporting source: SCIM endpoint and token permissions — https://docs.jfrog.com/administration/docs/scim.

- Compliance attestations: Sources checked — unresolved. The reviewed JFrog Artifactory Self-Hosted material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds (reviewed 2026-11-17).

- Security controls: Documented. The edition matrix distinguishes LDAP/RBAC from paid SAML, identity management, HA and scanning features. Xray and Advanced Security are separately entitled capabilities; do not assume the free Artifactory distribution includes them. Current advisory review: CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments. Upgrade to the fixed or later supported build for the installed branch and review administrative access. Scope: Self-managed component and feature entitlements; not an attestation JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches.. Source: https://docs.jfrog.com/releases/docs/jfrog-security-advisories (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds.

- Air-gapped operation: Edition-dependent. Artifactory 7.77+ documents an air-gap setting and offline entitlement-file workflow. Obtain and renew the correct entitlement files and stage all dependencies; the 14-day license grace period can end in service disruption. Scope: Licensed self-managed air-gap configuration. Source: https://docs.jfrog.com/installation/docs/configure-jfrog-platform-in-an-air-gapped-environment (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. JFrog supplies Helm installation paths for EKS, AKS and GKE. Configure master/join keys, persistent storage and the database, and pin compatible chart/application versions rather than treating Helm defaults as production sizing. Scope: Self-managed Artifactory Helm installation. Source: https://docs.jfrog.com/installation/docs/helm-charts (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Artifactory sizing is based on active clients: the baseline starts at 4 cores/6 GB RAM for up to 20 clients, rising to 8 cores/18 GB for 101–200 clients. Database, HA, Xray and storage are additional sizing decisions. Scope: Artifactory active-client matrix; users are not necessarily simultaneous clients. Source: https://docs.jfrog.com/installation/docs/hardware-sizing-matrix (reviewed 2026-11-17).

- License pricing: Documented. JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits. Scope: JFrog Artifactory Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://jfrog.com/community/open-source/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Determine active artifact clients, package traffic, HA edition, database/filestore design and whether Xray/Workers are included. A 100-person headcount does not determine concurrent repository clients or scanning load. 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://docs.jfrog.com/installation/docs/hardware-sizing-matrix (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed current self-managed Artifactory release is 7.173.21. Older maintained branches have separate CVE-2026-82329 fixed builds; verify the selected branch before upgrading. Scope: JFrog Artifactory self-managed release notes. Source: https://docs.jfrog.com/releases/docs/artifactory-release-notes (reviewed 2026-11-18). Supporting source: Self-managed lifecycle policy — https://docs.jfrog.com/releases/docs/artifactory-end-of-life.




### Security and lifecycle reviews

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

- JFrog Artifactory unauthenticated authentication bypass (security-advisory): CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments. Scope: JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches. Conditions: The vendor identifies default configuration as affected; exact branch applicability follows the advisory matrix. Action: Upgrade to the fixed or later supported build for the installed branch and review administrative access. Source: https://docs.jfrog.com/releases/docs/jfrog-security-advisories; reviewed 2026-11-18.




## Jira Service Management Data Center

Commercial self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/jira-service-management-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based Jira Data Center installation
- Architecture: Single-node or clustered Jira Service Management application nodes with an external database, load balancer, shared home, indexes and optional dedicated nodes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, email, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/jira/service-management/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Jira Service Management Data Center, not Atlassian Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Service Management Data Center versions before the fixed 5.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Jira Service Management Data Center runs persistent Jira application services with durable database, shared-home and local-index storage.


### Category fit

- customer-support: Provides self-managed service desks, request portals, queues, knowledge integration and service-management workflows.

- devops: Supports IT service management, incident response, change coordination and development-to-operations workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (checked 2026-11-16). 


### Cloud deployment evidence

- Jira Service Management Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html
  Atlassian documents Jira Service Management Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Jira Data Center: https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html

- Run Jira Service Management Data Center on Kubernetes: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html

- Jira Service Management Data Center architecture: https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html

- https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 documented, 1 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The Data Center SSO guide explicitly covers Jira Service Management 5.15+. SAML login can include customer-portal logins when enabled; application access remains separately configured. Scope: Jira Service Management Data Center 5.15+; not Atlassian Guard cloud customer provisioning. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16).

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Jira Service Management Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The vendor’s 11.3.x extra-large benchmark uses three r5.8xlarge application nodes, 30 GB Java heap per node and a separate db.m6i.4xlarge PostgreSQL 16.9 database in AWS ap-southeast-2. Its dataset includes about 3.1 million issues and 6,471 agents. This is a test configuration, not a universal minimum or a performance/cost guarantee. Scope: JSM 11.3.x extra-large benchmark; representative workload sizing remains necessary. Source: https://confluence.atlassian.com/servicemanagement/jira-service-management-11-3-x-long-term-support-release-performance-report-1689289059.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Jira Service Management Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.3.13, released 2026-11-05. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/jira-servicedesk.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/SERVICEDESK/JIRA+Service+Management+11.3.x+release+notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## Jira Software Data Center

Commercial self-managed Jira Software edition deployed on customer-operated cloud or Kubernetes infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/jira-software-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Jira application nodes with an external database, load balancer, shared home, local indexes and optional dedicated nodes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/jira/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Jira Software Data Center, not Jira Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained, so they are not listed as current install methods. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Software Data Center versions before the fixed 9.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Jira Data Center runs persistent application nodes with durable database, shared-home and index storage; managed Kubernetes supplies the cluster control plane but not a serverless application runtime.


### Category fit

- project-management: Provides self-managed issue, project, planning and work-tracking capabilities for enterprise teams.

- devops: Supports software-delivery planning, issue tracking, release coordination and integrations with development toolchains.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (checked 2026-11-16). 


### Cloud deployment evidence

- Jira Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html
  Atlassian documents Jira Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Atlassian supports the product and Helm chart, but not the underlying Kubernetes platform.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Jira Data Center: https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html

- Run Jira Data Center on Kubernetes: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html

- Jira Data Center architecture and infrastructure: https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html

- https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 documented, 1 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Jira Software 8.15+; authentication does not assign application access or permissions. Scope: Jira Software 8.15+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Jira Software Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The installation guide, last modified in 2021, gives a multicore server with 8 GB available RAM for 100 projects, 1,000–5,000 issues and 100–200 users. This is a legacy small-installation example, not a current Data Center cluster minimum; size production nodes, supported database and storage separately. Scope: Legacy small-installation example; not a current Data Center production sizing recommendation. Source: https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Jira Software Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.3.13, released 2026-11-05. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/jira-software.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+11.3.x+release+notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## 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/.




## PagerDuty Runbook Automation Self-Hosted

Commercial runbook and operations-automation platform deployed as a customer-operated cluster in AWS.

- Listing: https://launchinyourcloud.com/directory/pagerduty-runbook-automation-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial PagerDuty Runbook Automation Self-Hosted license required; Rundeck Community is a separate Apache-2.0 edition.
- Licensing model: commercial-only
- Installation: Commercial RPM/DEB/WAR or official Docker image on customer AWS infrastructure; obtain a current licensed Helm artifact before using the older EKS recipe
- Architecture: Customer-operated Runbook Automation application with load balancing, database, object storage and execution nodes.
- Operations: Customer manages EKS or VMs, database, storage, networking, TLS, execution nodes, backups, upgrades and license delivery.
- Product website: https://www.pagerduty.com/platform/automation/runbook-automation/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

Commercial Runbook Automation Self-Hosted is distinct from PagerDuty SaaS and Rundeck Community. The EKS tutorial’s linked commercial Helm directory returned 404; use current licensed package/container documentation and obtain a pinned chart if needed. Official Docker images before 6.3.0 require the scoped CA trust-store remediation.

Runbook Automation Self-Hosted is commercial software requiring a license. Rundeck Community is separately Apache-2.0 licensed and is not the selected edition.

The AWS architectures run persistent application and execution services backed by customer database and object storage.


### Category fit

- workflow-automation: Automates operational runbooks, scheduled jobs and controlled actions through customer-operated execution services.

- devops: Provides operations automation, job orchestration, access control and integrations for delivery and incident workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.rundeck.com/docs/administration/install/aws.html (checked 2026-11-18). 


### Cloud deployment evidence

- Runbook Automation Self-Hosted on AWS (aws): https://docs.rundeck.com/docs/administration/install/aws.html
  PagerDuty documents a customer-operated HA architecture using AWS load balancing, RDS and S3; a separate guide deploys the product to customer EKS.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Deploy Runbook Automation on Amazon EKS: https://docs.rundeck.com/docs/learning/howto/how2-terra-rd-eks.html

- Runbook Automation Self-Hosted on AWS: https://docs.rundeck.com/docs/administration/install/aws.html

- Deploy Rundeck on AWS with Terraform: https://docs.rundeck.com/docs/learning/howto/how2-terra-rd-aws.html

- Runbook Automation licensing: https://docs.rundeck.com/docs/administration/license.html

- Rundeck and Runbook Automation editions: https://docs.rundeck.com/docs/about/introduction.html

### Licensing sources

- https://docs.rundeck.com/docs/administration/license.html

- https://docs.rundeck.com/docs/about/introduction.html

### Infrastructure sources

- https://docs.rundeck.com/docs/administration/install/aws.html


### 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 vendor confirms a separate commercial Self-Hosted product, but the reviewed PagerDuty Marketplace leads did not establish an exact offer entitling that software. SaaS subscriptions, professional services and remotely hosted runners are different scopes. Request the applicable self-hosted offer/order ID, seller, licence terms and current commercial artifact. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://www.pagerduty.com/platform/automation/process-software/ (reviewed 2026-11-18).

- Cloud commitment eligibility: Sources checked — unresolved. A commercial Runbook Automation licence file and AWS deployment do not establish cloud-commitment credit. Confirm the actual self-hosted order, procurement route and buyer agreement. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/license.html (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Edition-dependent. Runbook Automation’s commercial SSO integration uses OAuth2/OIDC authorization-code login, with configuration guidance for Okta, Ping and Azure AD and required signing-key discovery. Confirm identity/role mapping for the selected IdP; this is distinct from Rundeck Community authentication. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/security/sso/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The OIDC SSO guide does not establish a commercial self-hosted SCIM endpoint or user/group lifecycle. PagerDuty account provisioning and SSO profile synchronization are not evidence of Runbook Automation SCIM support. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/security/sso/ (reviewed 2026-11-18). Supporting source: Authentication providers are not a provisioning endpoint — https://docs.rundeck.com/docs/administration/security/authentication.html.

- Compliance attestations: Sources checked — unresolved. PagerDuty says Runbook Automation Self-Hosted can operate inside the customer firewall to meet stricter requirements such as FedRAMP. That is deployment/control guidance, not evidence that the self-hosted product or buyer’s automation system has that authorisation. Obtain the actual report/certificate and include local database, runners, plugins, job targets, identity and operations in the assessment. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://www.pagerduty.com/platform/automation/process-software/ (reviewed 2026-11-18).

- Security controls: Documented. The commercial SSO guide configures OIDC login and signing-key validation. Release 6.3.0 hardens webhook token storage and official container trust stores. Operators must separately control job permissions, key storage, runner credentials and target access. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/security/sso/ (reviewed 2026-11-18). Supporting source: 6.3.0 security changes — https://docs.rundeck.com/docs/history/6_x/version-6.3.0.html. Supporting source: Container CA trust-store advisory — https://docs.rundeck.com/docs/history/cves/2026-10-emudhra-ca.html.

- Air-gapped operation: Edition-dependent. PagerDuty explicitly identifies Runbook Automation Self-Hosted for air-gapped networks and operation entirely inside the customer’s infrastructure. Prepare the commercial application/runner/plugin artifacts, local database, identity, certificates and job targets. A valid commercial licence is still required; agree its offline issuance/renewal and expiry process rather than assuming the SaaS or cloud-runner flow is disconnected. Scope: Commercial Runbook Automation Self-Hosted with prepared local dependencies; SaaS and remotely hosted control planes are excluded. Source: https://www.pagerduty.com/platform/automation/process-software/ (reviewed 2026-11-18). Supporting source: Local commercial licence installation — https://docs.rundeck.com/docs/administration/license.html.

- Deployment artifact / IaC: Documented. The current guide names the commercial image rundeckpro/enterprise:6.3.0 with an external database, and recommends a reviewed derived image in a private registry. DEB installation separately uses package rundeckpro-ent. The EKS tutorial’s linked commercial Helm directory returned 404; obtain a current chart rather than substituting its Community example. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/install/docker.html (reviewed 2026-11-18). Supporting source: Customer AWS EC2/load balancer/RDS/S3 architecture — https://docs.rundeck.com/docs/administration/install/aws.html. Supporting source: Commercial DEB package repository — https://docs.rundeck.com/docs/administration/install/linux-deb.html. Supporting source: EKS tutorial and obsolete chart link — https://docs.rundeck.com/docs/learning/howto/how2-terra-rd-eks.html.

- Minimum footprint / sizing: Documented. Commercial Runbook Automation minimum is 4 CPUs/16 GB RAM with 12 GB heap per application instance; recommended is 8 CPUs/32 GB with 24 GB heap. Java 17 is the minimum from 6.0. Production uses an external supported database; H2 is for testing. HA replicas, logs and job runners add resources. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/install/system-requirements.html (reviewed 2026-11-18).

- License pricing: Documented. Commercial Runbook Automation Self-Hosted requires a licence file and quote. Rundeck Community’s Apache 2.0 licence does not license the commercial SSO/cluster features in this listing. Price runners, support and the purchased entitlement separately. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/license.html (reviewed 2026-11-18).

- Operating cost estimate: Sources checked — unresolved. Specify concurrent jobs, execution duration, runner pools and job-target work, HA application instances, external database HA, log/object retention and commercial licences. The per-instance minimum is not a complete AWS bill for 100 users or 1 TB of logs. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.rundeck.com/docs/administration/install/system-requirements.html (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. The official release notes identify Runbook Automation/Rundeck 6.3.0 and its security fixes. The public Rundeck OSS tag v6.3.0 was published October 22, 2026; that repository timestamp is not asserted as a separate commercial-package publication time. Verify the licensed image/package version and rebuild official containers for the CA fix. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/history/6_x/version-6.3.0.html (reviewed 2026-11-18). Supporting source: Commercial Docker remediation requirements — https://docs.rundeck.com/docs/history/cves/2026-10-emudhra-ca.html.




### Security and lifecycle reviews

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

- Runbook Automation Docker CA trust-store remediation (security-advisory): Official Docker images before 6.3.0 trust compromised eMudhra intermediates. The vendor directs self-hosted operators to pull and redeploy fixed images. Scope: Official Runbook Automation/Rundeck and Runner Docker images before 6.3.0. SaaS is excluded; host-installed RPM/DEB/WAR deployments depend on OS and Java trust stores. Conditions: An on-path attacker could exploit trusted compromised intermediates for outbound TLS. The vendor reports no known exploitation; this is not a flaw in Runbook Automation code. Action: Redeploy the updated 6.3.0+ official images rather than patching a disposable container. For host installations update and verify both OS and Java trust stores and restart. Source: https://docs.rundeck.com/docs/history/cves/2026-10-emudhra-ca.html; reviewed 2026-11-18.




## Perforce P4 Server (Helix Core)

Commercial centralized version-control server deployed from Perforce's cloud quickstarts into customer infrastructure.

- Listing: https://launchinyourcloud.com/directory/perforce-p4-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary P4 license; free within the published small-team limits, with commercial licensing and support above them.
- Licensing model: commercial-only
- Installation: Perforce quickstart images for AWS, Azure, Google Cloud or DigitalOcean; AWS also uses CloudFormation
- Architecture: P4 Server on a customer VM with persistent metadata and depot storage; replication and edge services are optional separate topology choices.
- Operations: Customer manages VM and OS security, depot and metadata storage, accounts, firewall, backups, logs, upgrades, capacity and any replication or edge topology.
- Product website: https://www.perforce.com/products/helix-core
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

Helix Core is being renamed P4 in current documentation. The quickstarts establish single-server deployment, not an HA or disaster-recovery design. Confirm current user/workspace entitlements before production use.

P4 is proprietary software. Perforce publishes a free-use threshold, but larger deployments and support require commercial licensing.

The quickstarts launch a persistent P4 Server VM and attached depot/metadata storage in the customer's cloud.


### Category fit

- devops: Provides centralized version control and a high-volume repository for source code, binaries and digital assets used by development teams.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html (checked 2026-11-18). 


### Cloud deployment evidence

- P4 Server on AWS (aws): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html
  Perforce documents a customer AWS deployment using EC2 and a CloudFormation quickstart.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- P4 Server on Azure (azure): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html
  Perforce documents launching P4 Server in the customer's own Azure cloud instance through Marketplace.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- P4 Server on Google Cloud (gcp): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html
  Perforce documents deployment into the customer's selected Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- P4 Server on DigitalOcean (digitalocean): https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html
  Perforce documents a P4 Server Droplet in the customer's DigitalOcean account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Plan a P4 Server cloud deployment: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html

- Deploy P4 Server on AWS: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html

- Deploy P4 Server on Azure: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html

- Deploy P4 Server on Google Cloud: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html

- Deploy P4 Server on DigitalOcean: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html

### Licensing sources

- https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html

### Infrastructure sources

- https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 10 documented, 2 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: Documented. Perforce publishes P4 (Self-Managed) on AWS Marketplace as a CloudFormation delivery, package 2026.1.0, on Rocky Linux. The offer is a deployment package; the P4 server patch level and purchased licence must be checked separately. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4 (reviewed 2026-11-18). Offer prodview-nw7wxff425so4: Perforce; CloudFormation Template (CFT); package 2026.1.0; https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Perforce P4 CFT offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms. Scope: Externally billed software licence for the exact reviewed public Perforce P4 CFT offer; not all provider spend or future private offers. Source: https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4 (reviewed 2026-11-18). Supporting source: AWS BYOL pricing boundary — https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html. Supporting source: Commitment qualification remains product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. P4 Authentication Service integrates SAML and OIDC identity providers with P4 through the authentication extension and supported clients. Deploy and secure the service and extension separately. Logging out of P4 does not necessarily terminate the IdP session. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/overview-of-has.html (reviewed 2026-11-18).

- SCIM provisioning: Documented. P4 Authentication Service exposes SCIM v2 at /scim/v2 for user/group provisioning, protected by a bearer token and a P4 super-user ticket. The documented implementation explicitly does not support deprovisioning; user renames are rejected by default. Do not rely on it for automated offboarding. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/provisioning.html (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Perforce’s Trust Center separates assurance resources by product, including Delphix, BlazeMeter, Puppet and QAC/Klocwork. Those gated reports and corporate badges do not identify a current P4 Server/Authentication Service assurance boundary. Request the applicable report/certificate, entity, period and customer-control scope; do not transfer another Perforce product’s report to P4. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://trust.perforce.com/resources (reviewed 2026-11-18).

- Security controls: Documented. P4 2026.1 changes security defaults, including raising a lower security level to 4 during p4d -xu. Other configurables keep explicitly set values on upgrade; new defaults are not proof that an existing deployment is hardened. Review protections, TLS, authentication extension privileges and the upgrade procedure. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://www.perforce.com/perforce/doc.current/user/relnotes.txt (reviewed 2026-11-18). Supporting source: SCIM endpoint and privileged ticket requirements — https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/provisioning.html.

- Air-gapped operation: Documented. Perforce’s SDP upgrade tool explicitly covers air-gapped servers: stage the binaries from the locations reported by get_helix_binaries.sh -n. P4 installs a local licence file; request it outside the isolated network and transfer it securely. Commit/central servers and any replica intended for failover need appropriate licences bound to their host identity. Stage client/SDP updates and use reachable internal identity, DNS, backup and support procedures. Scope: Self-managed P4 with staged SDP/server/client artifacts and valid local licence files; external SSO services are not made offline automatically. Source: https://workshop.perforce.com/files/guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/upgrade.sh?v=25 (reviewed 2026-11-18). Supporting source: Install and reload the local licence file — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.tips.release.html. Supporting source: Replica and cloud-host licence requirements — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html.

- Deployment artifact / IaC: Documented. The AWS quickstart launches the Perforce Marketplace CloudFormation package and configures EC2, SSH/P4 security groups and separate encrypted EBS data volumes. It defaults to small-team capacity. Review IAM and source-IP restrictions, then record the resolved template and server build in the deployment inventory. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html (reviewed 2026-11-18). Supporting source: Exact CFT offer and package version — https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4.

- Minimum footprint / sizing: Documented. The server administration guide gives memory planning factors of 64 MB per licensed user and 1.5 KB per depot file for a single server, with additional memory useful for filesystem cache. Depot file count, revisions, concurrency and replication matter. The quickstart’s t3.small default is not an HA design for 100 users. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.memory.html (reviewed 2026-11-18). Supporting source: Small-team AWS quickstart — https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html.

- License pricing: Documented. P4 is proprietary. The published free threshold is up to five users and fewer than twenty workspaces. Larger self-managed installations require a commercial quote; hosted P4 Cloud per-user pricing is a different product. The reviewed AWS offer bills its software licence outside AWS Marketplace. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html (reviewed 2026-11-18). Supporting source: External licence billing in the exact AWS offer — https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4. Supporting source: Separate failover-server licensing requirements — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html.

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 741.44/month. Two 8-vCPU/32-GiB VMs model a primary and licensed failover standby. Each has 1,000 GB archive, 100 GB metadata/journals and 30 GB boot gp3 capacity (2,260 GB total). P4 licences, file/revision-driven sizing, backup and replication transfer are unpriced. This is not a complete operating-cost estimate or validated capacity/SLA claim. Scope: Editorial P4 compute/storage layer on two AZs; configure journal/archive replication, licensing, failover and recovery tests. Metadata allowance and VM size are assumptions to validate against depot file count and throughput, not a vendor sizing guarantee.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-18). Supporting source: Product topology/sizing basis — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/failover.html. Supporting source: Current AWS us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: Single-server memory planning factors — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.memory.html. Supporting source: Primary and failover licence requirements — https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html.

- Release snapshot / cadence: Documented. The server release notes identify P4 2026.1 Patch 4 as 2026.1/3141402, dated November 12, 2026. Check p4d -V against the bugfix change level. This is distinct from the Marketplace package 2026.1.0 and Authentication Service’s own release line. Scope: Perforce P4 Server (Helix Core): selected customer-operated edition. Source: https://www.perforce.com/perforce/doc.current/user/relnotes.txt (reviewed 2026-11-18).







## Pulumi Cloud Self-Hosted

Enterprise infrastructure-delivery control plane deployed and operated in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/pulumi-cloud-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option
- Licensing model: commercial-only
- Installation: Official Pulumi programs for ECS or EKS, AKS or GKE
- Architecture: Customer-operated Pulumi Cloud frontend and API with customer networking, database, object storage and container infrastructure
- Operations: Customer operates backups, uptime, infrastructure and upgrades; Pulumi supplies the licensed application and deployment tooling.
- Product website: https://www.pulumi.com/product/pulumi-cloud/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Self-hosting is an Enterprise-only option. The installers bootstrap with a separate state backend because the self-hosted Pulumi service does not yet exist during its own deployment. Validate the supported database, storage and identity configuration for the selected release. The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment.

The Self-Hosted option is available with Pulumi Enterprise; Pulumi's open-source CLI and SDK do not by themselves license this control plane.

The application runs on customer container compute and uses customer database, object storage, networking and key-management services.


### Category fit

- devops: Provides a customer-operated Pulumi control plane for infrastructure delivery, state, policy, access and deployment workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.pulumi.com/docs/administration/self-hosting/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/ (checked 2026-11-19). 


### Cloud deployment evidence

- Pulumi Cloud Self-Hosted on AWS ECS or EKS (aws): https://www.pulumi.com/docs/administration/self-hosting/
  Pulumi lists production self-hosting options for AWS ECS and EKS and links official deployment programs that create the application in the customer's AWS environment.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Pulumi Enterprise Self-Hosted.

- Pulumi Cloud Self-Hosted on Azure AKS (azure): https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/
  The official deployment option installs the full self-hosted Pulumi Cloud service on customer Azure AKS and supporting Azure resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Pulumi Enterprise Self-Hosted.

- Pulumi Cloud Self-Hosted on Google GKE (gcp): https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/
  The official deployment option installs the full self-hosted Pulumi Cloud service on customer Google GKE and supporting Google Cloud resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Pulumi Enterprise Self-Hosted.


### Sources

- Pulumi Cloud self-hosting overview: https://www.pulumi.com/docs/administration/self-hosting/

- Pulumi edition comparison: https://www.pulumi.com/docs/administration/get-started/choose-edition/

- Self-hosted Pulumi Cloud on ECS: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/

- Self-hosted Pulumi Cloud on EKS: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/eks-hosted/

- Self-hosted Pulumi Cloud on AKS: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/

- Self-hosted Pulumi Cloud on GKE: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/

- Buyer evidence: sso: https://www.pulumi.com/docs/administration/self-hosting/saml-sso/

- Self-hosted feature parity checked; no specific SCIM endpoint established: https://www.pulumi.com/docs/administration/self-hosting/feature-parity/

- Buyer evidence: securityControls: https://www.pulumi.com/docs/administration/self-hosting/operations/security-hardening/

- Buyer evidence: airGap: https://www.pulumi.com/docs/administration/self-hosting/airgapped/

- Reviewed deployment artifact reference: https://github.com/pulumi/pulumi-self-hosted-installers/tree/e7a8007335f692d5d343a16d121057bcabc2bab3

- Buyer evidence: footprint: https://www.pulumi.com/docs/administration/self-hosting/operations/compute-sizing/

- Buyer evidence: release: https://www.pulumi.com/docs/administration/self-hosting/changelog/

### Licensing sources

- https://www.pulumi.com/docs/administration/get-started/choose-edition/

- https://www.pulumi.com/docs/administration/self-hosting/

### Infrastructure sources

- https://www.pulumi.com/docs/administration/self-hosting/

- https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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 reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Single sign-on: Documented. Self-hosted Pulumi Enterprise supports SAML SSO. Configure the API service’s signing/validation key pair, enable SAML_SSO_ENABLED on the console, and complete the IdP and organization setup. The guide requires restarting the affected services after configuration changes. Scope: Licensed self-hosted Pulumi Enterprise console authentication; not an assertion of SCIM provisioning. Source: https://www.pulumi.com/docs/administration/self-hosting/saml-sso/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19). Supporting source: Self-hosted feature parity checked; no specific SCIM endpoint established — https://www.pulumi.com/docs/administration/self-hosting/feature-parity/.

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Security controls: Documented. The hardening guide specifies private application/database subnets, restricted inter-tier traffic, configurable CIDR ingress allowlists, encrypted database/object storage, encrypted Pulumi configuration secrets and TLS between clients, console, API and MySQL. These are controls the customer configures, not proof that an installation is hardened or independently attested. Scope: Documented self-hosted Enterprise controls and configuration responsibilities; compliance attestations are separate. Source: https://www.pulumi.com/docs/administration/self-hosting/operations/security-hardening/ (reviewed 2026-11-19).

- Air-gapped operation: Documented. Pulumi documents an air-gapped self-hosted Enterprise deployment using an entitled licence key and service images, internal infrastructure, and mirrors for CLI/SDK packages, provider plugins and container images. Configure all tools to use the mirrors and review identity and cloud-API connectivity for the selected workflows. Scope: Configured self-hosted Enterprise installation with staged licensed images and internal artifact mirrors. Source: https://www.pulumi.com/docs/administration/self-hosting/airgapped/ (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The official installer repository supplies ECS, EKS, AKS and GKE deployment programs. The reviewed repository commit is pinned independently of the licensed API/console images and licence key, which must be obtained from Pulumi. Pin compatible service images and review installer-specific changes before applying the code. Scope: Public self-hosted infrastructure/application deployment programs; not a licence to the commercial service images. Source: https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/ (reviewed 2026-11-19). Deployment artifact: https://github.com/pulumi/pulumi-self-hosted-installers/tree/e7a8007335f692d5d343a16d121057bcabc2bab3. Artifact reference: e7a8007335f692d5d343a16d121057bcabc2bab3; installer source commit, not a Pulumi Cloud application version.

- Minimum footprint / sizing: Documented. The production baseline specifies two or more API instances across two or more AZs, at least 2 vCPU and 4 GB RAM per API instance, a 0.5-vCPU/512-Mi console, a MySQL writer/reader setup with 20 GB+ SSD, and 200 GB+ object storage. Add migrations, networking, backups and workload growth; this is a vendor baseline, not a validated 100-user/1-TB cost or performance model. Scope: Self-hosted Enterprise production component baseline; size every selected service and workload separately. Source: https://www.pulumi.com/docs/administration/self-hosting/operations/compute-sizing/ (reviewed 2026-11-19).

- License pricing: Edition-dependent. Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option Infrastructure, support and operating labor are separate unless the order states otherwise. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/get-started/choose-edition/ (reviewed 2026-11-19).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: Pulumi Cloud Self-Hosted: selected customer-operated edition. Source: https://www.pulumi.com/docs/administration/self-hosting/ (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The public self-hosted changelog documents an October 2026 API trust-store update and a September OpenSearch 3.7.0 installer change, but does not identify one immutable licensed API/console image bundle and precise release timestamp. The public installer commit is separately pinned; obtain the entitled service image versions/digests and upgrade matrix from Pulumi. Scope: Licensed self-hosted service image release snapshot, distinct from the Pulumi CLI or public installer commit. Source: https://www.pulumi.com/docs/administration/self-hosting/changelog/ (reviewed 2026-11-19).




### Security and lifecycle reviews

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

- Pulumi self-hosted API October 2026 trust-store update (security-advisory): The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Scope: The licensed self-hosted API-service update described in the October 2026 changelog; an immutable patched image ID and exact release day are not published there. Conditions: The running API image and effective certificate trust store determine applicability. Pinning public installer source does not establish the private service image version. Action: Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment. Source: https://www.pulumi.com/docs/administration/self-hosting/changelog/; reviewed 2026-11-19.




## Rancher Manager

Open-source Kubernetes management platform deployed into a customer-operated cluster.

- Listing: https://launchinyourcloud.com/directory/rancher-manager/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0; commercial SUSE subscriptions and support are separate.
- Licensing model: open-source
- Installation: Official Helm chart on a supported Kubernetes cluster
- Architecture: Customer-operated Rancher management server, ingress and persistent Kubernetes resources
- Operations: Customer manages the management cluster, ingress, certificates, backups, upgrades, downstream-cluster credentials and availability.
- Product website: https://www.rancher.com/products/rancher
- Source review: 2026-11-14; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers self-managed Rancher Manager, not separate hosted offerings. Rancher documents EKS, AKS and GKE installation paths. GKE Autopilot is not supported for the Rancher server because required kube-system changes are restricted.

Rancher Manager is Apache-2.0 licensed. SUSE subscriptions, hosted services and enterprise support use separate commercial terms.

Rancher runs as persistent management services inside Kubernetes and requires ingress, certificates and durable state. The hosted Kubernetes control plane does not make Rancher serverless.


### Category fit

- devops: Provides centralized provisioning, access control and lifecycle management for Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke (checked 2026-11-14). 


### Cloud deployment evidence

- Rancher Manager on Amazon EKS (aws): https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks
  The upstream guide installs the Rancher server with Helm into an EKS cluster controlled by the customer.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Rancher Manager on Azure Kubernetes Service (azure): https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks
  The upstream guide installs the Rancher server with Helm into an AKS cluster controlled by the customer.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Rancher Manager on Google Kubernetes Engine (gcp): https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke
  The upstream guide installs Rancher into a GKE Standard cluster. GKE Autopilot is explicitly unsupported for the Rancher server.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

Rancher has sustained code participation from multiple contributors and an established upstream user community. The reviewed Community release 2.15.3, published October 29, 2026, records maintenance and security fixes. Public contributor history and the official community program establish participation beyond repository popularity; commercial SUSE support remains separate.

Reviewed 2026-11-14.

- Reviewed maintenance release v2.15.3: https://github.com/rancher/rancher/releases/tag/v2.15.3

- Upstream contributor history: https://github.com/rancher/rancher/graphs/contributors

- Upstream user community and participation: https://www.rancher.com/community

### Sources

- Kubernetes installation overview: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster

- Rancher on Amazon EKS: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks

- Rancher on AKS: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks

- Rancher on GKE: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke

- Apache 2.0 license: https://github.com/rancher/rancher/blob/master/LICENSE

- Reviewed maintenance release v2.15.3: https://github.com/rancher/rancher/releases/tag/v2.15.3

- Upstream contributor history: https://github.com/rancher/rancher/graphs/contributors

- Upstream user community and participation: https://www.rancher.com/community

### Licensing sources

- https://github.com/rancher/rancher/blob/master/LICENSE

### Infrastructure sources

- https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream authentication guide documents OIDC, SAML and OAuth integrations, including Keycloak, Okta, Entra ID, AD FS and a generic OIDC provider. Review version compatibility, local administrator access and downstream-cluster authorization separately from signing into Rancher. Scope: Rancher Manager console federation. Source: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Kubernetes guide publishes separate stable, latest and alpha Helm repositories. Stable is recommended for production; check the Kubernetes support matrix and certificate/HA prerequisites before installation. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster (reviewed 2026-11-14). Deployment artifact: https://releases.rancher.com/server-charts/stable/index.yaml. Artifact reference: stable Helm repository index (moving; select a supported chart version).

- Minimum footprint / sizing: Documented. For a small hosted-Kubernetes management cluster, the guide lists at least three nodes, each with 4 vCPUs and 16 GB RAM. Larger managed fleets need more. Single-node Docker is development/test only; downstream workload clusters, datastore/storage and HA headroom are additional. Scope: Upstream management-cluster starting profile; downstream applications excluded. Source: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements (reviewed 2026-11-20).

- License pricing: Documented. Rancher Manager core is Apache-2.0 licensed. This does not establish a SUSE support subscription price or the cost and licences of managed Kubernetes clusters and optional components. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/rancher/rancher/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v2.15.3, published 2026-10-29. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream rancher/rancher release record; commercial editions and deployment packages may differ. Source: https://github.com/rancher/rancher/releases/tag/v2.15.3 (reviewed 2026-11-14).







## Red Hat Ansible Automation Platform Self-Managed

Enterprise IT automation platform installed and managed by the customer in a public-cloud environment.

- Listing: https://launchinyourcloud.com/directory/ansible-automation-platform-self-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat Ansible Automation Platform subscription required.
- Licensing model: commercial-only
- Installation: Containerized installer on RHEL with Podman or the OpenShift Operator
- Architecture: Customer-operated automation controller, execution and platform services on RHEL or OpenShift.
- Operations: Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.
- Product website: https://www.redhat.com/en/technologies/management/ansible
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.

The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification.

Self-managed Ansible Automation Platform uses persistent RHEL containers or customer-operated OpenShift workloads with databases and execution capacity.


### Category fit

- devops: Enterprise configuration, provisioning and operations automation across infrastructure and applications.

- workflow-automation: Controller, event-driven automation and reusable automation content coordinate governed operational workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities (checked 2026-11-17). 


### Cloud deployment evidence

- Self-managed Ansible Automation Platform in named public clouds (aws, azure, gcp): https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities
  Red Hat documents self-managed Ansible Automation Platform deployments on infrastructure hosted in AWS, Azure and Google Cloud. The customer operates the RHEL or OpenShift environment and supplies the subscription.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Named-cloud and self-managed installation overview: https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities

- Current 2.7 deployment models: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models

- Set up the Ansible Automation Platform subscription: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription

### Licensing sources

- https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription

### Infrastructure sources

- https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models


### 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. AWS lists Red Hat subscriptions including AAP, alongside a different managed AAP service. Confirm an offer/order explicitly entitling this self-managed 2.7 installation. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Managed AAP Marketplace committed-spend claims do not establish treatment of this self-managed subscription. Obtain the selected offer and buyer-agreement eligibility. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk (reviewed 2026-11-17).

- Single sign-on: Documented. AAP 2.7 documents SAML identity-provider configuration through platform gateway. External authentication must use the gateway; legacy direct component authentication is no longer supported. Scope: Self-managed AAP 2.7 platform gateway. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml (reviewed 2026-11-17). Supporting source: Mandatory gateway authentication — https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-mandatory_platform_gateway_authentication_in_ansible_automation_platform_2_7.

- SCIM provisioning: Sources checked — unresolved. Platform gateway documents SAML/LDAP/OIDC and group/role mapping, but a supported AAP 2.7 SCIM lifecycle endpoint was not established. Scope: Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat Ansible Automation Platform Self-Managed material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment (reviewed 2026-11-17).

- Security controls: Documented. AAP 2.7 centralizes external authentication at platform gateway and documents HTTPS redirects and CSRF settings. Restrict component access and configure the chosen identity provider and role mappings. Scope: AAP 2.7 gateway and deployment configuration. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment (reviewed 2026-11-17).

- Air-gapped operation: Documented. The containerized installer supports disconnected installation using a downloaded setup bundle, local RHEL RPM repositories and bundle_install=true. Required metrics service works without internet access; content and update transfers remain operator responsibilities. Scope: AAP 2.7 containerized disconnected installation. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-assembly_aap_containerized_disconnected_installation (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The subscription-gated containerized setup bundle uses a configured inventory to install platform components with Podman; OpenShift uses the supported Operator path. AAP 2.7 does not use the removed RPM installer. Scope: AAP 2.7 installation methods; not AWX or Ansible Core. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-con_choosing_installation_type (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The containerized system requirements distinguish the supported RHEL host, subscriptions, database and component resources. Use the deployment-model inventory and execution capacity to size each host; portal-only appliance requirements do not size the complete platform. Scope: AAP 2.7 containerized topology, not portal-only sizing. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements (reviewed 2026-11-17).

- License pricing: Documented. The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification. Scope: Red Hat Ansible Automation Platform Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Choose the supported HA inventory and count managed nodes, execution jobs, execution environments, controller/hub/database hosts and RHEL/AAP subscriptions. Human users and data size alone do not size automation capacity. 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://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed self-managed documentation is the AAP 2.7 line, with separate patch-release notes and component updates. Select a supported patch and matching bundle; this is a version-line review, not a claim about a latest patch timestamp. Scope: Self-managed AAP documentation line and patch index. Source: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/ (reviewed 2026-11-17).







## Red Hat OpenShift Container Platform

Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.

- Listing: https://launchinyourcloud.com/directory/openshift-container-platform/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift subscription.
- Licensing model: commercial-only
- Installation: OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud
- Architecture: Customer-operated control-plane and worker machines with integrated operators, networking, storage and cluster services
- Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.

The selected self-managed OpenShift Container Platform edition is delivered through a commercial Red Hat subscription with entitlement and support terms.

OpenShift Container Platform runs persistent control-plane and worker nodes plus integrated cluster operators and storage services in the customer cloud.


### Category fit

- backend-platforms: Provides a self-managed Kubernetes application platform with integrated operators, developer workflows, networking, registry and cluster services.

- devops: Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index (checked 2026-11-15). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index (checked 2026-11-15). 


### Cloud deployment evidence

- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud (aws, azure, gcp): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview
  Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Self-managed OpenShift on IBM Cloud (ibm): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index
  Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21.

- OpenShift on Alibaba Cloud — Technology Preview (alibaba): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index
  Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21 Technology Preview.


### Sources

- OpenShift Container Platform 4.21 installation overview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview

- Red Hat self-managed OpenShift subscription guide: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

- Self-managed OpenShift on IBM Cloud: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index

- OpenShift on Alibaba Cloud — Technology Preview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index

### Licensing sources

- https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

### Infrastructure sources

- https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The 4.20 Authentication Operator supports an external OIDC identity provider using authorization-code flow, discovery and mapped claims. This authenticates platform users; applications running on the cluster need their own identity integration. Review browser/CLI token workflows and selected provider compatibility. Scope: OpenShift 4.20 platform-user OIDC through the integrated OAuth service. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/observability/authentication_and_authorization/using-rbac (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Red Hat documents installer-provisioned AWS infrastructure using the release-matched openshift-install tool, install configuration, pull secret and cloud credentials. Customer-managed networking and permissions require review. Use the entitled Red Hat release distribution; the upstream installer source alone is not the product entitlement. Scope: OpenShift Container Platform 4.20 AWS installer path. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20). Deployment artifact: https://github.com/openshift/installer. Artifact reference: Upstream installer source; obtain matching Red Hat release tooling and pull secret.

- Minimum footprint / sizing: Documented. The 4.20 AWS installation matrix gives bootstrap/control-plane minima of 4 vCPUs, 16 GB RAM and 100 GB disk, and compute nodes 2 vCPUs, 8 GB and 100 GB. A standard cluster uses multiple control-plane and worker machines; workload pods, operators, storage, bootstrap and HA capacity are additional. Scope: OpenShift 4.20 per-machine installation floors, not complete workload sizing. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20).

- License pricing: Documented. Self-managed subscriptions can use core-pairs or bare-metal nodes. On hyperscaler VMs, one core-pair covers four vCPUs; aggregate compute-node entitlement and support level must be sized. AI accelerators may require separate subscriptions. Obtain the applicable order and price. Scope: Red Hat self-managed OpenShift Container Platform subscription guide. Source: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SonarQube Server Data Center Edition

Commercial high-availability SonarQube Server edition with Google Cloud deployment, Azure Kubernetes instructions and documented AWS architecture guidance.

- Listing: https://launchinyourcloud.com/directory/sonarqube-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp, azure, aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Data Center Edition license.
- Licensing model: commercial-only
- Installation: Google Cloud Marketplace on GKE or DCE Helm chart; documented AKS deployment and AWS architecture adaptation
- Architecture: Clustered application and search nodes with load balancing, persistent volumes and an external production database
- Operations: Customer manages the Kubernetes cluster, namespaces, database, persistent volumes, secrets, TLS, identity, load balancing, backups, autoscaling, upgrades and the SonarQube license.
- Product website: https://www.sonarsource.com/products/sonarqube/server/
- Source review: 2026-11-18; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers self-managed Data Center Edition. Google Cloud has a Marketplace path; Azure has a concrete AKS deployment example, while the AWS architecture requires adaptation. For 2026.1, use an external production database, compatible Helm values and an appropriate storage class on AKS; the documentation warns about Azure Fileshare permissions. Confirm chart and package versions independently. CVE-2026-114938 is reported to allow unauthenticated RCE in affected OpenJDK 17.0.6+ runtimes, including Java 21 and 25, on x86-64 CPUs with AVX-512 VBMI. Until Sonar publishes patched builds, set -XX:-UseBASE64Intrinsics for Web, Compute Engine, and Search; ARM is unaffected, and Sonar reported no evidence of exploitation.

SonarQube Server Data Center Edition is a paid, per-instance commercial edition priced by licensed lines of code.

Data Center Edition runs clustered application and search services on customer Kubernetes infrastructure with persistent storage and an external production database.


### Category fit

- devops: Provides high-availability self-managed code-quality and security analysis integrated with source-control and CI workflows.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks (checked 2026-11-15). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example (checked 2026-11-15). 


### Cloud deployment evidence

- SonarQube Data Center Edition on GKE (gcp): https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp
  Sonar documents deploying Data Center Edition through Google Cloud Marketplace into an existing customer GKE cluster, using either Click to Deploy or the advanced command-line path.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- SonarQube DCE deployment on Azure Kubernetes Service (azure): https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks
  Sonar provides a Data Center Edition deployment procedure for primary and replica AKS clusters using its Helm chart, an external PostgreSQL writer endpoint and Azure ingress. This is an active-cold standby example; cluster sizing must be assessed separately.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Edition: Data Center Edition. Versions: 2026.1.

- SonarQube DCE cloud architecture and AWS chart guidance (aws): https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example
  Sonar explicitly says its DCE Kubernetes disaster-recovery architecture can be adapted to AWS with modifications. The upstream DCE Helm chart separately documents AWS ingress migration settings. This is an architecture adaptation path, not an AWS one-click package or a support commitment.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Edition: Data Center Edition. Versions: 2026.1 architecture; select a compatible Helm chart.


### Sources

- SonarQube Data Center Edition on Google Cloud: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp

- SonarQube Server plans and licensing: https://www.sonarsource.com/plans-and-pricing/sonarqube/

- SonarQube DCE deployment on Azure Kubernetes Service: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks

- SonarQube DCE cloud architecture and AWS chart guidance: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example

- Upstream SonarQube DCE Helm chart and AWS ingress settings: https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube-dce/README.md

- DCE Kubernetes prerequisites and AKS storage limitation: https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/before-you-start

- SonarQube Java4Shell workaround advisory: https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330

### Licensing sources

- https://www.sonarsource.com/plans-and-pricing/sonarqube/

### Infrastructure sources

- https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp

- https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks

- https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SonarQube Server 2026.5 documents SP-initiated SAML 2.0 federation and optional SCIM provisioning with configured identity providers. This applies to the licensed Server deployment; verify the chosen Data Center licence and identity-provider mapping. Scope: SonarQube Server 2026.5 SAML; selected Data Center entitlement requires review. Source: https://docs.sonarsource.com/sonarqube-server/instance-administration/authentication/saml/overview (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Sonar reports that CVE-2026-114938 may permit unauthenticated RCE in affected OpenJDK runtimes on x86-64 AVX-512 VBMI systems. Apply -XX:-UseBASE64Intrinsics to Web, Compute Engine, and Search as documented, and move to a patched Sonar build when the vendor names one. Scope: Potentially affects supported SonarQube Server 2026.5, 2026.1 LTA, 2025.4 LTA, Community Build, and older versions when the affected Java and CPU conditions are present. ARM is unaffected.. Source: https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream sonarqube-dce Helm chart installs Data Center Edition and requires an external database. It explicitly excludes Community, Developer and Enterprise Editions. Pin and validate the chart/application versions instead of assuming a moving chart matches the versioned cloud guide. Scope: SonarSource sonarqube-dce chart README on moving master branch. Source: https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube-dce/README.md (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. Current Data Center requirements call for at least two application nodes and three search nodes, plus a separate database and load balancer. The validated example uses 4-vCPU/16-GB application nodes and 8-vCPU/32-GB search nodes. Code/issue volume, storage, database and optional agentic features require additional sizing. Scope: Current five-node Data Center topology and vendor validation example. Source: https://docs.sonarsource.com/sonarqube-server/server-installation/data-center-edition/installation-requirements.md (reviewed 2026-11-20).

- License pricing: Documented. Self-hosted editions are priced per instance per year by lines of code; Data Center is the commercial clustered edition. Obtain the required LOC tier and support quote. Optional agentic features require separate subscriptions; the Community licence and Cloud price do not cover Data Center. Scope: Commercial Data Center edition; LOC-based annual model. Source: https://www.sonarsource.com/plans-and-pricing/sonarqube/ (reviewed 2026-11-20). Supporting source: Optional feature subscriptions — https://docs.sonarsource.com/sonarqube-server/server-installation/data-center-edition/installation-requirements.md.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- SonarQube Java4Shell workaround (security-advisory): Sonar reports that CVE-2026-114938 may permit unauthenticated RCE in affected OpenJDK runtimes on x86-64 AVX-512 VBMI systems. Scope: Potentially affects supported SonarQube Server 2026.5, 2026.1 LTA, 2025.4 LTA, Community Build, and older versions when the affected Java and CPU conditions are present. ARM is unaffected. Conditions: OpenJDK 17.0.6 or later, including Java 21 and 25, on x86-64 with AVX-512 VBMI. Sonar reported no known exploitation when publishing the notice. Action: Apply -XX:-UseBASE64Intrinsics to Web, Compute Engine, and Search as documented, and move to a patched Sonar build when the vendor names one. Source: https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330; reviewed 2026-11-18.




## Sonatype Nexus Repository Pro Self-Hosted

Commercial self-hosted artifact repository with supported high-availability deployment across customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/nexus-repository-pro-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Nexus Repository Pro license required for high availability and other Pro capabilities.
- Licensing model: commercial-only
- Installation: Official Helm chart for resilient or high-availability Kubernetes deployments, or supported standalone and Docker installation paths
- Architecture: Standalone node or active-active Nexus Repository Pro cluster with persistent storage, external PostgreSQL, load balancing and cloud blob storage
- Operations: Customer manages compute or Kubernetes, PostgreSQL, blob and node storage, ingress and load balancing, TLS, secrets, backups, monitoring, upgrades and license persistence.
- Product website: https://www.sonatype.com/products/sonatype-nexus-repository
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Nexus Repository Pro self-hosted deployments, not Nexus Repository Cloud or the unlicensed Community Edition. High availability requires Pro, an external PostgreSQL database and customer expertise in Kubernetes, Helm and cloud infrastructure. Sonatype states that its support expertise is strongest on AWS even though Azure and Google Cloud infrastructure are supported. Container deployments must persist both nexus-data and Java preferences so license state survives restarts. Nexus Repository 3.98.0 fixes seven November advisories covering Rut Auth privilege escalation, disabled or locked SSO users regaining access, exposed signing material, SQL injection in the optional reindex task, stored XSS, and group-member authorization bypass. After upgrading, remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove existing group members that group editors are not allowed to read; the upgrade does not clean these up. Review affected sign-ins and tasks, and rotate potentially exposed signing keys or passphrases. Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.

A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro.

Nexus Repository Pro runs on persistent VM or Kubernetes capacity with durable node storage, blob storage and, for resilient or HA deployments, an external PostgreSQL database.


### Category fit

- devops: Provides a self-managed repository for packages, containers and other build artifacts used by software-delivery pipelines.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html (checked 2026-11-16). Source: https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html (checked 2026-11-16). 


### Cloud deployment evidence

- Supported Nexus Repository Pro high-availability infrastructure (aws, azure, gcp): https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html
  Sonatype explicitly lists AWS, Azure and Google Cloud as supported providers for Nexus Repository Pro HA and names EKS, AKS and GKE together with provider-specific databases, storage and blob services.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: Nexus Repository Pro.

- Nexus Repository Pro deployment on Google Cloud (gcp): https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html
  Sonatype provides a concrete Google Cloud deployment path for Nexus Repository Pro using its resiliency and high-availability Helm chart, GKE ingress, persistent storage and license management.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: Nexus Repository Pro.


### Sources

- Install self-hosted Nexus Repository: https://help.sonatype.com/en/install-nexus-repository.html

- Nexus Repository high-availability requirements: https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html

- Deploy Nexus Repository to Google Cloud: https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html

- Nexus Repository license management: https://help.sonatype.com/en/license-management.html

- Nexus Repository CVE-2026-113373 advisory: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04

- Nexus Repository Rut Auth cleanup after upgrade: https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04

- Nexus Repository existing group-member cleanup after upgrade: https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04

- Nexus Repository 3.90.7 release notes: https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html

- Nexus Repository 3.88.2 release notes: https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html

- Sonatype Java4Shell FAQ: https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products

- Nexus Repository 3.98.2 Java4Shell mitigation and publication date: https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html

### Licensing sources

- https://help.sonatype.com/en/license-management.html

- https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html

### Infrastructure sources

- https://help.sonatype.com/en/install-nexus-repository.html

- https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html


### Buyer diligence


Research coverage: 9/12 fields (75%); 8 documented, 1 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: Edition-dependent. Sonatype publishes an AWS Marketplace offer explicitly named Nexus Repository Pro (Self-Hosted). It is a contract/license procurement listing classified as SaaS, not a vendor-run Repository Cloud deployment or an infrastructure installer. Confirm usage, renewal and support terms. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-444trrzad4z56 (reviewed 2026-11-16). Offer prodview-444trrzad4z56: Sonatype; Self-hosted license contract; AWS delivery classification SaaS; https://aws.amazon.com/marketplace/pp/prodview-444trrzad4z56.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Licensed self-hosted Nexus Repository supports SAML 2.0 browser SSO, including IdP group attributes for authorization. SAML authenticates the UI; repository clients use other supported credentials such as user tokens. Scope: Nexus Repository Pro self-hosted UI; not Community or a repository-content SAML protocol. Source: https://help.sonatype.com/en/saml.html (reviewed 2026-11-16).

- SCIM provisioning: Explicitly unsupported. Sonatype explicitly states that direct SCIM is unsupported. SSO does not automatically synchronize user lifecycle or group changes; manual management or custom API integrations are required. Scope: Nexus Repository direct SCIM integration. Source: https://help.sonatype.com/en/authentication.html (reviewed 2026-11-16). Supporting source: Separate SAML-user management REST API — https://help.sonatype.com/en/security-management-api.html.

- Compliance attestations: Not researched.

- Security controls: Documented. The policy requires base usage telemetry and administrator acknowledgment starting in 3.97.0. Pro has a stated 45-day telemetry-delivery grace period; customers requiring disconnected operation need entitlement-specific support review. This is an egress requirement, not a security attestation. Current advisory review: Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass. Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases. Current review: Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport. Scope: Nexus Repository maintenance lines explicitly covered by the November 19 release notes. Source: https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04. Supporting source: Prior security-controls source — https://help.sonatype.com/en/nexus-repository-telemetry.html. Supporting source: CVE-2026-113374 — https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04. Supporting source: CVE-2026-113372 — https://support.sonatype.com/hc/en-us/articles/56612283547539-CVE-2026-113372-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-YUM-Repository-Signing-Key-2026-11-04. Supporting source: CVE-2026-113371 — https://support.sonatype.com/hc/en-us/articles/56609541356051-CVE-2026-113371-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-Repository-Signing-Passphrase-2026-11-04. Supporting source: CVE-2026-113370 — https://support.sonatype.com/hc/en-us/articles/56603207226131-CVE-2026-113370-Nexus-Repository-3-SQL-Injection-in-Reindex-Search-by-Pattern-Task-2026-11-04. Supporting source: CVE-2026-113369 — https://support.sonatype.com/hc/en-us/articles/56597339691027-CVE-2026-113369-Nexus-Repository-3-Stored-Cross-Site-Scripting-in-OCI-Attestations-Tab-2026-11-04. Supporting source: CVE-2026-113368 — https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04. Supporting source: 3.90.7 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html. Supporting source: 3.88.2 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html. Supporting source: 3.98.2 current-line Java4Shell mitigation — https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html.

- Air-gapped operation: Sources checked — unresolved. The current telemetry policy requires base usage reporting and directs commercially entitled customers needing disconnected operation to Sonatype Support. It does not publish an unconditional Pro exemption or a complete disconnected procedure; obtain entitlement-specific terms before relying on air-gapped operation. Scope: Current self-hosted Pro telemetry policy, including 3.97+ onboarding; not Community or SAGE. Source: https://help.sonatype.com/en/nexus-repository-telemetry.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Sonatype publishes the nxrm-ha Helm chart for resilient and high-availability deployments. Pro HA requires an external PostgreSQL database and persistent storage; choose a supported chart, application and database combination. Scope: Nexus Repository Pro HA; not the standalone Community Edition topology. Source: https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html (reviewed 2026-11-16). Deployment artifact: https://github.com/sonatype/nxrm3-ha-repository/tree/main/nxrm-ha. Artifact reference: main (moving branch). Supporting source: HA requirements — https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html.

- Minimum footprint / sizing: Documented. The current cloud-native XS profile recommends one node with 4 vCPU and 16 GiB RAM for its stated 100 requests/second workload. Larger profiles increase node count and resources; Pro HA additionally needs a load balancer, shared blob storage and external PostgreSQL. Scope: Per-node example for the documented workload; not an HA total or performance guarantee. Source: https://help.sonatype.com/en/sonatype-nexus-repository-system-requirements.html (reviewed 2026-11-16). Supporting source: HA infrastructure requirements — https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html.

- License pricing: Documented. A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro. Scope: Sonatype Nexus Repository Pro Self-Hosted: software license terms; infrastructure and operating costs are separate. Source: https://help.sonatype.com/en/license-management.html (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Nexus Repository 3.98.2 was released November 18, 2026 and includes Java4Shell mitigation for CVE-2026-114938. This is the reviewed 3.98-line snapshot; 3.90.7 and 3.88.2 are separate maintenance backports. Check commercial-edition, runtime, Helm and HA compatibility before upgrading. Scope: Self-hosted Nexus Repository release; commercial edition and HA compatibility still govern use; source supplies a publication day, not a timestamp. Source: https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html (reviewed 2026-11-19). Supporting source: 3.90.7 maintenance-line mitigation — https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html. Supporting source: 3.88.2 maintenance-line mitigation — https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html. Supporting source: Sonatype Java4Shell product and maintained-branch guidance — https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products.




### Security and lifecycle reviews

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

- Nexus Repository 3.98.0 security update (security-advisory): Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass. Scope: Affected ranges vary from 3.0.0 through 3.97.x to narrower 3.86–3.97, 3.90–3.97, 3.93–3.97, and 3.94–3.97 ranges. All are fixed in 3.98.0. Conditions: Rut Auth, SSO, YUM or repository signing, the optional reindex task, OCI attestations, and repository groups determine applicability. Action: Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases. Source: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04; reviewed 2026-11-18. Supporting source: CVE-2026-113374 — https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04. Supporting source: CVE-2026-113372 — https://support.sonatype.com/hc/en-us/articles/56612283547539-CVE-2026-113372-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-YUM-Repository-Signing-Key-2026-11-04. Supporting source: CVE-2026-113371 — https://support.sonatype.com/hc/en-us/articles/56609541356051-CVE-2026-113371-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-Repository-Signing-Passphrase-2026-11-04. Supporting source: CVE-2026-113370 — https://support.sonatype.com/hc/en-us/articles/56603207226131-CVE-2026-113370-Nexus-Repository-3-SQL-Injection-in-Reindex-Search-by-Pattern-Task-2026-11-04. Supporting source: CVE-2026-113369 — https://support.sonatype.com/hc/en-us/articles/56597339691027-CVE-2026-113369-Nexus-Repository-3-Stored-Cross-Site-Scripting-in-OCI-Attestations-Tab-2026-11-04. Supporting source: CVE-2026-113368 — https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04.

- Nexus Repository Java4Shell fixes for current and maintained branches (security-advisory): Nexus Repository 3.98.2 includes Java4Shell mitigation; 3.90.7 and 3.88.2 are separate older-line backports, not substitutes for the current 3.98-line fix. Scope: Self-hosted Nexus Repository: 3.98.2 on the 3.98 line. The FAQ also lists 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the linked November 19 notes identify 3.90.7 and 3.88.2. Conditions: Installed branch, bundled JDK, CPU and process restart determine applicability. Action: Upgrade the installed supported branch to its fixed release, including 3.98.2 or later on 3.98. Restart and verify affected processes. If an immediate upgrade is unavailable, follow Sonatype’s temporary JVM mitigation and runtime-compatibility guidance. Do not downgrade to match an older maintenance backport. Source: https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products; reviewed 2026-11-19. Supporting source: 3.90.7 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html. Supporting source: 3.88.2 release notes — https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html. Supporting source: 3.98.2 current-line fix, released November 18, 2026 — https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html.




## Spacelift Self-Hosted

Commercial infrastructure-as-code automation platform deployed to customer AWS, Azure or Google Cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/spacelift-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Spacelift Self-Hosted Enterprise subscription and license token required.
- Licensing model: commercial-only
- Installation: Official Terraform/OpenTofu reference architectures and Helm charts for EKS/ECS, AKS or GKE
- Architecture: Customer-operated Spacelift backend, gateway, workers and data services on cloud compute or Kubernetes.
- Operations: Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.
- Product website: https://spacelift.io/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers Spacelift Self-Hosted, not the Spacelift SaaS service. New features can reach SaaS before self-hosted releases; match the deployment artifacts and architecture to the licensed version.

Self-hosting is a commercial Enterprise capability governed by Spacelift subscription and license terms.

Spacelift Self-Hosted runs persistent backend and worker services with database and object-storage dependencies.


### Category fit

- devops: Provides self-hosted infrastructure-as-code runs, policy, state, integrations and private workers.

- workflow-automation: Orchestrates governed infrastructure workflows, approvals and automated runs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.spacelift.io/self-hosted (checked 2026-11-18). 


### Cloud deployment evidence

- Spacelift in customer AWS, Azure or GCP infrastructure (aws, azure, gcp): https://docs.spacelift.io/self-hosted
  Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Spacelift Self-Hosted: https://docs.spacelift.io/self-hosted

- Deploy Spacelift to EKS: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks

- Deploy Spacelift to AKS: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-aks

- Deploy Spacelift to GKE: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-gke

- Spacelift pricing: https://spacelift.io/pricing

### Licensing sources

- https://docs.spacelift.io/self-hosted/latest/legal/terms

- https://spacelift.io/pricing

### Infrastructure sources

- https://docs.spacelift.io/self-hosted


### Buyer diligence


Research coverage: 12/12 fields (100%); 8 documented, 4 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. Spacelift documents public AWS contracts and a sales-assisted private-offer route. Its pricing FAQ says plans are available through AWS, but the reviewed public offer/registration describes SaaS. A private worker is not a self-hosted backend. Obtain an order/private offer that explicitly entitles Enterprise Self-Hosted, its package and support scope before applying Marketplace availability to this listing. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/product/billing/aws-marketplace (reviewed 2026-11-18). Supporting source: Plan, Self-Hosted and Marketplace FAQ statements — https://spacelift.io/pricing. Supporting source: Backend versus SaaS/private-worker boundary — https://docs.spacelift.io/self-hosted.

- Cloud commitment eligibility: Sources checked — unresolved. Spacelift’s pricing FAQ says it qualifies as a SaaS partner for AWS PPA commitments. That statement does not identify a Self-Hosted private-offer entitlement or its eligible billed dimensions. Confirm the selected Enterprise Self-Hosted order and buyer agreement; private-worker SaaS procurement is a separate boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://spacelift.io/pricing (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html. Supporting source: Public versus sales-assisted private procurement — https://docs.spacelift.io/product/billing/aws-marketplace.

- Single sign-on: Documented. The self-hosted documentation supports SAML 2.0 or OIDC SSO and describes the transition from managed-IdP bootstrap to SSO administration. Login policies are not evaluated for the bootstrap/SSO admin, so protect and govern those accounts explicitly. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/ (reviewed 2026-11-18).

- SCIM provisioning: Documented. The self-hosted SCIM 2.0 integration provisions users/groups with OAuth client credentials and requires configured SSO. Provisioning does not grant roles by itself; the corresponding group claims must also be sent during login. The self-hosted change log confirms availability from v6.1.0. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/scim (reviewed 2026-11-18). Supporting source: Self-hosted v6.1.0 release boundary — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog.

- Compliance attestations: Sources checked — unresolved. Spacelift’s Trust Center says it uses ISO 27001 internally but is not ISO 27001 certified, and instead maintains SOC 2 Type II assurance. The self-hosted security guide also claims SOC 2. Obtain the current report period, system boundary and customer controls before applying that claim to a customer-operated backend; a SaaS/private-worker assessment alone would not settle this boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://trust.spacelift.io/faq (reviewed 2026-11-18). Supporting source: Self-hosted security statement and customer patch responsibilities — https://docs.spacelift.io/self-hosted/latest/product/security.

- Security controls: Documented. Spacelift documents security boundaries for code/state/secrets and integrations. Self-hosting adds customer-managed encryption keys, backend database/object storage and private workers. SSO/SCIM configuration and worker permissions remain distinct from cloud-target authorization. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/product/security (reviewed 2026-11-18). Supporting source: Customer backend dependencies — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements. Supporting source: SSO administrator behavior — https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/.

- Air-gapped operation: Documented. The vendor documents isolated deployment, local VCS, cached IaC providers/CLI binaries, custom runner images and manual usage/licence handling. EC2 launchers require customer-staged artifacts. Repeat this preparation for upgrades and ensure IdP/cloud targets are reachable within the selected boundary. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The self-hosted Helm chart is versioned v7.2.0 and now tracks the application release. Provider-specific Terraform/OpenTofu modules provision backing infrastructure separately. Pin chart, images, modules and worker artifacts as a compatible set; do not confuse old 0.x chart versions with application versions. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0 (reviewed 2026-11-18). Deployment artifact: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0. Artifact reference: Spacelift self-hosted Helm chart v7.2.0. Supporting source: EKS reference deployment — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks.

- Minimum footprint / sizing: Documented. The reference architecture requires PostgreSQL 14+, object storage, container orchestration, encryption keys and separate application/worker connectivity. This establishes component dependencies, not a fixed CPU/RAM minimum. Concurrent runs and worker jobs drive capacity independently of user count. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements (reviewed 2026-11-18).

- License pricing: Documented. Self-Hosted is a commercial Enterprise purchase requiring a quote and licence. Public SaaS plan/worker prices do not price this deployment. Confirm backend, private workers, feature entitlement, usage reporting and renewal terms. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://spacelift.io/pricing (reviewed 2026-11-18). Supporting source: Isolated deployment licence/usage handling — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped.

- Operating cost estimate: Sources checked — unresolved. Specify parallel runs, worker instance sizes and run duration, state/artifact/log retention, HA backend/DB, optional messaging transport, source-control/IdP dependencies and Enterprise pricing. One hundred users do not determine worker concurrency or the cloud resources those jobs manage. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. Spacelift self-hosted chart v7.2.0 was published November 11, 2026 and aligns with the application release. Review the self-hosted changelog and upgrade path. The DinD worker chart reaches EOL February 1, 2027; v7 is also the last major with CloudFormation installation support. Scope: Spacelift Self-Hosted: selected customer-operated edition. Source: https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0 (reviewed 2026-11-18). Supporting source: Self-hosted changes and deprecations — https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog.




### Security and lifecycle reviews

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

- Spacelift DinD worker Helm chart support ends February 2027 (lifecycle): The Docker-in-Docker worker chart reaches end of life February 1, 2027. Existing charts remain available/runnable, but receive no new versions, fixes or support. Scope: DinD worker Helm chart only; Docker workers on EC2 and the main self-hosted service are not retired by this notice. Conditions: Only installations using the DinD chart require this worker migration. CloudFormation has a separate version-based boundary: v7 is its last supported major. Action: Migrate DinD pools to operator-managed Kubernetes workers. Separately move CloudFormation installations to Terraform/OpenTofu while on v7 before considering v8. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog; reviewed 2026-11-18.

- Spacelift self-hosted component CA trust update (security-advisory): The v7.1.0 changelog updates shipped Go components/images to reject compromised eMudhra intermediate certificate chains and names CVE-2026-111943. Scope: Self-hosted components, launchers/workers and shipped Docker images covered by the vendor’s v7.1.0 security entry; IaC binaries used by stacks are separate. Conditions: TLS trust depends on component/binary version and connection path. The vendor also identifies fixed OpenTofu versions; updating the backend alone does not replace every stack binary. Action: Use a self-hosted release containing the fix, refresh affected worker/launcher images and upgrade stack OpenTofu versions according to the changelog. Source: https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog; reviewed 2026-11-18.




## SuperPlane Enterprise Self-Hosted

Enterprise software-factory and agent-workflow platform installed with Terraform and Helm in a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/superplane-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment.
- Licensing model: commercial-only
- Installation: Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release
- Architecture: Customer-operated Kubernetes cluster, managed PostgreSQL and object storage, Fleet Manager and runner virtual machines.
- Operations: Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.
- Product website: https://superplane.com/
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.

The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements.

Terraform provisions persistent Kubernetes application services, managed PostgreSQL and object storage, while Fleet Manager creates runner virtual machines.


### Category fit

- devops: Coordinates coding agents, source control, CI, review and verified software-delivery work.

- workflow-automation: Defines durable automation lines, approvals, checks and repair loops for recurring engineering work.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.superplane.com/self-hosting/overview/ (checked 2026-11-17). 


### Cloud deployment evidence

- SuperPlane Enterprise on EKS, AKS and GKE (aws, azure, gcp): https://docs.superplane.com/self-hosting/overview/
  SuperPlane documents Terraform-created EKS, AKS and GKE clusters with managed PostgreSQL, object storage and Helm releases in the customer's account. Enterprise licensing is required; Google Cloud runner images must currently be built by the operator with Packer.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Self-hosted editions and provider architectures: https://docs.superplane.com/self-hosting/overview/

- Provider-specific Enterprise installation: https://docs.superplane.com/self-hosting/install/

- SuperPlane pricing and Enterprise self-hosting: https://superplane.com/pricing/

- Upstream Apache-2.0 project: https://github.com/superplanehq/superplane

### Licensing sources

- https://docs.superplane.com/self-hosting/overview/

- https://superplane.com/pricing/

### Infrastructure sources

- https://docs.superplane.com/self-hosting/overview/

- https://docs.superplane.com/self-hosting/install/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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. Enterprise installation and direct commercial terms are documented; a current cloud Marketplace offer for this Kubernetes edition was not established. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Enterprise custom terms do not establish an eligible Marketplace offer, qualifying fees or cloud-commitment treatment. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The plan comparison includes SSO in Enterprise together with Enterprise self-hosting. Confirm the required IdP protocol and configuration with the vendor; these entitlements do not apply to the separate community VM edition. Scope: Enterprise self-hosting plan. Source: https://superplane.com/pricing/ (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise includes automated user provisioning, but the pricing table does not name SCIM or document its endpoint, operations and identity-provider limitations. Scope: Enterprise automated provisioning; protocol not established. Source: https://superplane.com/pricing/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SuperPlane Enterprise Self-Hosted material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Security controls: Documented. The provider installation separates infrastructure provisioning, application secrets and runner management. Protect Terraform state, generated credentials and license material; configure TLS/DNS and restrict the provider permissions used by the installer. Scope: Enterprise Kubernetes provider installation. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The standard installer downloads charts, images and provider tooling and configures public DNS/certificates. A supported offline licensing, dependency-transfer and upgrade workflow was not established in this guide. Scope: Enterprise installation; no inference from running in a private VPC. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Provider-specific Terraform creates the managed Kubernetes, PostgreSQL and storage dependencies; Helm installs the application and Fleet Manager controls runners. GCP requires building runner images with Packer rather than using the published AWS/Azure images. Scope: Enterprise installer and provider dependencies; community VM is a different path. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The Enterprise guide requires managed Kubernetes, PostgreSQL, object storage and separately provisioned runners. Runner defaults and example machine types are component settings, not a measured minimum for the complete Enterprise service. Scope: Enterprise topology requirements; size the cluster and runners separately. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- License pricing: Documented. The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements. Scope: SuperPlane Enterprise Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.superplane.com/self-hosting/overview/ (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Price EKS, RDS HA PostgreSQL, storage and runner pools after the Enterprise bill of materials and active-runner concurrency are confirmed. Hosted sandbox/model charges do not price this deployment. 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://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. The installer names component/chart revisions, while the latest GitHub release is Fleet Manager v0.1.7. Neither alone establishes the current Enterprise application bundle and supported upgrade compatibility. Scope: Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment. Source: https://docs.superplane.com/self-hosting/install/ (reviewed 2026-11-17).







## SUSE Multi-Linux Manager 5.2

Open-source Linux infrastructure management and automation platform deployed as a customer-operated container or cloud virtual machine.

- Listing: https://launchinyourcloud.com/directory/suse-multi-linux-manager/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source product based on Uyuni with component open-source licenses; SUSE subscriptions, support, images and trademarks use separate commercial terms.
- Licensing model: open-source
- Installation: SUSE Multi-Linux Manager 5.2 container with mgradm on SL Micro 6.2 or SLES 15 SP7, or a SUSE-provided cloud VM image
- Architecture: Customer-operated management server container with persistent repositories, database data, proxy services and managed-system connections.
- Operations: Customer manages the cloud VM, private networking, DNS, storage, server and proxy containers, repository synchronization, backups, upgrades and registered systems.
- Product website: https://www.suse.com/products/multi-linux-manager/
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

SUSE documents public-cloud installation tested on Amazon EC2, Google Compute Engine and Microsoft Azure. Keep the server on a restricted private network with working forward-confirmed reverse DNS and external persistent disks for repositories and database data. AWS supports PAYG and BYOS; Azure supports BYOS, while the public guide's GCP path is a tested customer-operated installation rather than a confirmed marketplace billing offer. Public-cloud proxies are BYOS-only.

SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms.

The supported 5.2 deployment runs persistent server and proxy containers on customer virtual machines with large durable repository and database volumes.


### Category fit

- devops: Automates Linux provisioning, patching, configuration, monitoring, inventory and compliance operations across managed systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html (checked 2026-11-17). Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html (checked 2026-11-17). Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html (checked 2026-11-17). 


### Cloud deployment evidence

- SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE (aws, azure, gcp): https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html
  SUSE states that its public-cloud requirements and procedures were tested on Amazon EC2, Microsoft Azure and Google Compute Engine. The customer operates the instance, DNS, private networking and durable storage; billing and image availability differ by provider.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SUSE Multi-Linux Manager BYOS and PAYG public-cloud models (aws, azure): https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html
  The public-cloud guide documents BYOS on AWS and Azure and PAYG on AWS. This evidence qualifies procurement models; it does not extend PAYG availability to Azure or Google Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- SUSE Multi-Linux Manager 5.2 documentation: https://documentation.suse.com/multi-linux-manager/5.2/

- Public-cloud requirements for EC2, GCE and Azure: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html

- Public Cloud Guide and subscription models: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html

- SUSE Multi-Linux Manager 5.2 container deployment: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html

- SUSE Multi-Linux Manager 5.2 release notes: https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html

- Product and subscription overview: https://www.suse.com/products/multi-linux-manager/

### Licensing sources

- https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html

- https://www.suse.com/products/multi-linux-manager/

### Infrastructure sources

- https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html

- https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html


### 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: Edition-dependent. The public-cloud guide documents AWS BYOS/PAYG and Azure BYOS routes. Google Cloud is tested but a corresponding Marketplace offer is not established by the guide; proxies are BYOS only. Scope: Product-specific public-cloud delivery variants. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. AWS PAYG and BYOS variants have different entitlement/billing terms. The public-cloud guide does not establish qualifying charges under a buyer commitment agreement. Scope: Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html (reviewed 2026-11-17).

- Single sign-on: Documented. Multi-Linux Manager supports SAML 2 SSO with signed/encrypted assertions and SP metadata. The corresponding Manager user must exist before enabling SSO; selecting an IdP and its support remain customer responsibilities. Scope: SUSE Multi-Linux Manager 5.2 server authentication. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The SAML guide requires the Manager user to exist before enabling SSO. It does not establish a SCIM endpoint or automatic lifecycle provisioning. Scope: Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SUSE Multi-Linux Manager 5.2 material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- Security controls: Documented. The SSO workflow requires mapping the IdP uid to an existing Manager user and protecting signing/encryption material. SSO does not automatically provision accounts or grant other SUSE products the same identity support. Scope: Manager identity trust; not SCIM or a certification. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The reviewed 5.2 administration PDF identifies itself as Beta 1 and describes disconnected repository synchronization. It does not settle the supported GA installation, subscription renewal, container updates and client-content transfer workflow. Scope: Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment. Source: https://documentation.suse.com/multi-linux-manager/5.2/pdf/en/suse_multi_linux_manager_administration_guide.pdf (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The 5.2 server workflow deploys containers using mgradm on the supported host OS, with persistent volumes and separately prepared repository/database storage. Select the matching BYOS/PAYG cloud image and entitlements. Scope: Multi-Linux Manager container deployment. Source: https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Size the server and proxy for managed clients and mirrored repositories, not human users. PostgreSQL must be local; remote PostgreSQL and NFS database storage are unsupported. Separate persistent repository/database devices and supported filesystems are recommended. Scope: 5.2 storage and database requirements; not an approved active-active HA design. Source: https://documentation.suse.com/multi-linux-manager/5.2/en/docs/installation-and-upgrade/hardware-requirements.html (reviewed 2026-11-17).

- License pricing: Documented. SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms. Scope: SUSE Multi-Linux Manager 5.2: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify managed clients, OS repositories/proxies, subscription units and a supported HA/recovery design. The guide requires local PostgreSQL, so substituting RDS Multi-AZ is not established. 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://documentation.suse.com/multi-linux-manager/5.2/en/docs/installation-and-upgrade/hardware-requirements.html (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The reviewed 5.2 Server notes include 5.2.1 updates, PostgreSQL 18, platform changes and security fixes. Kubernetes deployment remains a Technology Preview; the notes document host/feature support separately from container and proxy versions. Scope: 5.2 Server release notes; document revision time is not a software release timestamp. Source: https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html (reviewed 2026-11-17).







## SUSE Security (NeuVector)

Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.

- Listing: https://launchinyourcloud.com/directory/suse-security-neuvector/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
- Licensing model: open-source
- Installation: SUSE Security Helm chart or manifests on public-cloud Kubernetes
- Architecture: Manager, controller and scanner services plus an enforcer DaemonSet inside the customer Kubernetes cluster.
- Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
- Product website: https://www.suse.com/products/security/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.

NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.

SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.


### Category fit

- devops: Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.

- observability: Provides workload, network and security-event visibility for Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 


### Cloud deployment evidence

- SUSE Security on six named public-cloud Kubernetes services (aws, azure, gcp, ibm, alibaba, oci): https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html
  SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

NeuVector publishes contribution/governance instructions and maintained public application and Helm releases. This is sustained upstream participation rather than a star-count threshold; commercial SUSE support remains a separately purchased entitlement.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/blob/main/CONTRIBUTING.md

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/releases/tag/v5.6.4

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4

### Sources

- Deploy SUSE Security on public-cloud Kubernetes: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html

- Deploy SUSE Security with Helm: https://documentation.suse.com/cloudnative/security/latest/en/helm.html

- SUSE Security support matrix: https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/

- NeuVector Apache 2.0 license: https://github.com/neuvector/neuvector/blob/main/LICENSE

### Licensing sources

- https://github.com/neuvector/neuvector/blob/main/LICENSE

### Infrastructure sources

- https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 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: Edition-dependent. SUSE’s security guide routes AWS procurement through its multi-product Rancher/SUSE subscription offer. The current offer is a private-offer commercial contract labelled SaaS delivery; it is not a standalone upstream OSS AMI or proof of included NeuVector support. Confirm the Security entitlement in the order. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html (reviewed 2026-11-18). Supporting source: Actual SUSE Cloud Marketplace Program offer — https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw. Offer prodview-b6es6ar6n4siw: SUSE; SaaS-labelled multi-product private-offer subscription; https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw.

- Cloud commitment eligibility: Sources checked — unresolved. The multi-product private-offer route does not settle the buyer’s commitment eligibility or whether SUSE Security is included in the selected contract. Confirm exact entitlement, billable dimensions and cloud agreement. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. The v5.6 guide documents SAML 2.0 SSO, including Okta and group-to-role mapping. Signed assertions are required; encrypted assertions are not supported by this documented configuration. Set a deliberate default role rather than assuming group import grants appropriate access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. SAML group-to-role mapping does not establish a SCIM server or provisioning/deprovisioning operations. Confirm a current endpoint and user-removal behavior for the selected OSS or subscription-delivered edition. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- Compliance attestations: Documented. LRQA certificate 10726335 covers SUSE’s ISO/IEC 27001:2022 ISMS and ISO/IEC 27701:2019 PIMS; schedule page 28 explicitly includes NeuVector, LLC. Issued November 4, 2025, it expires November 3, 2028. This is organisational information/privacy management assurance, not certification of a customer’s NeuVector cluster, protected workloads, configuration or operations. Scope: SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation. Source: https://www.suse.com/support/security/certifications/SUSE-ISO-27001-ISO-27701.pdf (reviewed 2026-11-18). Supporting source: Official SUSE certificate index — https://www.suse.com/support/security/certifications/isoiec-certification/.

- Security controls: Documented. NeuVector documents SAML role mapping and signed-assertion requirements. Enforcers run on cluster nodes and controllers coordinate security policy, so deployment needs the documented privileged access and network visibility. Scope cluster roles and protect console/controller access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18). Supporting source: Runtime and component requirements — https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html. Supporting source: Cloud network and topology requirements — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- Air-gapped operation: Documented. The air-gap guide mirrors charts and images using Skopeo/zstd, transfers them and deploys from an internal registry. Its example versions are older than the current 5.6 line; resolve matching current application/chart/scanner versions and arrange offline vulnerability-database updates. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/airgap.html (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. NeuVector maintains a Helm chart for manager/controller/enforcer/scanner deployment. The reviewed chart release is v2.11.4, separate from application v5.6.4. Pin image tags and check values/privileges; air-gap documentation’s historical chart example is not a current version pin. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/latest/en/helm.html (reviewed 2026-11-18). Deployment artifact: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4. Artifact reference: NeuVector Helm chart v2.11.4.

- Minimum footprint / sizing: Documented. The requirements recommend three controllers for HA, an enforcer on each worker and separate scanner/manager resources. Controller minimum is 1 CPU/2 GB; an enforcer needs 1+ CPU/1 GB and a scanner 1 CPU/2 GB before workload growth. The public-cloud guide warns against multiple managers behind a load balancer because of session state, while requirements suggest manager redundancy; resolve that design before claiming full HA. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Manager scaling caveat and cloud topology — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- License pricing: Documented. Upstream NeuVector is Apache 2.0 licensed. SUSE subscription-delivered images, support and Rancher Prime integrations may require commercial entitlements. The multi-product AWS order is distinct from the free upstream code licence. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/blob/main/LICENSE (reviewed 2026-11-18). Supporting source: SUSE commercial procurement path — https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html.

- Operating cost estimate: Sources checked — unresolved. Size by protected Kubernetes node count, network throughput, container/image scan volume, registry retention and HA controller/scanner design, not directory users. Include per-node enforcers, scan capacity, persistent configuration and any SUSE support subscription. The manager redundancy conflict also needs resolution. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. NeuVector v5.6.4 was published October 27, 2026; chart v2.11.4 is a separate release. When upgrading from before v5.6.0, SUSE requires restarting/redeploying existing scanner pods for critical CVE severity handling. Maintenance releases on older branches are not a newer major-line snapshot. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/releases/tag/v5.6.4 (reviewed 2026-11-18). Supporting source: 5.6.4 upgrade and scanner requirements — https://documentation.suse.com/cloudnative/security/5.6/en/5x.html. Supporting source: Separate chart release — https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4.




### Security and lifecycle reviews

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

- NeuVector scanner restart required for critical-severity results (security-advisory): SUSE requires existing scanner pods to restart or redeploy when upgrading from before 5.6.0 to 5.6.4 or later, so cached capabilities recognize critical CVE severity. Scope: Upgrades from pre-5.6.0 controllers with existing scanner pods; not a claim of a new exploitable vulnerability in every NeuVector installation. Conditions: Older scanners cache the controller capability response. SUSE also calls for current scanner/CVE database content for PHP vulnerability checks. Action: Follow the 5.6.4 scanner restart and database-update instructions, including the transfer process in isolated environments. Source: https://documentation.suse.com/cloudnative/security/5.6/en/5x.html; reviewed 2026-11-18.




## Terraform Enterprise

Commercial self-hosted Terraform collaboration and infrastructure-automation platform.

- Listing: https://launchinyourcloud.com/directory/terraform-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Terraform Enterprise license required.
- Licensing model: commercial-only
- Installation: Official HashiCorp Terraform modules for EC2, EKS, Azure VMs, AKS, GCE or GKE; Kubernetes or OpenShift workflow on IBM Cloud
- Architecture: Containerized Terraform Enterprise application with customer-managed runtime, data storage and worker capacity
- Operations: Customer manages compute or Kubernetes, PostgreSQL and object storage, cache, networking, TLS, identity, worker images, backups, scaling, upgrades and licensing.
- Product website: https://developer.hashicorp.com/terraform/enterprise
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers Terraform Enterprise, the self-hosted distribution, not HCP Terraform. Match the selected runtime to the current compatibility matrix and review the module's IAM, managed-identity, database, object-storage and network requirements before applying it.

Terraform Enterprise is a commercial self-hosted product and requires a valid license file or license server configuration.

Terraform Enterprise runs as persistent containers on VM or Kubernetes runtimes with durable database and object-storage dependencies.


### Category fit

- devops: Provides self-hosted infrastructure-as-code runs, workspaces, policy controls, private registry and team workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (checked 2026-11-15). 


### Cloud deployment evidence

- Official Terraform Enterprise modules and provider guidance (aws, azure, gcp): https://developer.hashicorp.com/terraform/enterprise/deploy
  HashiCorp lists official Terraform Enterprise modules for AWS EC2 and EKS, Azure VMs and AKS, and Google GCE and GKE, together with provider-specific deployment guidance for customer environments.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Terraform Enterprise on IBM Cloud (ibm): https://developer.hashicorp.com/terraform/enterprise/deploy
  HashiCorp explicitly directs IBM Cloud Kubernetes Service users to its Kubernetes deployment workflow, and Red Hat OpenShift users to its OpenShift workflow. It also links the IBM Cloud deployable architecture. This is separate from the EC2, Azure and Google Cloud validated modules.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Terraform Enterprise deployment overview and cloud modules: https://developer.hashicorp.com/terraform/enterprise/deploy

- Terraform Enterprise license configuration: https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/license

### Licensing sources

- https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/license

### Infrastructure sources

- https://developer.hashicorp.com/terraform/enterprise/deploy


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The vendor validates SAML 2.0 integration and requires connectivity to the identity provider metadata endpoint at login. Configure the Enterprise identity integration and recovery access; an air-gapped deployment needs a reachable internal IdP. Scope: Terraform Enterprise SAML login and metadata connectivity. Source: https://developer.hashicorp.com/validated-designs/terraform/installation-guide/air-gapped-configuration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. HashiCorp links official deployment modules for AWS EC2/EKS, Azure VM/AKS and Google Cloud GCE/GKE. Select a supported Enterprise version, runtime and storage arrangement before using the appropriate module. A module is not a software license. Scope: Terraform Enterprise flexible deployment overview and HashiCorp Validated Designs. Source: https://developer.hashicorp.com/terraform/enterprise/deploy (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The validated design gives per-node application baseline 4 vCPUs/32 GB/1 TB, PostgreSQL 4 cores/32 GB/2 TB, and Redis 4 cores/16 GB/500 GB. It notes larger initial application nodes are common. Execution concurrency, per-run memory, availability and object storage require separate sizing. Scope: Vendor validated-design baseline; execution workers and HA topology additional. Source: https://developer.hashicorp.com/validated-designs/terraform/installation-guide/detailed-design (reviewed 2026-11-20).

- License pricing: Documented. HashiCorp identifies Terraform Enterprise as closed-source commercial software. It requires Enterprise entitlement; Terraform CLI source-available terms do not license the Enterprise service. The reviewed product documentation does not establish a numeric price; obtain a current licence/support quote. Scope: Terraform Enterprise commercial licensing; CLI and HCP pricing excluded. Source: https://developer.hashicorp.com/terraform/docs/glossary (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






