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

Apollo GraphOS vs IBM DataPower Gateway 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

Apollo GraphOS
Ranking in API Management
20th
Average Rating
7.6
Reviews Sentiment
4.4
Number of Reviews
7
Ranking in other categories
No ranking in other categories
IBM DataPower Gateway
Ranking in API Management
13th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (6th), Application Infrastructure (13th), SOA Application Gateways (1st)
 

Mindshare comparison

As of October 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.8%, up from 0.4% compared to the previous year. The mindshare of IBM DataPower Gateway is 4.0%, up from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway4.0%
Apollo GraphOS0.8%
Other95.2%
API Management
 

Featured Reviews

MB
Business Development Manager at Digitaltrack
Unified schemas have streamlined team collaboration and have reduced API-related deployment issues
We had a positive experience with Apollo GraphOS, but there are a few areas where I think it could be improved. One area is the learning curve around GraphQL Federation and schema governance. Teams that are new to federated architectures often need to understand best practices. More guided onboarding, built-in recommendations, and practical examples would make adoption easier. I also think the observability and troubleshooting experience could be enhanced, particularly when diagnosing issues that span multiple subgraphs. While the platform provides useful insights, tracing complex requests across a federated environment can still require additional investigations. Another improvement would be more granular administrative controls and reporting, especially for larger organizations where different teams manage different parts of the GraphQL platform. Although the CI/CD integration is one of the product's strengths, having more out-of-the-box integrations and similar configurations for popular DevOps tools would reduce the initial setup effort. These suggestions would make the platform easier to adopt, operate, and scale, particularly for organizations that are beginning their GraphQL Federation journey. One thing I would like to see in future releases is deeper operational visibility for large-scale federated environments. As the number of subgraphs and development teams grows, it becomes more important to quickly identify where performance bottlenecks or schema-related issues are originating without having to correlate information from multiple tools. More built-in governance capabilities would be valuable, such as stronger policy enforcement, approval workflows for schema changes, and richer reporting for platform administrators. Another area that could be improved is the onboarding experience. While the documentation is comprehensive, having more guided setup wizards, architectures, and real-world implementation examples would help new teams become productive more quickly. I would also like to see even broader integrations with common enterprise monitoring, security, and development platforms so organizations can manage Apollo GraphOS as part of their existing operational ecosystem rather than relying on additional customization. These points would make day-to-day administration easier and improve the experience for organizations running GraphQL at a larger scale.
AkshaySawant - PeerSpot reviewer
Manager at CSB Bank Ltd
Security features excel but development limitations emerge
We are using the IBM DataPower Gateway for security purposes. As per the development perspective, there are some limitations with IBM DataPower Gateway because it only supports XML and XSLT language, but it does not support the Java language. This is the only limitation of the IBM DataPower Gateway. For the authentication and authorization purpose, we can use the IBM DataPower Gateway. It's a very good product. We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes. If we are handling the load for a particular server, then we can use the IBM DataPower Gateway. The IBM DataPower Gateway is mostly used for security purposes. If we have some APIs and we are using some security for those APIs, then we can use it. It can also be used as a load balancer. It's also used for certificate management, user management purposes, authentication, and authorization. For routing, the IBM DataPower Gateway has multiple URL-based routing and content-based routing capabilities. If we have multiple URLs, then we can use an XML script. Using the XSLT language, we can configure multiple URLs and implement URL-based routing. Content-based routing means if we have multiple requests, we can route the request to a particular URL. For this, we need to use the XSLT language only. We can't use XML, Java, or other scripting languages. With IBM DataPower Gateway, we are using all the APIs. All APIs have been configured on the gateway. We have configured the particular TLS profile and some TLS client profiles as well. Using that TLS profile, we have configured the APIs and authentication. We have configured some tokens also, including JWT tokens and different types of auth tokens. There is also a rate limiting feature which we use for handling API loads.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Overall, Apollo GraphOS has been a valuable asset."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"Apollo GraphOS has positively impacted our organization by reducing unwanted code and helping us combine multiple services."
"Apollo GraphOS positively impacts my organization by providing a complete platform for API orchestration, schema governance, observability, and federation."
"Apollo GraphOS has had a positive impact on our organization by making our API development process more structured, predictable, and collaborative."
"Apollo GraphOS has had a positive impact by improving the way we manage and evolve our GraphQL APIs."
"Apollo GraphOS has significantly enhanced both the developer experience and product delivery timelines by offering a centralized approach to managing GraphQL schemas and services, helping reduce overhead and improve collaboration between frontend and backend teams."
"It is a scalable solution."
"Since it is a gateway, it provides a lot of security features."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
"The API Connect gateway service and the SQL injection feature is good."
"What I like most is the stability."
"The whole purpose of this product is to provide high speed and high performance."
"If you are an enterprise customer, I would definitely advise that it is better to go for IBM DataPower, because you won't need to have a proxy or any other security measures required in the DMC, and it is easy to implement and easy to maintain and scale."
"I like the API Gateway feature."
 

Cons

"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"The reason I held back from giving it a perfect score is that some enterprise scenarios still require additional effort."
"I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, making the platform seem more complex than necessary for smaller teams."
"Apollo GraphOS could be improved with simpler pricing, more transparent usage and cost reporting, easier onboarding for new teams and learners, and more detailed documentation and troubleshooting guidance for complex GraphQL."
"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage. It sometimes takes longer than three seconds, which can affect loading times and lead to user dissatisfaction. I would like to see improved performance."
"I rated it six out of ten because while it offers useful capabilities such as schema management, schema validation, and API observability, I feel there are several areas that need improvement."
"For the workloads that are not too high, appliance is a little bit expensive, especially in the development test and UAT environment, where we can use the virtual version of the product."
"Small and medium-sized companies might look for cloud-hosted applications due to the cost."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"The components that they include in the product that are, in fact, a WTX, really need to be removed from the product because they tend to fail."
"The IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
 

Pricing and Cost Advice

Information not available
"The tool's initial costing is expensive for small banks and financial institutions."
"The licensing cost is very expensive."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The solution is expensive in comparison to other products."
"The total cost of IBM DataPower Gateway would depend on the configuration, but in my experience, it can amount to 60,000 Euros per box, even for the virtual version. Usually, customers need high availability and a non-production environment, so the total price for IBM DataPower Gateway can be quite a lot. It can be 200,000 Euros or a similar figure."
"The appliance is a bit on the expensive side for the workloads that are not too high."
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
Manufacturing Company
12%
University
10%
Program Development Consultancy
10%
Financial Services Firm
10%
Financial Services Firm
22%
Outsourcing Company
8%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise3
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
 

Questions from the Community

What is your experience regarding pricing and costs for Apollo GraphOS?
I am not sensitive to nor very knowledgeable about the pricing and setup cost.
What needs improvement with Apollo GraphOS?
I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, ma...
What is your primary use case for Apollo GraphOS?
My main use case for Apollo GraphOS is creating APIs with GraphQL. I create subgraphs and schema composition, contracts, schema registry, and change validation, which helps me prevent breaking chan...
What is your experience regarding pricing and costs for IBM DataPower Gateway?
I don't know if the current licensing cost of IBM DataPower Gateway is high, but I think it's acceptable. I don't have any complaints about it.
What needs improvement with IBM DataPower Gateway?
I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need.
What is your primary use case for IBM DataPower Gateway?
The primary purposes for which IBM DataPower Gateway is used include security purposes, and sometimes you need to put some configurations and mapping into the process.
 

Also Known As

No data available
WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
 

Overview

 

Sample Customers

Information Not Available
RBL Bank, Availity
Find out what your peers are saying about Apollo GraphOS vs. IBM DataPower Gateway and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.