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

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

IBM DataPower Gateway
Ranking in API Management
11th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
31
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (7th), SOA Application Gateways (1st)
SwaggerHub
Ranking in API Management
14th
Average Rating
7.8
Reviews Sentiment
6.1
Number of Reviews
12
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2025, in the API Management category, the mindshare of IBM DataPower Gateway is 3.2%, down from 3.7% compared to the previous year. The mindshare of SwaggerHub is 1.5%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway3.2%
SwaggerHub1.5%
Other95.3%
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.
Manish Indupuri - PeerSpot reviewer
senior DevOps engineer at a tech services company with 10,001+ employees
Has streamlined API documentation and integration workflows across cross-functional teams
Documenting SwaggerHub has a standard and consistent structure of API definitions, and it automatically generates interactive documentation which helps the developers to understand everything. There are certain areas where SwaggerHub can go beyond here as formatting options for documentation pages are restricted, and the import and export options of API collections are complex in SwaggerHub. It provides various collaboration tools where we can work and do it. The strong validation against the API maintains conformity and reduces errors. That part is very great in SwaggerHub. Overall, scalability and stability-wise, it varies high compared to the competitors, but there are still certain areas where competitors are providing various customizations. SwaggerHub can understand those aspects and implement them as well. The complex import and export of API calls and collaborations can be challenging in SwaggerHub. If they can make it easier for us, that would be great. Their performance is degraded if there is too much load on the API. The customization and doc formatting options for documentation pages are restricted in SwaggerHub. A few of my teammates have complained that they find the UI unintuitive where it requires multiple clicks for simple tasks. SwaggerHub is a great tool, but these limitations can be addressed to make things better and easier.

Quotes from Members

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

Pros

"Support for PCA and non-PCA services is valuable."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"I like the API Gateway feature."
"I like that it is very stable, and we never experience any downtime."
"Its initial setup was straightforward."
"The scalability of the solution is good."
"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 very easy to work with."
"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."
"The tool's most valuable feature is licensing."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"It is a stable solution."
"It is quite a useful tool. It is quite good with the validation of the spec. It works quite well in terms of errors and conformity to the OpenAPI standard. It is better than Visual Studio Code in terms of editing."
"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."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
 

Cons

"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"My experience with the pricing of this product is that pricing is too high and should be reduced."
"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."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"The programming language is only supported in XSLT and Gateway script."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing. A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated. In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine."
"SwaggerHub could be improved with better integration for tools."
"More integration and usability with the cloud microservices would be nice"
"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."
"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."
"It could be more intuitive compared to one of its competitors."
"We have to use additional tools to test APIs."
"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

"The tool's initial costing is expensive for small banks and financial institutions."
"The product is expensive."
"The cost of this product varies from customer to customer and the relationship with IBM, including how many offerings from IBM are already being used."
"The licensing cost is very expensive."
"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 cost is very high and requires all five components in the API management solution."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"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.
879,310 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
9%
Manufacturing Company
8%
Computer Software Company
8%
Financial Services Firm
16%
Computer Software Company
11%
Manufacturing Company
8%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise17
By reviewers
Company SizeCount
Small Business3
Large Enterprise8
 

Questions from the Community

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?
This product is definitely expensive because if any issue occurs in the live environment or production environment, and our organization faces some issue with the IBM DataPower Gateway, then the IB...
What needs improvement with IBM DataPower Gateway?
The developer portal should be an integrated part of IBM DataPower Gateway to improve it. I think it is fine as is, and maybe no other additional features should be included in the next release. My...
What needs improvement with SwaggerHub?
In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited. I would love to see enhanced permissions allowing...
What is your primary use case for SwaggerHub?
I have worked for Arden University, University of Sheffield, and Nanyang Technological University. For those institutions, I used Amazon AppStream for backend validations. When working for Prolific...
What advice do you have for others considering SwaggerHub?
Based on my limited experience with SwaggerHub, I can share a few practical recommendations for implementing it effectively. Before onboarding multiple teams, it's important to define naming conven...
 

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: December 2025.
879,310 professionals have used our research since 2012.