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

IBM API Connect vs IBM Cloud Pak for Integration 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 API Connect
Ranking in API Management
5th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
Integration Platform as a Service (iPaaS) (7th)
IBM Cloud Pak for Integration
Ranking in API Management
24th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (15th)
 

Mindshare comparison

As of April 2025, in the API Management category, the mindshare of IBM API Connect is 6.4%, up from 6.2% compared to the previous year. The mindshare of IBM Cloud Pak for Integration is 0.4%, down from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

KavitaChavan - PeerSpot reviewer
Quite flexible and provides excellent performance for API gateway
The only disadvantage I can see is that it requires heavy hardware support, which can be considered quite expensive. In terms of new functionality, I think the analytics can be improved in V10. The analytics feature was better in the older version, 2.18. But in V10, it's not as flexible. When exporting analytics as KSP or JSON, it's not well formatted. They can work on enhancing the analytics part. Additionally, they can focus on reducing the hardware cost.
Neelima Golla - PeerSpot reviewer
A hybrid integration platform that applies the functionality of closed-loop AI automation
I recommend using it because, in today's context, the cloud plays a significant role. Within the same user interface, you can develop applications and manage multiple applications, making it a more user-friendly option. Moreover, you can explore various other technologies while deploying on the cloud, broadening your knowledge of cloud technologies. In my case, the transition led to my learning of Kubernetes, enabling multi-scaling and expanding my technical skills. It was a valuable experience, and I had the opportunity to learn many new things during the migration process. I can easily rate it an eight or nine out of ten.

Quotes from Members

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

Pros

"One of the most valuable features of this solution is that it protects our backend system. We are exposing services to external parties and using this solution to protect the backend system, and to have a navigation in between."
"Since it runs on top of Datapower, all Datapower based custom policies can be utilized and exported to API connect but its not straightforward/simple process."
"Security is well organized and managed within the solution."
"I have found the API Management to be most valuable."
"The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster."
"It has all of the tools that are needed for the specific mission."
"It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems. It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions."
"One of the most valuable features is that we can seamlessly and harmoniously expose our capabilities, from a security point of view."
"It is a stable solution."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"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."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
 

Cons

"The product's setup phase and its setup for the users in different environments, along with DevOps integration, are areas of concern where there is a need for improvement."
"The only disadvantage I can see is that it requires heavy hardware support."
"While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome."
"It is expensive within this class of products."
"The installation process could use improvement. I hope that in the next release, the installation process is easier."
"Debugging could be improved."
"We've had some issues upgrading to the latest version of the solution."
"I would like to see automation of the installation. If there could be a single-click function where you could automate everything, that would be helpful."
"Its queuing and messaging features need improvement."
"The pricing can be improved."
"Enterprise bots are needed to balance products like Kafka and Confluent."
"The initial setup is not easy."
"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."
 

Pricing and Cost Advice

"API Connect is quite pricey."
"It's an expensive product."
"The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight."
"This is a licensed product. If your company is looking to obtain a license, you have to work with IBM partners."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"API Connect was highly expensive for us, but the decision to switch was made before I joined the company. It seems like the company bought it, but they didn't know how to use it. After two years, they decided to reevaluate and conduct some cost estimates."
"Pricing for IBM API Connect varies, e.g. it could be subscription-based. Deploying it on private cloud also means you have to own most of the software licensing."
"There was a need to purchase an upfront license or a one-time license or upfront license, but I cannot remember the details about it clearly."
"It is an expensive solution."
"The solution's pricing model is very flexible."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
23%
Financial Services Firm
17%
Insurance Company
10%
Computer Software Company
9%
Financial Services Firm
20%
Computer Software Company
12%
Government
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about IBM API Connect?
Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules.
What is your experience regarding pricing and costs for IBM API Connect?
Price depends on many factors like size of the deal, competitive factors, timing, customer profile or where the pricing for API Calls is very competitive comparing to any of the leader players.
What needs improvement with IBM API Connect?
The only downside where improvements are needed is probably on the licensing side. Scalability is an issue with IBM API Connect, making it an area where improvements are required.
What do you like most about IBM Cloud Pak for Integration?
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 ...
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...
 

Overview

 

Sample Customers

Heineken, Tine, Finologee, Axis Bank
CVS Health Corporation
Find out what your peers are saying about IBM API Connect vs. IBM Cloud Pak for Integration and other solutions. Updated: April 2025.
849,686 professionals have used our research since 2012.