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 (10th)
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 November 2025, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 6.4%, up from 5.8% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.7%, up from 5.1% 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 Gateway6.4%
WSO2 Enterprise Integrator5.7%
Other87.9%
Enterprise Service Bus (ESB)
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
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.
Ritesh_Shah - PeerSpot reviewer
Decreases the development timeframe and costs
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. Often, customers decide to develop using open-source tools like Spring Boot if there aren't many connectors required to avoid increasing costs. They'll develop this way and then deploy using APIM, the bare minimum needed. It is mainly required for very complicated setups with many connectors. In the implementations I've seen, people often used open-source tools because there weren't many third-party systems involved—just their organization's own systems. From WSO2 Enterprise Integrator, I expect them to bring up more and more connectors in the future. That's the main expectation. Having more connectors in various areas will help us when discussing new requirements. I don't have any specific use case right now, so I can't name a particular connector. But, as new technologies emerge, the relevant connectors should be there for those. WSO2 Enterprise Integrator mainly helps with the integration part, which can be simplified only if you have relevant connectors for whatever you're doing.

Quotes from Members

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

Pros

"I like that it is very stable, and we never experience any downtime."
"The API Connect gateway service and the SQL injection feature is good."
"The most valuable feature is the security appliance, it's very secure."
"I like the API Gateway feature."
"I like the API Gateway feature."
"It is a scalable solution."
"The solution is straightforward and for large organizations, it functions well."
"The scalability of the solution is good."
"The drag-and-drop features for connectors are very valuable."
"It's a consolidated product. It works and it does its job pretty well."
"In my opinion, the most valuable aspect of this solution is its extensive range of adaptors and connectors. This feature holds significant importance and provides great value to users."
"The productivity is the most valuable feature. It is very easy to write remediations."
"The customer service executives are very responsive."
"The solution's customer service is good."
"It's a very complete product. It allows us to network security and add more layers of security to the system."
"The learning curve for this solution is very good."
 

Cons

"Scripting needs improvement. It's hard for our customers."
"They should add features to manage API integrations."
"The programming language is only supported in XSLT and Gateway script."
"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."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"DataPower isn't the most user-friendly tool. It is not an easy tool to use. Some things could use better wizards to guide you through processes."
"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."
"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."
"You cannot include the validation of XPath."
"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 administration side is complex and could use significant improvements to enhance the solution's functionality."
"They should introduce better pricing for small companies."
"One of the reasons that we are looking for a replacement is their way of defining integration. The language of the XML structures that I use to describe the integrations are not that standard, and it's not easy to find people who are familiar with this approach."
"The integration capabilities need to be improved."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
 

Pricing and Cost Advice

"The solution has a return on investment but is a little expensive."
"The licensing cost is very expensive."
"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."
"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."
"The cost is very high and requires all five components in the API management solution."
"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."
"It's expensive when you compare it with others."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"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 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.
872,869 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
9%
Computer Software Company
8%
Manufacturing Company
7%
Financial Services Firm
15%
Computer Software Company
11%
Government
7%
Comms Service Provider
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?
I have significant experience with the IBM DataPower Gateway. As a security product, it is very good. However, from the development perspective, it has limitations because it only supports the XSLT...
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: November 2025.
872,869 professionals have used our research since 2012.