No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Cloud Pak for Integration vs Kong Konnect comparison

 

Comparison Buyer's Guide

Executive Summary

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
29th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (20th)
Kong Konnect
Ranking in API Management
13th
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
9
Ranking in other categories
AI Observability (16th)
 

Mindshare comparison

As of August 2026, in the API Management category, the mindshare of IBM Cloud Pak for Integration is 1.0%, up from 0.5% compared to the previous year. The mindshare of Kong Konnect is 1.1%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Kong Konnect1.1%
IBM Cloud Pak for Integration1.0%
Other97.9%
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.
AK
CTO at Keogh Innovation
Centralizes API and AI control planes and has enabled federated self-service for many teams
The whole area of API and AI management is quite complex, with so many different ways of being able to do things. I think a positive of Kong is that it's so configurable and extendable, but that is also a con because there are so many ways of achieving the same thing that I think often people are either confused or struggle to get going as to how to solve a particular problem. In my mind, a more opinionated deployment of Kong itself or even how to solve certain use cases would be something I would like to see, so a more opinionated use of their products and configuration of their products on how to solve the most common use cases. That's probably the main thing about needed improvements for Kong Konnect. It's a pretty fully-fledged platform; there obviously are portions of it that could be improved. But I think overall as a platform, it's really good, and I think it can help the majority of organizations looking to manage their throughput of APIs or AI traffic. The majority of what I've said before probably covers the improvements needed for Kong Konnect. There probably are some API Ops and AI Ops changes that could be improved, which is not necessarily the Kong Konnect product, but some of the toolchains around it. I'm thinking around, especially if it's API Ops, about topics like better GitOps processes and the ways of being able to roll back changes when there are issues. At the moment, a lot of that is either non-existent or is hand-cranked. I would like to see the ability to roll back configurations when there are issues being added to the product.

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."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"In general, the solution works very, very well."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"It is a stable solution."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"My advice for others looking into using Kong Konnect is to please go with it, as it is very good compared to other tools in the market, low cost, has a user-friendly interface, is easy to set up, and customer support is also very good."
"I think it's a really great tool, and I've seen a number of enterprise companies using it."
"Technical support from Proofpoint was absolutely excellent."
"Kong Konnect has impacted my organization positively, particularly in enhancing security and providing a compliance dashboard for applications, making it a very positive impact on my organization."
"Kong Konnect has positively impacted my organization by making our development easier and helping us push new routes to our current customers."
"Their tech support is excellent; when I raise an incident or a support ticket, it gets answered in four hours."
"The documentation is excellent, and it includes a developer portal, which helps create a common distribution channel for APIs within and outside the enterprise."
"Since using Kong Konnect, I have observed less time in onboarding external partners for our internal APIs, less time in exposing our APIs with proper authentication and rate limiting, and more collaboration for discovering API specifications across platforms."
 

Cons

"Enterprise bots are needed to balance products like Kafka and Confluent."
"The pricing can be improved."
"Its queuing and messaging features need improvement."
"What needs to be improved is the restriction that they have on the product."
"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."
"Kong Konnect can be improved by simplifying pricing to make it more transparent, simplifying the user experience so that non-technical people can also configure API specifications, and by supporting more enterprise plugins and third-party integrations to make it more robust."
"Kong Konnect needs improvement in the UI."
"Pricing was the issue as it becomes very expensive due to the nature of local circumstances."
"I do not rate Kong Konnect a nine out of ten because the configuration can be complex and not beginner-friendly."
"I think a positive of Kong is that it's so configurable and extendable, but that is also a con because there are so many ways of achieving the same thing that I think often people are either confused or struggle to get going as to how to solve a particular problem."
"I would recommend that Kong add the capability to sort the routes by name, date, or size, as the current setup does not support this."
"Kong Konnect's RBAC needs to evolve more, as they currently offer only one or two levels of RBAC in terms of organization and teams."
"When comparing documentation, Kong's documentation is not on par with Google, Amazon, or other cloud providers."
 

Pricing and Cost Advice

"It is an expensive solution."
"The solution's pricing model is very flexible."
Information not available
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
12%
Construction Company
9%
Government
8%
Financial Services Firm
14%
Outsourcing Company
13%
Manufacturing Company
13%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise2
Large Enterprise3
 

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 is your experience regarding pricing and costs for Kong Konnect?
Regarding my experience with pricing, setup cost, and licensing, I find that the pricing can be made more transparent and more helpful for enterprise integration.
What needs improvement with Kong Konnect?
I would recommend that Kong add the capability to sort the routes by name, date, or size, as the current setup does not support this. I would suggest that Kong make the routes or services appear in...
What is your primary use case for Kong Konnect?
We use Kong Konnect primarily for centralized API management, API security, Kubernetes ingress management, traffic control, observability, and governance across multiple environments. Additionally,...
 

Overview

 

Sample Customers

CVS Health Corporation
Information Not Available
Find out what your peers are saying about IBM Cloud Pak for Integration vs. Kong Konnect and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.