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

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

Apiary
Ranking in API Management
36th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
4
Ranking in other categories
No ranking in other categories
IBM DataPower Gateway
Ranking in API Management
10th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (6th), SOA Application Gateways (1st)
 

Mindshare comparison

As of March 2026, in the API Management category, the mindshare of Apiary is 0.7%, up from 0.3% compared to the previous year. The mindshare of IBM DataPower Gateway is 3.1%, down from 3.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.1%
Apiary0.7%
Other96.2%
API Management
 

Featured Reviews

PW
Enterprise Integration Architect at Capgemini
The ability to configure rules to check for consistency has helped
Apiary provides a free tier of the platform which allows a small group of developers to collaborate easily on the design of open source APIs. In addition to this, it provides mock endpoints allowing people to experiment with the API without depending or having to stand up a real backend. With our clients, using Apiary allows us to very quickly pull together an API definition (particularly when using API Blueprint). The whole API design process for the simpler use cases can be done in a relatively short workshop which makes it a lot easier to agree, publish, version-manage an API definition with suitable documentation. This can then be evolved and enhanced (particularly in the documentation aspects). With the ability to support Swagger (Open API v2 and introducing/ed support for v3) and API Blueprint makes it a very versatile tool.
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

"Quick and easy way to share a new API design with teams."
"This solution has allowed us to standardize API definitions and bring consistency into our shared components, reducing the effort and cost of using functionality across domains within the organization, with Apiary being crucial to our good API strategy."
"Vey high - very easy API design with no setup effort"
"I find the generation of mock services very useful, especially when demonstrating for new consumers."
"Quick and easy way to share a new API design with teams."
"The feature I find most valuable is that it offers authentication and allows us to develop communication points."
"Git integration"
"I do like the overall performance of the solution."
"The scalability of the solution is good."
"For me, its most valuable features include: the fact that it's high-speed, its ability to be remotely administered via an API, the fact that it can deal with multiple protocols, and it's very quick to make changes to the setup."
"I like that it is very stable, and we never experience any downtime."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"What I like most is the stability."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
"I like the API Gateway feature."
 

Cons

"I would like an integrated option to download a Swagger version of the definition."
"I don't think this solution is very stable so we try to manage stability from our side."
"Better Swagger support."
"The Oracle release cycle is very bad because the patches only update once a year."
"Swagger (OpenAPI Specification) and Blueprint Support"
"I would like an integrated option to download a Swagger version of the definition."
"Validation messages could be a bit clearer."
"IBM DataPower Gateway is a great solution but when based on utilizations in the different streams others feel that this is an expensive product for one simple use case."
"API management launched two years back and we consider it quite unstable because we still face a lot of bugs."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"My experience with the pricing of this product is that pricing is too high and should be reduced."
"The programming language is only supported in XSLT and Gateway script."
"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."
"For the workloads that are not too high, appliance is a little bit expensive."
 

Pricing and Cost Advice

"There is a free subscription option to start and try the service."
"It is easy to get started with personal (free) accounts, but a subscription is required for additional features."
"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."
"IBM DataPower Gateway is quite expensive to get resources to work on this product. If the price could be cheaper, I think that will make it a little bit better and easily accessible to smaller clients. Then it could compete with other solutions that are available in the market. There's a whole lot of other solutions available that work well and are cheaper than IBM's products."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The product is expensive."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"It is an expensive solution."
"The solution has a return on investment but is a little expensive."
"The solution is expensive in comparison to other products."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
885,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
28%
Insurance Company
8%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about IBM DataPower Gateway?
The MPGW (Multi-Protocol Gateway) is great because it allows you to easily expose services using various protocols – web services, REST (JSON), and others. This flexibility simplifies things.
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.
 

Also Known As

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

Overview

 

Sample Customers

Microsoft, salesforce.com, Bloomberg, GoodData, Viacom, Akamai Technologies, DigitalGlobe
RBL Bank, Availity
Find out what your peers are saying about Apiary vs. IBM DataPower Gateway and other solutions. Updated: March 2026.
885,311 professionals have used our research since 2012.