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

IBM DataPower Gateway vs WSO2 Enterprise Integrator comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 3, 2025

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 Enterprise Service Bus (ESB)
8th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Application Infrastructure (13th), SOA Application Gateways (1st), API Management (16th)
WSO2 Enterprise Integrator
Ranking in Enterprise Service Bus (ESB)
6th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
20
Ranking in other categories
Data Integration (31st)
 

Mindshare comparison

As of November 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 4.9%, down from 6.4% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 4.9%, down from 5.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
WSO2 Enterprise Integrator4.9%
IBM DataPower Gateway4.9%
Other90.2%
Enterprise Service Bus (ESB)
 

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.
AC
Technical director at Cremete
Effective data transformation and integration in complex environments with high functionality
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your hand on this environment is a very demanding task. This is the real problem. The problem is not about the product, but about the complexity to manage, to configure, to decide what to do. I have some experience using SAP R/3. It seems to me something similar. When you have to configure a situation with a client, especially for a client not in an industrial sector, but in a service sector, it is quite usual that you are in trouble for some reason. This is always the story that I found in the implementations I have done. Maybe there are only three or four big problems, in some other cases there are more than that, but this is the situation usually. For WSO2 Enterprise Integrator, not the same, but I must say it is quite often there is a need to put together some pieces and make it work in a coordinated way.

Quotes from Members

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

Pros

"The support for IBM DataPower Gateway has been exceptional."
"I like that it is very stable, and we never experience any downtime."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
"If you have an API application in your organization that you want to make safe and secure, in addition to your existing WAF or load balancer, this product comes with all those capabilities:"
"It's high-speed and it can be remotely administered via an API."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"It is a scalable solution."
"The whole purpose of this product is to provide high speed and high performance."
"From the capabilities and functional possibility and anything else technical, it is a very well-done product, I have to say."
"The drag-and-drop features for connectors are very valuable."
"The most valuable aspect of the solution is the integration between core banking and other systems."
"The solution's customer service is good."
"The solution has two main parts: integration and transformation. It's very user-friendly and easy to understand for everyone."
"The productivity is the most valuable feature. It is very easy to write remediations."
"The installation process is easy."
"The solution basically conforms to our standards."
 

Cons

"In the next release, I would like to see the product price reduced. It should be cheaper."
"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."
"They should add features to manage API integrations."
"Additional documentation needs to be provided for complex automations."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need."
"The DCDR process should be less complex."
"The customization of the solution isn't as straightforward as we would like it to be."
"The main issue with the product is pricing. It uses core-based pricing for WSO2 Enterprise Integrator and API Manager. It would be best if you had APIM by default. It provides many connectors for easy integration with third-party systems."
"They should introduce better pricing for small companies."
"We had some challenges with the installation of this solution."
"For simpler tasks or simpler use cases, we avoid using WSO2 Enterprise Integrator because it is quite complex."
"If I have to buy software, then it becomes expensive for me."
"The micro integrator should be improved. There is room for enhancement considering alternative integration components."
"You cannot include the validation of XPath."
"The server is very specific and it is very difficult to get experience with it."
 

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 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 solution has a return on investment but is a little expensive."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The tool's initial costing is expensive for small banks and financial institutions."
"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 solution costs about 20,000 or 30,000 euros per year, per instance."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"The open-source, unsupported version is available free of charge."
"It is a low-cost solution."
"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."
"The cost is better than IBM Cloud Pak."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
921,523 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%
Outsourcing Company
14%
Financial Services Firm
8%
Construction Company
8%
Comms Service Provider
7%
 

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 Business8
Midsize Enterprise2
Large Enterprise11
 

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 WSO2 Enterprise Integrator?
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your ...
What is your primary use case for WSO2 Enterprise Integrator?
A typical use case for WSO2 Enterprise Integrator is when I am in an interoperability environment with healthcare facilities and I have to put together a lot of applications that share some HL7 mes...
What advice do you have for others considering WSO2 Enterprise Integrator?
For simpler tasks or simpler use cases, we avoid using WSO2 Enterprise Integrator because it is quite complex. So it is easier to manage some more simple solutions than that. WSO2 Enterprise Integr...
 

Also Known As

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

Overview

 

Sample Customers

RBL Bank, Availity
West
Find out what your peers are saying about IBM DataPower Gateway vs. WSO2 Enterprise Integrator and other solutions. Updated: November 2026.
921,523 professionals have used our research since 2012.