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

Aurea CX Messenger vs webMethods.io 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

Aurea CX Messenger
Ranking in Enterprise Service Bus (ESB)
12th
Average Rating
9.0
Reviews Sentiment
7.7
Number of Reviews
7
Ranking in other categories
Business Activity Monitoring (3rd), Message Queue (MQ) Software (9th), SOA Governance (3rd), Message Oriented Middleware (MOM) (7th)
webMethods.io
Ranking in Enterprise Service Bus (ESB)
3rd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Managed File Transfer (MFT) (10th), API Management (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of April 2025, in the Enterprise Service Bus (ESB) category, the mindshare of Aurea CX Messenger is 0.6%, up from 0.5% compared to the previous year. The mindshare of webMethods.io is 10.7%, up from 9.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

Featured Reviews

Radhey Rajput - PeerSpot reviewer
Lightweight and efficient solution
It's very good and lightweight. But, it does not provide web service communication. But it is excellent for internal connections One valuable feature is the messaging broker. If there is a disruption, it restores the messages. And when the application is running, it delivers all the messages. The…
Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.

Quotes from Members

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

Pros

"The features that I have found most valuable are that it is very easy to develop. Most of it is graphical, but we also have the option to add any custom call that you need."
"SDM: User-friendly tool which allows for a seamless approach to performing hotfixes, if required."
"The solution is highly scalable, this is very important for us. It can handle a lot of messages."
"ESB: Provides all kind of possibilities to resolve business needs. A lot of ready to use services plus custom Java services. I used a lot of them all."
"The solution offers excellent stability."
"The Messenger Broker is a really good feature."
"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."
"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."
"High throughput and excellent scalability."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."
"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."
"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
 

Cons

"It should include/add more services with the product as per market demand. It should include custom Java services developed by any organization or provide a platform where users/developers can share ideas/custom services, etc."
"You should not hurry with upgrades without testing the whole product completely."
"Aurea CX Messenger could improve by making better use of the new APIs"
"The improvement is that it should be on the cloud and use web services."
"I don't know if the last version has the cloud option, but maybe that could be good. That could be something that is included."
"The solution needs to improve support for new, more recent protocols on the API."
"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."
"It could be more user-friendly."
"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."
"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."
"Rapid application development has to be considered, especially for UI, where user interference is crucial."
"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
 

Pricing and Cost Advice

"You pay nothing for licensing, because the commercial model is a subscription. Other environments, such as QA and Development, are included in the subscription"
"Much better than Oracle SOA Suite."
"The pricing is not so high."
"There is a license needed to use the webMethods Integration Server."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"The price is high and I give it a five out of ten."
"webMethods Trading Networks is a bit costly compared to others solutions."
"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"I am not involved in the licensing side of things."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
849,190 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
17%
Insurance Company
8%
Retailer
6%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
12%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Aurea CX Messenger?
The Messenger Broker is a really good feature.
What is your experience regarding pricing and costs for Aurea CX Messenger?
The pricing is not so high. I will rate it a seven out of ten, where one is the lowest and ten is the highest. There are no additional fees to the standard license.
What needs improvement with Aurea CX Messenger?
The improvement is that it should be on the cloud and use web services because the earlier version is not using web service and cloud functionality. If Aurea could include these features in the fut...
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

CX Messenger Enterprise, Aurea Sonic ESB, Aurea Sonic, Aurea Sonic MQ
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Heathrow, HomeServe, Paypal, Freedom Mortgage
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Aurea CX Messenger vs. webMethods.io and other solutions. Updated: April 2025.
849,190 professionals have used our research since 2012.