We performed a comparison between IBM API Connect and IBM Cloud Pak for Integration based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The support is good and active. I rate the technical support a nine out of ten."
"IBM API Connect is a good product, and their technical support is excellent."
"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."
"We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable."
"WSRR is a powerful component for getting the endpoints."
"The most valuable feature of IBM API Connect is the security of the protocol."
"It has all of the tools that are needed for the specific mission."
"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 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."
"It is a stable solution."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"We've had some issues upgrading to the latest version of the solution."
"Automation for our Domino applications could be improved."
"It's based on a little bit dated architecture. A lot of evolution has happened after that. It's an evolving field. Kong is a Kubernetes-based platform. Kong runs on Kubernetes, but all the other ones are in microservices. So, there's a lot of improvement that can be done."
"Extracting the data could be improved."
"In terms of what needs improvement, some of the product documentation could be better."
"The only disadvantage I can see is that it requires heavy hardware support."
"The solution is not scalable."
"The new version is very unstable."
"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 pricing can be improved."
"The initial setup is not easy."
More IBM Cloud Pak for Integration Pricing and Cost Advice →
IBM API Connect is ranked 5th in API Management with 73 reviews while IBM Cloud Pak for Integration is ranked 21st in API Management with 4 reviews. IBM API Connect is rated 8.0, while IBM Cloud Pak for Integration is rated 8.6. The top reviewer of IBM API Connect writes "Good speed and performance, but it's based on a bit dated architecture". On the other hand, the top reviewer of IBM Cloud Pak for Integration writes "A hybrid integration platform that applies the functionality of closed-loop AI automation". IBM API Connect is most compared with IBM DataPower Gateway, Apigee, Microsoft Azure API Management, MuleSoft Anypoint API Manager and WSO2 API Manager, whereas IBM Cloud Pak for Integration is most compared with IBM App Connect, IBM DataPower Gateway, MuleSoft Anypoint API Manager, Microsoft Azure API Management and AWS Glue. See our IBM API Connect vs. IBM Cloud Pak for Integration report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.