G2

Kim M.

Integration Consultant

Small-Business (50 or fewer emp.)

7/15/2026

"Unified, Cloud-Native Integration Platform on OpenShift That Simplifies Architecture"

5/5

What do you like best about IBM Cloud Pak for Integration?

It provides a complete integration platform rather than a collection of standalone products. Having API Connect, App Connect, IBM MQ, Event Streams, DataPower, Aspera, and shared platform services running on the same OpenShift foundation simplifies the architecture and creates a consistent operational model.

I also appreciate the cloud-native approach. Everything is deployed as Kubernetes operators, making it easier to automate installations, upgrades, and configuration using GitOps and CI/CD pipelines. Once the platform is established, new environments can be deployed in a repeatable and consistent manner.

Another strength is the integration between the products. APIs exposed through API Connect can easily integrate with App Connect flows, IBM MQ messaging, Kafka events, and DataPower security policies, all within the same ecosystem. This significantly reduces integration effort compared to stitching together multiple vendors' products.

One of the major advantages of IBM Cloud Pak for Integration is its flexible licensing model. A Cloud Pak for Integration (CP4I) license is not tied to a single product. Instead, the available Virtual Processor Core (VPC) entitlement can be allocated to any of the supported components, such as IBM API Connect, App Connect, IBM MQ, Event Streams, DataPower Gateway, Aspera, or other eligible capabilities. Review collected by and hosted on G2.com.

What do you dislike about IBM Cloud Pak for Integration?

Cloud Pak for Integration is designed for enterprise-scale environments, and that comes with complexity. Installing and operating the platform requires solid knowledge of Red Hat OpenShift, Kubernetes, storage, networking, certificates, and the individual integration capabilities.

The platform is also resource-intensive. For development or proof-of-concept environments, the infrastructure requirements can be significant, although this is understandable given the number of enterprise services that are included.

While IBM's documentation is comprehensive, it can sometimes be difficult to find practical end-to-end deployment examples, especially for GitOps, automation, disaster recovery, and upgrade scenarios. More production-focused examples would help organizations adopt the platform more quickly. Review collected by and hosted on G2.com.

What problems is IBM Cloud Pak for Integration solving and how is that benefiting you?

Cloud Pak for Integration enables us to standardize enterprise integration on a single platform. Instead of managing separate products with different deployment models and operational processes, we have one consistent platform for API management, application integration, messaging, event streaming, security, and file transfer. Review collected by and hosted on G2.com.