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

IBM DataPower Gateway vs SwaggerHub comparison

Why PeerSpot?
 

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

IBM DataPower Gateway
Ranking in API Management
16th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (8th), Application Infrastructure (13th), SOA Application Gateways (1st)
SwaggerHub
Ranking in API Management
9th
Average Rating
7.8
Reviews Sentiment
6.4
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the API Management category, the mindshare of IBM DataPower Gateway is 4.0%, up from 3.5% compared to the previous year. The mindshare of SwaggerHub is 2.0%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
SwaggerHub2.0%
IBM DataPower Gateway4.0%
Other94.0%
API Management
 

Featured Reviews

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.
Coralia Popa - PeerSpot reviewer
Software Architect at Waters Corporation
Centralized API documentation has supported versioned collaboration across our teams
We have tried automated code generation several times, and I think maybe some people are still using it somewhere, but it is not something that we do as a consolidated practice. At some point, we were missing some tagging of the APIs, and we could not do that. We asked the provider, but I do not believe they added that kind of support. However, we somehow gave up a bit because we are now in the process of moving to different platforms ourselves, so most likely we are not going to invest in improving this integration with SwaggerHub or how we are using it. We will just keep it going for the platform we are leaving, and then because our focus is in a different place, we are not looking to change or do other things. I am not using SwaggerHub's OpenAI management feature. We are not looking much at what they added new. We got some notification that they added things, but we have so many other things to do.

Quotes from Members

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

Pros

"We did not experience any downtime, even if the number of transactions increased heavily."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"The solution is robust, and we use the appliance version, which comes with good security features and troubleshooting tools, so we are happy with IBM DataPower."
"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."
"The solution is stable."
"I like that it is very stable, and we never experience any downtime."
"The performance is good, it's been very stable, and the product is easy to integrate."
"The product is stable...The product is scalable."
"Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI, which allows us to perform detailed end-to-end automation testing."
"SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."
"It is a stable solution."
"The best feature that SwaggerHub offers is the collaboration capability that helps us the most across all of our teams, as we have a single API infrastructure but several teams working in different areas of these APIs."
"SwaggerHub has significantly improved how my organization designs, documents, and manages APIs, centralizing API management so that all API definitions are stored in one location, which makes it easy for stakeholders, developers, QA, DevOps, and products to access the latest version."
"SwaggerHub is helping with team collaboration, as all the people now know the link, they just go there and get the information they need, and it is really a documentation tool for sharing documentation information about the API we support."
 

Cons

"The DCDR process should be less complex."
"In terms of OEM support, it is poor. If I raise a CBRT one, as per the SLA, they should respond in one hour, however, sometimes it takes four or five hours to respond."
"I would like the tool to improve its training."
"They should add features to manage API integrations."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product."
"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 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."
"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."
"SwaggerHub's UI needs to be improved as it looks very old school."
"The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability."
"It could be more intuitive compared to one of its competitors."
"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that."
"We have to use additional tools to test APIs."
"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account."
 

Pricing and Cost Advice

"It is an expensive solution."
"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."
"The solution is expensive in comparison to other products."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The licensing cost is very expensive."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"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."
"It's expensive when you compare it with others."
"It has a yearly subscription, but I am not sure."
"The tool is cheap."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
920,929 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Outsourcing Company
9%
Manufacturing Company
8%
Government
6%
Financial Services Firm
12%
Outsourcing Company
11%
Manufacturing Company
11%
Comms Service Provider
8%
 

Company Size

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

Questions from the Community

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.
What needs improvement with SwaggerHub?
SwaggerHub can be improved since the API testing features are limited compared to Postman, and it is somewhat expensive for small teams as paid plans cost a lot.
What is your primary use case for SwaggerHub?
My main use case for SwaggerHub is to design and review API specifications, as I test endpoints with the help of Swagger UI, validate the request and the response schemas, and share the API documen...
What advice do you have for others considering SwaggerHub?
Before using SwaggerHub, I advise having basic API knowledge, as those with API knowledge can easily use SwaggerHub. I would rate this review an eight out of ten.
 

Also Known As

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

Overview

 

Sample Customers

RBL Bank, Availity
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about IBM DataPower Gateway vs. SwaggerHub and other solutions. Updated: September 2026.
920,929 professionals have used our research since 2012.