
# Software on IBM Cloud

Explore software with documented IBM Cloud deployment, customer-account guidance, licensing qualifications and source evidence.

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


## Provider guidance

- Account boundary: IBM Cloud account and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://github.com/ibm-cloud-docs/vpc/blob/master/vsi_is_create_instance.md (checked 2026-11-20).
- Network: VPC, subnets and security groups
- Identity and access: Cloud access controls and server SSH keys
- Installation guidance: Provision virtual servers through the console, CLI, API or Terraform; obtain and configure the selected vendor private application package.
- Guidance source: https://github.com/ibm-cloud-docs/vpc/blob/master/vsi_is_create_instance.md
- Guidance reviewed: 2026-11-12


### VPC isolation

IBM Cloud VPC provides logical network isolation with private subnets. Review application segmentation and access policies; a platform compatibility statement does not establish a current installer or support agreement.
Source: https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc (reviewed 2026-11-14).

The listings below have evidence for IBM Cloud. Read each cloud evidence note for the applicable package, edition and support qualifications.

9 listings.


## IBM Cognos Analytics Certified Containers

Customer-managed enterprise reporting and analytics deployed by Helm to a Kubernetes cluster in the customer's cloud.

- Listing: https://launchinyourcloud.com/directory/ibm-cognos-analytics-certified-containers/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial, separately licensed Cognos Analytics Certified Containers entitlement.
- Licensing model: commercial-only
- Installation: Install IBM's entitled Cognos Analytics Helm chart on customer-managed Kubernetes
- Architecture: Customer-operated Kubernetes cluster running IBM Cognos containers with external databases, authentication, storage and ingress.
- Operations: Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.
- Product website: https://www.ibm.com/products/cognos-analytics
- 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 Cognos Analytics Certified Containers, not IBM-hosted or on-demand Cognos offerings. Installation requires an IBM entitlement key and registry access. Support on EKS, AKS, GKE and other non-OpenShift platforms is narrower than on Red Hat OpenShift and is focused on the Cognos software, certified images, Helm orchestration, deployment and updates.

Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key.

The product runs as persistent containerized services on a customer Kubernetes cluster and requires external stateful services, ingress and production capacity planning.


### Category fit

- data-analytics: Enterprise reporting, dashboards, governed analytics and data exploration delivered by customer-managed Cognos containers.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration (checked 2026-11-17). 


### Cloud deployment evidence

- Cognos Certified Containers on EKS, AKS and GKE (aws, azure, gcp): https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models
  IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Cognos Certified Containers on IBM Cloud Kubernetes Service (ibm): https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration
  IBM's Cognos ingress framework explicitly names IBM Cloud Kubernetes Service alongside EKS, AKS and GKE. The customer operates the cluster and external dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cognos Analytics offerings: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings

- Certified Containers overview: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview

- Container delivery support policy: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models

- Ingress configuration for named Kubernetes services: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration

- Installing and deploying Certified Containers: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers

### Licensing sources

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers

### Infrastructure sources

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 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. Entitled registry images and Helm installation are documented; a current Marketplace offer for this Certified Containers edition was not established. Cognos hosted offerings are separate. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Container entitlement and registry access do not establish qualifying Marketplace spend or contract-specific cloud credit eligibility. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Single sign-on: Documented. Cognos 12.1.x documents dynamic OpenID Connect namespaces with a configured supported IdP and administrative capabilities. Confirm the namespace/provider settings for the selected container deployment. Scope: Cognos 12.1.x identity configuration; not a Cloud-only entitlement. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The reviewed 12.1.x namespace guide supports LDAP/OIDC providers, but does not establish a Certified Containers SCIM endpoint and lifecycle operations. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed IBM Cognos Analytics Certified Containers 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://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).

- Security controls: Documented. IBM bulletin 7250395 identifies Certified Containers 12.1.0 vulnerabilities and names 12.1.1 as the fix. Check the deployed container release against current bulletins; this historical fix is not a claim that newer releases have no vulnerabilities. Scope: Certified Containers 12.1.0-specific security bulletin; historical affected/fixed scope. Source: https://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Registry entitlement and Helm deployment alone do not establish the complete offline image, licence, dependency and update workflow for Certified Containers. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. IBM supplies entitled container images and Helm deployment for Certified Containers. Obtain the registry entitlement and configure ingress, persistent storage and the selected cluster; OpenShift and other Kubernetes platforms have different support boundaries. Scope: Cognos Analytics 12.1.x Certified Containers. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed container installation requires cluster, storage and deployment configuration, but did not establish a complete numerical HA sizing model for 100 users/1 TB, including reporting concurrency and auxiliary services. Scope: Certified Containers sizing; desktop/agent-only requirements excluded. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- License pricing: Documented. Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key. Scope: IBM Cognos Analytics Certified Containers: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the current entitled container bundle, report concurrency, HA services, content-store database, storage and licence metric. User count and data volume do not size reporting/AI dependencies. 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://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. IBM identifies container release-specific fixes, including 12.1.0 to 12.1.1 remediation, but the reviewed public records did not establish the latest entitled container/chart bundle and publication date. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Cognos Certified Containers 12.1.0 fixes available (security-advisory): IBM bulletin 7250395 identifies PostgreSQL JDBC and information-disclosure vulnerabilities in Certified Containers 12.1.0, with 12.1.1 named as the fix. Scope: IBM bulletin published 2025-11-07 for Certified Containers 12.1.0; not a claim that every newer Cognos release or deployment is affected. Conditions: Exposure depends on the affected components and CVE-specific prerequisites in the bulletin. The reviewed record does not establish the current entitled container bundle. Action: Check the installed container version and current IBM bulletins. For affected 12.1.0 deployments, obtain the designated fixed or later supported bundle and follow the vendor upgrade procedure. Source: https://www.ibm.com/support/pages/node/7250395; reviewed 2026-11-17.




## IBM Maximo Application Suite (BYOL)

Customer-managed asset maintenance, work-order and enterprise asset management suite.

- Listing: https://launchinyourcloud.com/directory/ibm-maximo-application-suite/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Kubernetes manifests
- Architecture: Maximo Application Suite on Red Hat OpenShift on IBM Cloud VPC with persistent data services.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/ibm-cloud-docs/maximo-application-suite
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

IBM deployment automation provisions the actual application, not only an OpenShift cluster. Maximo and Red Hat subscription and AppPoints requirements must be agreed separately.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Maximo Application Suite on Red Hat OpenShift on IBM Cloud VPC with persistent data services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed asset maintenance, work-order and enterprise asset management suite.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da (checked 2026-11-19). 


### Cloud deployment evidence

- IBM Cloud Docs (ibm): https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da
  Maximo Application Suite on Red Hat OpenShift on IBM Cloud VPC with persistent data services. IBM deployment automation provisions the actual application, not only an OpenShift cluster. Maximo and Red Hat subscription and AppPoints requirements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- IBM Cloud Docs: https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da

- GitHub deploy.md: https://raw.githubusercontent.com/ibm-cloud-docs/maximo-application-suite/master/deploy.md

- IBM Terms (IPLA): https://www.ibm.com/support/customer/csol/terms/?id=Z125-3301

- GitHub plan.md (License Key Center): https://raw.githubusercontent.com/ibm-cloud-docs/maximo-application-suite/master/plan.md

- IBM Support Licensing: https://www.ibm.com/support/pages/ibm-support-licensing-start-page

- MAS CLI 9.1/9.2 Docs: https://ibm-mas.github.io/cli/

- MAS CLI Releases: https://github.com/ibm-mas/cli/releases

- MAS Ansible Releases: https://github.com/ibm-mas/ansible-devops/releases

### Licensing sources

- https://www.ibm.com/support/customer/csol/terms/?id=Z125-3301

- https://raw.githubusercontent.com/ibm-cloud-docs/maximo-application-suite/master/plan.md

- https://www.ibm.com/support/pages/ibm-support-licensing-start-page

### Infrastructure sources

- https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 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. IBM documents Maximo Application Suite SAML 2.0 federation with external identity providers such as IBM Security Verify, Keycloak, Okta and Microsoft Entra ID. Configure identity mapping and authentication flows for the installed suite release; the article does not establish every newer protocol or provider combination. Scope: Customer-operated Maximo Application Suite SAML integration; not a hosted-service entitlement or blanket protocol limitation. Source: https://developer.ibm.com/articles/single-sign-on-multi-factor-authentication-integration-with-maximo-application-suite/ (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. IBM documents a catalog deployable architecture through IBM Cloud Projects/Schematics and an official Terraform module. It requires an existing supported OpenShift cluster, entitled registry key and MAS licence file; Core and Core + Manage have different dependencies. Scope: IBM Cloud MAS deployable architecture; version-match the module, suite, database and OpenShift cluster. Source: https://github.com/ibm-cloud-docs/maximo-application-suite/blob/master/deploy.md (reviewed 2026-11-20). Deployment artifact: https://github.com/terraform-ibm-modules/terraform-ibm-mas/tree/24ddaef186771dc4996645c45de84d7ea500933d. Artifact reference: 24ddaef186771dc4996645c45de84d7ea500933d (configuration commit cited by the planning guide; verify suite compatibility). Supporting source: Planning and entitlement prerequisites — https://github.com/ibm-cloud-docs/maximo-application-suite/blob/master/plan.md.

- Minimum footprint / sizing: Sources checked — unresolved. The deployable-architecture guide requires an existing OpenShift cluster and describes 300 GB secondary ephemeral storage per node. That is a storage prerequisite, not a complete suite CPU/RAM/database minimum. Size the selected MAS applications, MongoDB, Db2, storage and HA roles separately. Scope: MAS Core versus Core + Manage on customer OpenShift; selected application and database sizing remains unconfirmed. Source: https://github.com/ibm-cloud-docs/maximo-application-suite/blob/master/plan.md (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: IBM Maximo Application Suite (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.ibm.com/support/customer/csol/terms/?id=Z125-3301 (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## IBM OpenPages on Software Hub

Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.

- Listing: https://launchinyourcloud.com/directory/ibm-openpages/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Kubernetes manifests
- Architecture: OpenPages 9.2.1.1 cartridge on IBM Software Hub 5.4 Patch 4 and customer Red Hat OpenShift on IBM Cloud.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/ibm-cloud-docs/cloud-pak-data
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cartridge version and underlying Software Hub/OpenShift matrix must be matched. Standalone OpenPages 9.2.2 release availability does not establish that version for the selected cartridge. IBM-hosted OpenPages as a Service is a different deployment.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

OpenPages 9.2.1.1 cartridge on IBM Software Hub 5.4 Patch 4 and customer Red Hat OpenShift on IBM Cloud. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.

- vendor-supplier-document-management: Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md (checked 2026-11-19). 


### Cloud deployment evidence

- CP4D Services Install (OpenPages) (ibm): https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md
  OpenPages 9.2.1.1 cartridge on IBM Software Hub 5.4 Patch 4 and customer Red Hat OpenShift on IBM Cloud. The cartridge version and underlying Software Hub/OpenShift matrix must be matched. Standalone OpenPages 9.2.2 release availability does not establish that version for the selected cartridge. IBM-hosted OpenPages as a Service is a different deployment.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- CP4D Services Install (OpenPages): https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md

- IBM OpenPages: https://www.ibm.com/products/openpages

- OpenPages 9.2.1 on IBM Software Hub: https://www.ibm.com/support/pages/node/7282885

- OpenPages Cartridge Supported Environments: https://www.ibm.com/support/pages/node/6347144

- IBM Cloud ROKS Docs: https://cloud.ibm.com/docs/openshift?topic=openshift-getting-started

- IBM OpenPages License (L-CBML-R8TYAW): https://www14.software.ibm.com/cgi-bin/weblap/lap.pl?li_formnum=L-CBML-R8TYAW

- OpenPages 9.2 Fix List (9.2.2.1): https://www.ibm.com/support/pages/ibm-openpages-92-fix-list

- OpenPages 9.2.2 Release Notice: https://www.ibm.com/support/pages/node/7289843

- CP4D Docs Commits: https://github.com/ibm-cloud-docs/cloud-pak-data/commits/master

### Licensing sources

- https://www14.software.ibm.com/cgi-bin/weblap/lap.pl?li_formnum=L-CBML-R8TYAW

### Infrastructure sources

- https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md


### Buyer diligence


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

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Software Hub documents centrally managed access to OpenPages instances, including a default administrator used to configure directory/SSO integration and synchronised users/groups. This is the Software Hub-hosted service identity boundary; standalone OpenPages application-server instructions and IBM SaaS authentication are separate deployment paths. Scope: OpenPages on IBM Software Hub 5.4 platform identity and instance access. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=groups-managing-access-openpages-instances (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The cloud guide documents installing the licensed service, but does not establish a public versioned OpenPages cartridge deployment artifact for the selected customer entitlement. Scope: OpenPages cartridge installation workflow versus the base Software Hub platform. Source: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md (reviewed 2026-11-19).

- Minimum footprint / sizing: Documented. The published Software Hub 5.2 x86 table gives OpenPages operand minimums of 6 vCPU/20 GB RAM with 252 GB persistent storage for the described Db2-backed configuration, plus operator/catalog overhead. This version-specific reference excludes the OpenShift/Software Hub platform and is not a validated current 5.4 or HA workload baseline; recheck the selected release and database placement. Scope: Published Software Hub 5.2 OpenPages component example; current-release/platform/HA sizing requires validation. Source: https://www.ibm.com/docs/en/software-hub/5.2.x?topic=requirements-x86-64-hardware (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. The selected OpenPages cartridge has its own version/entitlement scope. A base Software Hub licence does not establish the customer’s OpenPages purchase, users or price. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://www.ibm.com/support/pages/node/6347144 (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## IBM Planning Analytics Cartridge

Licensed self-managed planning, budgeting and multidimensional analytics cartridge.

- Listing: https://launchinyourcloud.com/directory/ibm-planning-analytics/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm, aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Kubernetes manifests
- Architecture: Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/ibm-cloud-docs/cloud-pak-data
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Licensed self-managed planning, budgeting and multidimensional analytics cartridge.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 


### Cloud deployment evidence

- Application deployment guidance (ibm, aws, azure, gcp): https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing
  Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Additional reviewed source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing

- IBM Cloud CP4D Services: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md

- Azure ARO PA Guide (PDF): https://cp4dazuremarketplacedoc.blob.core.windows.net/ibmcp4dazuremarketplace/CP4D_MS_ARO_Deployment_Guide.pdf

- PA Pricing & CP4D Cartridge: https://www.ibm.com/products/planning-analytics/pricing

- CP4D Docs Commits: https://github.com/ibm-cloud-docs/cloud-pak-data/commits/master

- PA CASE Index (v5.4.5): https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml

- PA CASE Commits: https://github.com/IBM/cloud-pak/commits/master/repo/case/ibm-planning-analytics

- Current Software Hub cloud installation environments: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=cluster-installing-red-hat-openshift

- License information for IBM Software Hub 5.4 and related services: https://www.ibm.com/support/pages/node/7275162/

### Licensing sources

- https://www.ibm.com/products/planning-analytics/pricing

### Infrastructure sources

- https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing


### Buyer diligence


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

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed Software Hub cartridge installation context does not establish its exact user SSO configuration. Separate Planning Analytics Cloud IBMid and Advanced Certified Containers OIDC guides apply to different offerings; confirm the cartridge release, platform/user mapping and configured provider before transferring those claims. Scope: Planning Analytics cartridge on Software Hub; selected-edition user federation remains unconfirmed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. IBM publishes a CASE package index for Planning Analytics, separate from Local and SaaS releases. Use the application-specific install-components workflow and keep the cartridge and Software Hub refresh aligned. Scope: Planning Analytics CASE package metadata; select a compatible release and licensed image source. Source: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml (reviewed 2026-11-19). Deployment artifact: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml. Artifact reference: master (moving CASE package index).

- Minimum footprint / sizing: Sources checked — unresolved. Software Hub/OpenShift platform requirements are additional to the Planning Analytics cartridge and model/data resources. A complete current cartridge-specific CPU/RAM/storage and HA baseline was not verified from accessible material; standalone/TM1 or vendor-hosted sizing must not be substituted. Scope: Planning Analytics cartridge current full production sizing remains unconfirmed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: IBM Planning Analytics Cartridge; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.ibm.com/products/planning-analytics/pricing (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Red Hat OpenShift AI Self-Managed

Commercial AI and machine-learning platform installed as an Operator on a customer-operated Red Hat OpenShift cluster.

- Listing: https://launchinyourcloud.com/directory/red-hat-openshift-ai-self-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, oci, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.
- Licensing model: commercial-only
- Installation: OpenShift AI Operator through OperatorHub or the oc command-line interface
- Architecture: OpenShift operators and persistent AI workbench, pipeline, model-serving and supporting services on customer Kubernetes infrastructure.
- Operations: Customer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-ai
- 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 OpenShift AI Self-Managed, not Red Hat's managed cloud-service add-on. Support depends on a compatible OpenShift Container Platform release, storage and accelerator matrix, and active subscriptions. Underlying OpenShift and cloud infrastructure are operated by the customer. RHSA-2026:95872 is a critical OpenShift AI 3.5.3 security update covering nine CVEs. Use Red Hat's package and deployment scope to determine affected components, then apply 3.5.3 or a later supported update.

The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement.

OpenShift AI runs persistent operator-managed workloads on customer OpenShift clusters with storage, compute and optional accelerator dependencies.


### Category fit

- ai-tools: AI workbenches, pipelines, model serving and lifecycle tooling delivered on a customer-operated OpenShift platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 


### Cloud deployment evidence

- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms (aws, azure, gcp, oci, ibm): https://access.redhat.com/articles/rhoai-supported-configs
  Red Hat's Self-Managed matrix explicitly lists OpenShift Container Platform on AWS, Azure, Google Cloud, IBM Cloud and Oracle Cloud. The selected OpenShift release, subscriptions, storage, accelerator and component restrictions apply; managed cloud-service add-ons are a separate offering.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- OpenShift AI supported configurations: https://access.redhat.com/articles/rhoai-supported-configs

- OpenShift AI Self-Managed 3.5 installation and subscription: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install

- RHSA-2026:95872: https://access.redhat.com/errata/RHSA-2026%3A95872

### Licensing sources

- https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install

### Infrastructure sources

- https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install


### 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. OperatorHub installation and required subscriptions do not establish a specific cloud Marketplace offer for the Self-Managed AI entitlement. Managed add-ons and generic OpenShift offers are separate. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Self-Managed AI and underlying OpenShift subscriptions need offer-specific confirmation before software charges are treated as eligible cloud commitment spend. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Single sign-on: Documented. OpenShift AI uses the identity provider configured for its OpenShift cluster. Configure cluster identity and AI user/admin groups; this does not establish a separate application SCIM endpoint. Scope: Self-managed OpenShift AI 3.5 identity through the cluster. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. AI authentication delegates to the OpenShift IdP. The reviewed installation guide does not establish a separate AI SCIM endpoint or the provisioning capabilities of the buyer’s chosen IdP. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat OpenShift AI 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_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Security controls: Documented. Installation requires cluster administrator access, a configured IdP and compatible subscriptions. Configure access groups and certificate trust for workbenches, models, pipelines and object storage. Current advisory review: RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum. Scope: OpenShift AI cluster access prerequisites Red Hat OpenShift AI 3.5 packages identified in the erratum.. Source: https://access.redhat.com/errata/RHSA-2026%3A95872 (reviewed 2026-11-18). Supporting source: Certificate trust in disconnected deployments — https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/working-with-certificates_certs. Supporting source: Prior security-controls source — https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install.

- Air-gapped operation: Documented. Red Hat supplies a separate disconnected installation guide using mirrored Operator/container content. Required model, notebook, accelerator and object-storage dependencies must also be staged for the selected components. Scope: Self-managed OpenShift AI disconnected installation. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Install the supported OpenShift AI Operator on an entitled, compatible OpenShift cluster and enable the required components. Cluster creation, storage, accelerators and model assets remain separate deployment work. Scope: OpenShift AI Self-Managed 3.5 Operator installation. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Installing the Operator requires at least two workers with 8 CPU/32 GiB each; single-node OpenShift requires 32 CPU/128 GiB. Workloads, models, accelerators and storage need additional resources; these installation minima do not establish HA workload capacity. Scope: OpenShift AI 3.5 installation minima; platform/control-plane resources additional. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- License pricing: Documented. The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement. Scope: Red Hat OpenShift AI Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Select OpenShift HA topology, enabled AI components, model size, GPU needs, concurrency, object storage and both subscription entitlements. Operator installation minima do not size inference/training. 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_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Red Hat OpenShift AI 3.5.3 was published as critical security advisory RHSA-2026:95872 on November 6, 2026 and covers nine CVEs. Scope: Red Hat OpenShift AI self-managed 3.5. Source: https://access.redhat.com/errata/RHSA-2026%3A95872 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Red Hat OpenShift AI 3.5.3 critical security update (security-advisory): RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Scope: Red Hat OpenShift AI 3.5 packages identified in the erratum. Conditions: Installed components and package versions determine applicability. Action: Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum. Source: https://access.redhat.com/errata/RHSA-2026%3A95872; reviewed 2026-11-18.




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







## Solix Application Retirement — Customer-Managed

Archive retired applications while retaining searchable access to historical business information.

- Listing: https://launchinyourcloud.com/directory/solix-application-retirement/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci, ibm
- Operating model: Customer-operated
- Infrastructure IDs: unspecified
- License: Commercial Enterprise Edition
- Licensing model: commercial-only
- Installation: Vendor-assisted customer-managed enterprise deployment; confirm supported package/topology
- Architecture: Customer-managed archival platform and data storage
- Operations: Customer-managed deployment is available; agree implementation, support, upgrades and infrastructure ownership with Solix.
- Product website: https://www.solix.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Solix documents application retirement and separately describes customer-managed and self-managed on-premises/private/public-cloud options. This entry excludes fully managed SOLIXCloud SaaS. Public installation commands and specific customer-account hyperscaler deployment paths were not verified.

This entry covers the licensed Enterprise Edition customer-managed application retirement option. Self-management and public-cloud deployment do not imply open-source rights.

Customer-hosted installation is documented, but the reviewed public material does not specify enough runtime detail to classify it. Confirm the supported server or container topology with the vendor.


### Category fit

- legacy-system-archive-access: Dedicated application retirement and historical-data archival access using the customer-managed enterprise option. Vendor-assisted enterprise installation; no public installer was verified. Confirm package, deployment topology and responsibility split.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). Source: https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Solix private deployment and enterprise archiving platform disclosure (aws, azure, gcp, oci, ibm): https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf
  The parent company's 2024-25 annual report, printed page 46/PDF page 48, describes CDP Private on an organization's existing cloud instances with in-house application management. Its Enterprise Archiving architecture includes Application Retirement above named AWS, Azure, Google Cloud, Oracle Cloud and IBM Cloud infrastructure, and states that the bundle is offered privately as well as as SaaS. This is a platform compatibility disclosure, not a release-specific installation guide; confirm the current private package, topology, licenses and operating agreement.
  Source type: corporate-disclosure; reviewed: 2026-11-12; vendor support: not-assessed.

- Solix Application Retirement customer case on a Google Cloud private tenant (gcp): https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf
  The vendor case documents Application Retirement on a Google Cloud private tenant, delivered collaboratively with Kyndryl. It corroborates a real private deployment; it does not by itself establish customer account ownership or customer operations. Use the separate CDP Private disclosure for the customer-operated option and agree the exact contract and support boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Application retirement functionality: https://www.solix.com/products/application-retirement-solution/

- Explicit customer-managed deployment option: https://www.solix.com/solixcloud/

- Enterprise Edition deployment options: https://www.solix.com/products/enterprise-edition/

- Official self-managed private/public-cloud deployment statement: https://www.solix.com/documents/datasheets/solix-cloud-data-management-for-sap.pdf

### Licensing sources

- https://www.solix.com/products/enterprise-edition/

- https://www.solix.com/solixcloud/

### Infrastructure sources

- https://www.solix.com/products/application-retirement-solution/


### Buyer diligence


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

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed product and Enterprise Edition pages describe governance and deployment options but do not establish the customer-managed retirement application identity integration, provider protocol or account mapping. A hosted-service SSO statement cannot settle the selected customer-hosted edition. Scope: Solix customer-managed application retirement SSO remains unconfirmed. Source: https://www.solix.com/products/application-retirement-solution/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The product page mentions SOC 2 and ISO 27001 alongside SolixCloud options. It does not establish an assessed scope for the customer-managed Application Retirement installation. Scope: Customer-managed application versus vendor cloud scope unresolved. Source: https://www.solix.com/products/application-retirement-solution/ (reviewed 2026-11-14).

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Solix advertises implementation services and multiple deployment options, but the reviewed public material does not expose a release-specific installer, chart or infrastructure artifact for customer-managed retirement. Obtain the supported delivery package and deployment procedure. Scope: Customer-managed Solix installation artifact remains unconfirmed. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed enterprise/product material does not establish numeric customer-managed CPU/RAM/storage or HA requirements. Size ingestion, source formats, indexed archive volume, retrieval concurrency and retention separately from the vendor-operated cloud service. Scope: Customer-managed application retirement sizing remains unconfirmed. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- License pricing: Documented. Solix describes Enterprise Edition as a consumption-based commercial bundle including preservation products and application retirement, with on-premises, hybrid and cloud options. Obtain the applicable customer-managed order, consumption metric, support and non-production/DR rights; no SOLIXCloud SaaS rate is substituted for that agreement. Scope: Current Enterprise Edition commercial model; negotiated customer-managed entitlement and price remain order-specific. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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






