Software on IBM Cloud
Software with a documented deployment path in a customer environment on IBM Cloud.
9 listings, including 9 from other publishers. Search and filter IBM Cloud listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- IBM Cloud account and resource group
- Network
- VPC, subnets and security groups
- Identity & access
- Cloud access controls and server SSH keys
- Deployment tooling
- Provision virtual servers through the console, CLI, API or Terraform; obtain and configure the selected vendor private application package.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-12. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- 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. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Browse by category
9 categories on IBM Cloud. Counts show matching listings; a listing can appear in more than one category.
Business operations2 categories
Governance & industries2 categories
Data & analytics1 category
Developer platforms & operations3 categories
AI tools & infrastructure1 category
No categories match your search.
Documented software
Deployment evidence and qualifications
Customer-managed enterprise reporting and analytics deployed by Helm to a Kubernetes cluster in the customer's cloud.
- Cognos Certified Containers on IBM Cloud Kubernetes Service ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
IBM's Cognos ingress framework explicitly names IBM Cloud Kubernetes Service alongside EKS, AKS and GKE. The customer operates the cluster and external dependencies.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.
Scope: 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.
License: Commercial, separately licensed Cognos Analytics Certified Containers entitlement.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Cognos Certified Containers on IBM Cloud Kubernetes Service ↗
Deployment evidence and qualifications
Customer-managed asset maintenance, work-order and enterprise asset management suite.
- IBM Cloud Docs ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: IBM deployment automation provisions the actual application, not only an OpenShift cluster. Maximo and Red Hat subscription and AppPoints requirements must be agreed separately.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- IBM Cloud Docs ↗
Deployment evidence and qualifications
Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.
- CP4D Services Install (OpenPages) ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- CP4D Services Install (OpenPages) ↗
Deployment evidence and qualifications
Licensed self-managed planning, budgeting and multidimensional analytics cartridge.
- Application deployment guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Application deployment guidance ↗
Deployment evidence and qualifications
Commercial AI and machine-learning platform installed as an Operator on a customer-operated Red Hat OpenShift cluster.
- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.
Scope: 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.
License: Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms ↗
Deployment evidence and qualifications
Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
- Self-managed OpenShift on IBM Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-15 · Version: 4.21. Vendor support commitment: not assessed; confirm the selected release and contract.
Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
Scope: 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.
License: Commercial Red Hat OpenShift subscription.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Self-managed OpenShift on IBM Cloud ↗
Deployment evidence and qualifications
Archive retired applications while retaining searchable access to historical business information.
- Solix private deployment and enterprise archiving platform disclosure ↗
Corporate disclosure · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer-managed deployment is available; agree implementation, support, upgrades and infrastructure ownership with Solix.
Scope: 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.
License: Commercial Enterprise Edition
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Solix private deployment and enterprise archiving platform disclosure ↗
Deployment evidence and qualifications
Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.
- SUSE Security on six named public-cloud Kubernetes services ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
Scope: 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.
License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- SUSE Security on six named public-cloud Kubernetes services ↗
Deployment evidence and qualifications
Commercial self-hosted Terraform collaboration and infrastructure-automation platform.
- Terraform Enterprise on IBM Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages compute or Kubernetes, PostgreSQL and object storage, cache, networking, TLS, identity, worker images, backups, scaling, upgrades and licensing.
Scope: 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.
License: Commercial Terraform Enterprise license required.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Terraform Enterprise on IBM Cloud ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings