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

Apollo GraphOS 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

Apollo GraphOS
Ranking in API Management
31st
Average Rating
7.0
Reviews Sentiment
3.9
Number of Reviews
1
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
10th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Featured Reviews

Sagor Rana - PeerSpot reviewer
Efficiently filters API data though experiences slower performance with larger projects
I would like to see better performance in larger projects. When dealing with large amounts of data, it can become slow, causing users to potentially abandon the application. Improving performance and ensuring the app runs smoothly would enhance user experience. Stability issues, where it sometimes breaks down, need to be addressed as well.
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 most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"It's easy to construct new interfaces like apps and client portals."
"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."
"EDI is robust and integration with SAP is good."
"We have found the pricing of the solution to be fair."
"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."
"The stability is good."
"webMethods Trading Networks is a stable solution."
"Operationally, I consider the solution to be quite good."
 

Cons

"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage. It sometimes takes longer than three seconds, which can affect loading times and lead to user dissatisfaction. I would like to see improved performance."
"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage."
"Rules engine processes and BPM processes should be improved."
"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"I would like to see the price improve."
"The on-premises setup can be difficult."
"Support is expensive."
"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"The installation process should be simplified for first time users and be made more user-friendly."
 

Pricing and Cost Advice

Information not available
"Some of the licensing is "component-ized," which is confusing to new users/customers."
"Most of my clients would like the price of the solution to be reduced."
"Initialy good pricing and good, if it comes to Enterprise license agreements."
"The pricing is a yearly license."
"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."
"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."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
849,335 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
12%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Apollo GraphOS?
I am not sensitive to nor very knowledgeable about the pricing and setup cost.
What needs improvement with Apollo GraphOS?
I would like to see better performance in larger projects. When dealing with large amounts of data, it can become slow, causing users to potentially abandon the application. Improving performance a...
What is your primary use case for Apollo GraphOS?
I primarily use Apollo GraphQL to work with APIs in conjunction with Node.js. When I make API calls, I receive a lot of information, but I only need specific details like names, emails, and photos....
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

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Information Not Available
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management. Updated: April 2025.
849,335 professionals have used our research since 2012.