Try our new research platform with insights from 80,000+ expert users

IBM Cloud Pak for Integration vs IBM DataPower Gateway comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Cloud Pak for Integration
Ranking in API Management
28th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (16th)
IBM DataPower Gateway
Ranking in API Management
11th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
31
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (7th), SOA Application Gateways (1st)
 

Mindshare comparison

As of January 2026, in the API Management category, the mindshare of IBM Cloud Pak for Integration is 0.8%, up from 0.4% compared to the previous year. The mindshare of IBM DataPower Gateway is 3.1%, down from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway3.1%
IBM Cloud Pak for Integration0.8%
Other96.1%
API Management
 

Featured Reviews

Igor Khalitov - PeerSpot reviewer
Owner/Full Stack Software Engineer at Maraphonic, Inc.
Manages APIs and integrates microservices with redirection feature
IBM Cloud Pak for Integration includes monitoring capabilities to track the performance and health of your integrations. You can quickly roll back to a previous version if an issue arises. Additionally, it supports incremental deployments, allowing you to shift traffic to a new version of an API gradually. For example, you can start by directing 10% of traffic to the new version while the rest continue using the legacy version. If everything works as expected, you can gradually increase the traffic to the new version over time. IBM Cloud Pak for Integration has a client base that includes numerous organizations using AI and machine learning technologies. We leverage an open-source machine learning framework and integrate it with Kafka to help create and manage various products and data retrieval processes. For companies with private data, the framework first retrieves relevant data from a GitHub database, which is then combined with the final request before being sent to a language model like GPT. This ensures that the language model uses your specific data to generate responses. Kafka plays a key role by streaming real-time data from file systems and databases like Oracle and Microsoft SQL. This data is published to Kafka topics, then vectorized and used with artificial intelligence to enhance the overall process. It's like an old-fashioned approach. The best way is to redesign it with products such as Kafka. Overall, I rate the solution an eight out of ten.
AkshaySawant - PeerSpot reviewer
Manager at CSB Bank Ltd
Security features excel but development limitations emerge
We are using the IBM DataPower Gateway for security purposes. As per the development perspective, there are some limitations with IBM DataPower Gateway because it only supports XML and XSLT language, but it does not support the Java language. This is the only limitation of the IBM DataPower Gateway. For the authentication and authorization purpose, we can use the IBM DataPower Gateway. It's a very good product. We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes. If we are handling the load for a particular server, then we can use the IBM DataPower Gateway. The IBM DataPower Gateway is mostly used for security purposes. If we have some APIs and we are using some security for those APIs, then we can use it. It can also be used as a load balancer. It's also used for certificate management, user management purposes, authentication, and authorization. For routing, the IBM DataPower Gateway has multiple URL-based routing and content-based routing capabilities. If we have multiple URLs, then we can use an XML script. Using the XSLT language, we can configure multiple URLs and implement URL-based routing. Content-based routing means if we have multiple requests, we can route the request to a particular URL. For this, we need to use the XSLT language only. We can't use XML, Java, or other scripting languages. With IBM DataPower Gateway, we are using all the APIs. All APIs have been configured on the gateway. We have configured the particular TLS profile and some TLS client profiles as well. Using that TLS profile, we have configured the APIs and authentication. We have configured some tokens also, including JWT tokens and different types of auth tokens. There is also a rate limiting feature which we use for handling API loads.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."
"It is a stable solution."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"The product is stable...The product is scalable."
"The performance is good. It's been very stable."
"It's high-speed and it can be remotely administered via an API."
"The solution is stable."
"I like the API Gateway feature."
"I like the API Gateway feature."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
 

Cons

"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."
"The pricing can be improved."
"Enterprise bots are needed to balance products like Kafka and Confluent."
"The initial setup is not easy."
"Its queuing and messaging features need improvement."
"They should improve the solution's clustering features."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"DataPower isn't the most user-friendly tool. It is not an easy tool to use. Some things could use better wizards to guide you through processes."
"The programming language is only supported in XSLT and Gateway script."
"In terms of OEM support, it is poor. If I raise a CBRT one, as per the SLA, they should respond in one hour, however, sometimes it takes four or five hours to respond."
"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing. A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated. In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine."
 

Pricing and Cost Advice

"It is an expensive solution."
"The solution's pricing model is very flexible."
"The solution has a return on investment but is a little expensive."
"The cost is very high and requires all five components in the API management solution."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"The solution is expensive in comparison to other products."
"It's expensive when you compare it with others."
"The licensing cost is very expensive."
"IBM DataPower Gateway is quite expensive to get resources to work on this product. If the price could be cheaper, I think that will make it a little bit better and easily accessible to smaller clients. Then it could compete with other solutions that are available in the market. There's a whole lot of other solutions available that work well and are cheaper than IBM's products."
"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Government
13%
Insurance Company
8%
Computer Software Company
8%
Financial Services Firm
29%
Insurance Company
9%
Manufacturing Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise17
 

Questions from the Community

What needs improvement with IBM Cloud Pak for Integration?
Enterprise bots are needed to balance products like Kafka and Confluent.
What is your primary use case for IBM Cloud Pak for Integration?
It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousa...
What advice do you have for others considering IBM Cloud Pak for Integration?
IBM Cloud Pak for Integration includes monitoring capabilities to track the performance and health of your integrations. You can quickly roll back to a previous version if an issue arises. Addition...
What do you like most about IBM DataPower Gateway?
The MPGW (Multi-Protocol Gateway) is great because it allows you to easily expose services using various protocols – web services, REST (JSON), and others. This flexibility simplifies things.
What is your experience regarding pricing and costs for IBM DataPower Gateway?
This product is definitely expensive because if any issue occurs in the live environment or production environment, and our organization faces some issue with the IBM DataPower Gateway, then the IB...
What needs improvement with IBM DataPower Gateway?
The developer portal should be an integrated part of IBM DataPower Gateway to improve it. I think it is fine as is, and maybe no other additional features should be included in the next release. My...
 

Also Known As

No data available
WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
 

Overview

 

Sample Customers

CVS Health Corporation
RBL Bank, Availity
Find out what your peers are saying about IBM Cloud Pak for Integration vs. IBM DataPower Gateway and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.