IBM Maximo Application Suite (BYOL)

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

8 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Kubernetes manifests

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • IBM Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    IBM Cloud Docs ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodKubernetes manifests
InfrastructureServers / containers
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.
Licensing modelCommercial Only
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
LicenseCommercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Customer-operated Maximo Application Suite SAML integration; not a hosted-service entitlement or blanket protocol limitation · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

IBM Cloud MAS deployable architecture; version-match the module, suite, database and OpenShift cluster · Source ↗ · Deployment artifact ↗ (24ddaef186771dc4996645c45de84d7ea500933d (configuration commit cited by the planning guide; verify suite compatibility)) · Planning and entitlement prerequisites ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

MAS Core versus Core + Manage on customer OpenShift; selected application and database sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

IBM Maximo Application Suite (BYOL); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

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

Category fit

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

Compare within ERP & CRM

  • Acumatica Private Cloud ERPCustomer-operated ERP with contract billing, renewals and business records.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Apache OFBizApache enterprise resource planning and commerce application framework.
    • AWS
    Customer-operated · Open Source / Open Core
  • Atomic CRMCustomer-operated CRM for contacts, companies, deals and communication history.
    • Azure
    Customer-operated · Open Source / Open Core
  • AureusERPCustomer-operated ERP for business, inventory, purchasing and financial records.
    • Azure
    • Hostinger
    Customer-operated · Open Source / Open Core
  • BigcapitalSelf-hosted accounting, invoicing and financial reporting application.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • CelerpSource-available customer-operated business, inventory and ERP application.
    • DigitalOcean
    Customer-operated · Source Available
  • Creatio Customer-ManagedCustomer-managed business application platform with sales, orders and contract records.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • ERPNext Supplier ManagementSelf-hosted supplier records, procurement documents, quotation attachments and supplier scorecards.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 22 other listings in ERP & CRM. These products address related workflows; read their category-fit notes before comparing scope. See all of ERP & CRM →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • IBM Cloud Docs ↗ · IBM Cloud

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory