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

OpenText Trading Grid vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive Summary

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

OpenText Trading Grid
Ranking in Business-to-Business Middleware
12th
Ranking in Cloud Data Integration
35th
Ranking in Integration Platform as a Service (iPaaS)
20th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
1
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in Business-to-Business Middleware
3rd
Ranking in Cloud Data Integration
10th
Ranking in Integration Platform as a Service (iPaaS)
7th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
93
Ranking in other categories
Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (11th), API Management (11th)
 

Mindshare comparison

As of October 2025, in the Integration Platform as a Service (iPaaS) category, the mindshare of OpenText Trading Grid is 1.8%, up from 1.2% compared to the previous year. The mindshare of webMethods.io is 7.9%, down from 9.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Integration Platform as a Service (iPaaS) Market Share Distribution
ProductMarket Share (%)
webMethods.io7.9%
OpenText Trading Grid1.8%
Other90.3%
Integration Platform as a Service (iPaaS)
 

Featured Reviews

VARUNKUMAR - PeerSpot reviewer
Industry-leading, easy to implement, and has good mapping specification guidelines
The good thing about OpenText is that we have the mapping specification guideline available, which is not there in a solution like SEEBURGER. Whenever you want to take a decision to move away from OpenText, you have already documented your mapping and what your mapping looks like. So you go to the next provider, provide them with that mapping specification, and it'll be very easy for them to develop a new map instead of just taking the data - input data, output data - and then looking for how the data is getting transformed. So you have the mapping spec level which is a very good feature of OpenText, which we do not have in SEEBURGER. It's very hard to move from SEEBURGER. The solution is easy to implement. It's stable and reliable. They are the industry leaders in the integration space.
MohanPrasad - PeerSpot reviewer
Smooth integration and enhanced deployment with high licensing cost
webMethods.io was used to integrate APIs through the webMethods.io platform, trigger database events, and connect backend APIs through a Java backend. It was used extensively for integration purposes in my organization Integration became smoother, troubleshooting was easier, and deployment and…

Quotes from Members

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

Pros

"The solution is easy to implement."
"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."
"There's hardware, software and application integration, providing hosting flexibility."
"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."
"They are the building blocks of EAI in SAG products, and they offer a very good platform."
"It's very flexible and a good platform to use."
"The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together."
"My impression of webMethods.io's drag-and-drop interface to design workflows is actually amazing."
"The core product can be used not only for automatic file transfers between applications, but also as an Enterprise Service Bus (ESB)."
 

Cons

"Technical support needs to be better."
"The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
"Scalability and connectors to different cloud applications is lacking."
"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."
"Need to see more API portal features like monetizing APIs and private cloud readiness."
"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
 

Pricing and Cost Advice

Information not available
"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."
"Its cost depends on the use cases."
"The solution’s pricing is too high."
"Some who consider this solution often avoid it due to its high price."
"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."
"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."
"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
report
Use our free recommendation engine to learn which Integration Platform as a Service (iPaaS) solutions are best for your needs.
868,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
15%
Retailer
13%
Computer Software Company
9%
Media Company
6%
Manufacturing Company
14%
Computer Software Company
12%
Financial Services Firm
11%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise63
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Also Known As

Trading Grid, GXS Trading Grid
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Autoliv, Hella, Hutchinson, Michelin
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Microsoft, Salesforce, SAP and others in Integration Platform as a Service (iPaaS). Updated: September 2025.
868,706 professionals have used our research since 2012.