
# IBM Maximo Application Suite (BYOL)

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

Canonical page: https://launchinyourcloud.com/directory/ibm-maximo-application-suite/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




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


1 listing.


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






