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
4.6
Number of Reviews
2
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
94
Ranking in other categories
Business-to-Business Middleware (2nd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (9th), Cloud Data Integration (8th), Integration Platform as a Service (iPaaS) (7th)
 

Mindshare comparison

As of January 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.6%, up from 0.1% compared to the previous year. The mindshare of webMethods.io is 2.5%, up from 2.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
webMethods.io2.5%
Apollo GraphOS0.6%
Other96.9%
API Management
 

Featured Reviews

Sagor Rana - PeerSpot reviewer
Front End Engineer at Upwork
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.
YM
Developer at a hospitality company with 1,001-5,000 employees
Offers strong integration capabilities and reliable features but needs pricing and scaling improvements
Many things are evolving with the AI buzz in the market. What I would like to see improved or enhanced in webMethods.io in the future is that since webMethods.io is already under IBM, I think IBM will introduce and integrate AI into it. Additionally, regarding what webMethods.io can improve is the license cost. Other cloud players are also providing the same kind of functionality, such as AWS and Azure. webMethods.io is being installed on-premises, but AWS is providing it directly in the cloud. When comparing the license cost and request per minute cost, webMethods.io needs to address that. There are many competitors in the market for this.

Quotes from Members

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

Pros

"Apollo GraphOS has significantly enhanced both the developer experience and product delivery timelines by offering a centralized approach to managing GraphQL schemas and services, helping reduce overhead and improve collaboration between frontend and backend teams."
"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."
"They are the building blocks of EAI in SAG products, and they offer a very good platform."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"Segregation of deployment for the environments is the most valuable feature of the solution."
"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"How simple it is to create new solutions."
"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."
 

Cons

"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"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."
"Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it. Its price can also be better. It is pretty costly because they charge us for each transmission."
"webMethods Integration Server needs to add more adapters."
"webMethods.io lacks advanced monitoring and analytics capabilities, so my customers need to use something additional."
"The learning curve is a little steep at first."
"I would like the solution to provide bi-weekly updates."
"Scalability and connectors to different cloud applications is lacking."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."
 

Pricing and Cost Advice

Information not available
"The vendor is flexible with respect to pricing."
"Some of the licensing is "component-ized," which is confusing to new users/customers."
"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."
"The product is very expensive."
"It's a good deal for the money that we pay."
"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."
"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."
"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
881,114 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
14%
Financial Services Firm
12%
Computer Software Company
10%
Energy/Utilities Company
7%
 

Company Size

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

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?
So far, I could say that Apollo GraphOS is quite comprehensive, there’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overla...
What is your primary use case for Apollo GraphOS?
I’ve been using Apollo GraphOS across several mobile and web projects. On the mobile side, I’ve integrated it with React Native and Flutter. For web applications, the usage has been primarily withi...
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 Apollo GraphOS vs. webMethods.io and other solutions. Updated: December 2025.
881,114 professionals have used our research since 2012.