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

Apigee 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

Apigee
Ranking in API Management
2nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
86
Ranking in other categories
API Testing Tools (6th)
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 March 2025, in the API Management category, the mindshare of Apigee is 14.5%, down from 15.1% 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

ShawkyFoda  - PeerSpot reviewer
Provides high visibility and control with good traffic monitoring
Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability. The replication process between Master and Slave for disaster recovery takes too long. Dependencies on analytics impact the performance of the user interface, which should be separate. The complex setup process on-premises, especially with multi-node installations, could also be improved. Additional control in product declarations, based on operations like POST and GET, is needed.
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

"The usability is one of the best aspects of the product."
"The analytics feature is quite good."
"The most valuable feature of Apigee is its simplicity of deploying an API and restricting access, like rate limit, with the API."
"The ability to convert from language to language using a single tool."
"The security that you have with Apigee is very good and aligns with compliance."
"Apigee is the heart of the architectural design for building an integration layer in our digital transformation projects. Organizations need an integration layer to connect their legacy backend services with the external world, such as Fintechs. This layer must be secure, not just a simple pass-through or gateway."
"Apigee is relatively easy to use for developers."
"It nice and easy for the clients and those using the product to access the product's help resources."
"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."
"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."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
 

Cons

"Apigee is not a solution compatible with public clouds, making it one of its shortcomings where improvements are required."
"Apigee's user interface could be more straightforward and have more options. Also, it would be nice if it were ready to work out of the box without so much configuration."
"I would like to see SOAP services and socket-based connectivity developed."
"I would like them to add features, such as caching and mediation policies."
"The analytical aspect of it could be better. I think it is fair if Apigee lets you configure some of the metrics of the key details you want to monitor in terms of analytics."
"The entire user across all the layers should be singly authenticated through an external authentication system."
"Sometimes there are glitches, which means there's still room for improvement in the platform."
"Access restrictions can be improved."
"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."
"Its queuing and messaging features need improvement."
"The initial setup is not easy."
"Enterprise bots are needed to balance products like Kafka and Confluent."
 

Pricing and Cost Advice

"The product's pricing is fair. You need to pay additional costs for the support."
"Its price is reasonable for the features they provide and the maturity of the platform."
"I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited."
"Compared to other products, Apigee had higher pricing."
"It is more expensive when you compare to open-source products or other vendors."
"My clients pay for a license."
"The cost increases as the usage increases."
"It is an expensive solution."
"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.
841,004 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
12%
Manufacturing Company
7%
Insurance Company
7%
Financial Services Firm
18%
Computer Software Company
14%
Government
8%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Apigee or Amazon API Gateway?
Amazon API Gateway is a platform that supports the creation and publication of API for web applications. The platform can support thousands of simultaneous API calls, and it provides monitoring, ma...
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

Adobe, advance.net, Amadeus, AT&T, Bechtel, Belly, Burberry, Chegg, Citrix, Dell, eBay, Equifax, GameStop, First Data, Globe, HCSC, Intralinks, Kao, Meredith, Mitchell, Orange, Pearson
CVS Health Corporation
Find out what your peers are saying about Apigee vs. IBM Cloud Pak for Integration and other solutions. Updated: January 2025.
841,004 professionals have used our research since 2012.