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

Apache APISIX vs IBM Cloud Pak for Integration comparison

Why PeerSpot?
 

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

Apache APISIX
Ranking in API Management
21st
Average Rating
8.0
Reviews Sentiment
7.5
Number of Reviews
2
Ranking in other categories
No ranking in other categories
IBM Cloud Pak for Integration
Ranking in API Management
36th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (28th)
 

Mindshare comparison

As of October 2026, in the API Management category, the mindshare of Apache APISIX is 2.0%, down from 3.5% compared to the previous year. The mindshare of IBM Cloud Pak for Integration is 1.1%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apache APISIX2.0%
IBM Cloud Pak for Integration1.1%
Other96.9%
API Management
 

Featured Reviews

AS
Senior Java Software Developer at VOIS
Integration with backend systems and runtime configuration simplicity enhance operational efficiency
Apache APISIX is easy to configure. It supports coding for filters and can integrate with many languages. Its configuration at runtime is very easy. You can configure your gateway at runtime without needing to restart the gateway to apply configurations. This is a perfect feature. The service discovery feature integrates with backend systems and provides powerful load balancing. Also, its integration with Keycloak and authorization systems is a valuable feature.
Neelima Golla - PeerSpot reviewer
Senior Software Engineer at NessPRO Italy
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

"The most valuable features of Apache APISIX include routing for upstream and frontend services, masking using proxy rewrite, and the integration of different plugins like Prometheus and Grafana."
"I recommend Apache APISIX to others because of its many useful features."
"In general, the solution works very, very well."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"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."
"It is a stable solution."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
 

Cons

"The user interface is limited and does not support all features of Apache APISIX."
"The routing algorithms in Apache APISIX, such as node-based and round-robin, could be improved. Introducing more plugins and supporting AI features can enhance the solution."
"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."
"The pricing can be improved."
"What needs to be improved is the restriction that they have on the product."
"Its queuing and messaging features need improvement."
 

Pricing and Cost Advice

Information not available
"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.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Comms Service Provider
10%
Government
10%
Manufacturing Company
9%
Financial Services Firm
13%
Manufacturing Company
11%
Construction Company
9%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What needs improvement with Apache APISIX?
The routing algorithms in Apache APISIX, such as node-based and round-robin, could be improved. Introducing more plugins and supporting AI features can enhance the solution.
What is your primary use case for Apache APISIX?
The primary use case for Apache APISIX is to mask the API endpoints for my microservices and use self-given APIs in Apache APISIX and mask those with the actual real ones. This helps to prevent use...
What advice do you have for others considering Apache APISIX?
I rate Apache APISIX an eight out of ten overall. For new users, I advise going through the official documentation deeply to implement the solution efficiently.
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Information Not Available
CVS Health Corporation
Find out what your peers are saying about Apache APISIX vs. IBM Cloud Pak for Integration and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.