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

IBM DataPower Gateway vs WSO2 Enterprise Integrator comparison

 

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)
5th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
31
Ranking in other categories
Application Infrastructure (7th), SOA Application Gateways (1st), API Management (11th)
WSO2 Enterprise Integrator
Ranking in Enterprise Service Bus (ESB)
7th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
20
Ranking in other categories
Data Integration (32nd)
 

Mindshare comparison

As of January 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 5.9%, up from 5.6% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.9%, up from 4.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway5.9%
WSO2 Enterprise Integrator5.9%
Other88.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

"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"What I like most is the stability."
"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."
"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:"
"Since it is a gateway, it provides a lot of security features."
"The solution is stable."
"I like the API Gateway feature."
"WSO2's analytics capability is good, considering the ELC support they provide."
"The solution basically conforms to our standards."
"It's a consolidated product. It works and it does its job pretty well."
"It's a very complete product. It allows us to network security and add more layers of security to the system."
"From the capabilities and functional possibility and anything else technical, it is a very well-done product, I have to say."
"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The installation process is easy."
"The solution's technical support is very knowledgeable."
 

Cons

"For the workloads that are not too high, appliance is a little bit expensive."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"It is a costly product."
"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."
"My experience with the pricing of this product is that pricing is too high and should be reduced."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"Its support services could be better."
"The customization can be a bit difficult."
"You cannot include the validation of XPath."
"The setup can be difficult for those not familiar with the solution."
"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."
"The integration capabilities need to be improved."
"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."
"The server is very specific and it is very difficult to get experience with it."
 

Pricing and Cost Advice

"The appliance is a bit on the expensive side for the workloads that are not too high."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The cost is very high and requires all five components in the API management solution."
"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."
"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 licensing cost is very expensive."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too 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."
"It is a low-cost solution."
"The open-source, unsupported version is available free of charge."
"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 pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
"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.
881,082 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
7%
Financial Services Firm
11%
Computer Software Company
8%
Comms Service Provider
7%
Insurance Company
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 Business8
Midsize Enterprise2
Large Enterprise11
 

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 do you like most about WSO2 Enterprise Integrator?
WSO2's analytics capability is good, considering the ELC support they provide.
What is your experience regarding pricing and costs for WSO2 Enterprise Integrator?
The product has reasonable and competitive pricing for enterprise customers. It is expensive for small businesses especially. They are using the open-source solution, and they find it expensive sin...
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 ...
 

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