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

Choreo WSO2 Enterprise Integrator vs IBM DataPower Gateway comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 18, 2026

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

Choreo WSO2 Enterprise Inte...
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)
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)
 

Mindshare comparison

As of November 2026, in the Enterprise Service Bus (ESB) category, the mindshare of Choreo WSO2 Enterprise Integrator is 4.9%, down from 5.7% compared to the previous year. The mindshare of IBM DataPower Gateway is 4.9%, down from 6.4% 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

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.
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.

Quotes from Members

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

Pros

"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The learning curve for this solution is very good."
"While I am still exploring the solution, I've so far been pretty satisfied with it."
"The stability is excellent."
"The productivity is the most valuable feature. It is very easy to write remediations."
"WSO2's analytics capability is good, considering the ELC support they provide."
"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."
"Anybody can use it as their security device and as their multi-protocol handling device."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"I like all of the features in this product and it does what it's supposed to do."
"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."
"I like that it is very stable, and we never experience any downtime."
"The solution is very easy to work with."
"Since it is a gateway, it provides a lot of security features."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
 

Cons

"They should introduce better pricing for small companies."
"Most of the issues we run into with the WSO2 Enterprise Integrator deal with customizations."
"You cannot include the validation of XPath."
"They should release upgrades more frequently."
"For simpler tasks or simpler use cases, we avoid using WSO2 Enterprise Integrator because it is quite complex."
"The product's price is an area of concern where improvements are required."
"The server is very specific and it is very difficult to get experience with it."
"The administration side is complex and could use significant improvements to enhance the solution's functionality."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."
"They should improve the solution's clustering features."
"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."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"The programming language is only supported in XSLT and Gateway script."
"It is challenging to understand the solution's design and support skills."
 

Pricing and Cost Advice

"It is a low-cost solution."
"The cost is better than IBM Cloud Pak."
"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 open-source, unsupported version is available free of charge."
"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 an expensive solution."
"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 solution has a return on investment but is a little expensive."
"The tool's initial costing is expensive for small banks and financial institutions."
"The solution is expensive in comparison to other products."
"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."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
922,349 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
14%
Financial Services Firm
8%
Construction Company
8%
Comms Service Provider
7%
Financial Services Firm
21%
Outsourcing Company
9%
Manufacturing Company
8%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise11
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
 

Questions from the Community

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...
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.
 

Also Known As

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

Overview

 

Sample Customers

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