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
8th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
Integration Platform as a Service (iPaaS) (9th)
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)
 

Mindshare comparison

As of October 2025, in the API Management category, the mindshare of IBM API Connect is 6.0%, down from 6.3% compared to the previous year. The mindshare of IBM Cloud Pak for Integration is 0.5%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM API Connect6.0%
IBM Cloud Pak for Integration0.5%
Other93.5%
API Management
 

Featured Reviews

Shanmugasundaram Shanmuganathan - PeerSpot reviewer
Offers basic API orchestration and provides robust security and governance features
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. Overall, I would rate the scalability an eight out of ten. Almost all applications we've been exposing lately go through this middleware, so it's used extensively. There are around sixty applications directly using it, but six Kubernetes clusters serve those applications. It's heavily used for integration, including system-to-system integration and product integrations. Our usage has been increasing year-on-year based on our needs.
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

"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."
"It has all of the tools that are needed for the specific mission."
"This solution is ready to scale and already supports our agile CICD."
"The management of the API and API portal is good."
"It allows enterprises to expose some of their tech to outside stakeholders."
"It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month."
"The developer portal has been the most useful feature."
"Its speed and performance are valuable."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"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."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"It is a stable solution."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
 

Cons

"We would have more capability to interact with the catalog and inventories, so a more DevOps-friendly solution is needed."
"The developmental process is not quite user-friendly."
"The solution could improve security and performance."
"Our main pain points are in these two areas: creating a better developer portal and improving stability in terms of synchronization and monetization."
"The only disadvantage I can see is that it requires heavy hardware support."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"It should be cheaper."
"The administration of the user interface and the technical documentation are areas of concern in the solution where improvements are required."
"The pricing can be improved."
"Its queuing and messaging features need improvement."
"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 initial setup is not easy."
"Enterprise bots are needed to balance products like Kafka and Confluent."
 

Pricing and Cost Advice

"API Connect is expensive - I'd rate their pricing five out of ten."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"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."
"API Connect is quite pricey."
"We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee."
"It is an expensive solution. The licensing model is based on a per-subscription and per-subscriber end-user basis, meaning the price is determined by the end-users of the platform."
"API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution."
"It can be quite expensive. It's okay for large-scale usage but quite expensive for smaller-scale implementations."
"The solution's pricing model is very flexible."
"It is an expensive solution."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
868,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Insurance Company
12%
Computer Software Company
11%
Manufacturing Company
7%
Financial Services Firm
18%
Government
10%
Insurance Company
8%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise10
Large Enterprise58
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?
Pricing depends on how many instances run across environments. I don't deal with licensing, but compared to other IBM products, the licensing is not significantly higher.
What needs improvement with IBM API Connect?
When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer. Examples include the lack of connectivity to MQ ( /categories/message-queue-mq...
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: September 2025.
868,706 professionals have used our research since 2012.