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

SAS Access 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

SAS Access
Average Rating
9.0
Reviews Sentiment
7.5
Number of Reviews
3
Ranking in other categories
Data Integration (59th)
webMethods.io
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
94
Ranking in other categories
Business-to-Business Middleware (6th), Enterprise Service Bus (ESB) (5th), Managed File Transfer (MFT) (13th), API Management (16th), Cloud Data Integration (11th), Integration Platform as a Service (iPaaS) (11th)
 

Featured Reviews

Robert Heck - PeerSpot reviewer
Co Owner at Hecht und Heck GmbH
The solution is stable, scalable, and flexible
I rate the solution eight out of ten. The number of people required to maintain the solution is dependent on the other applications running. The solution in itself does not require a lot of maintenance. The solution is flexible and I recommend it when you have more complex applications with special requirements.
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

"The most valuable feature is you have native access to the external databases."
"The most valuable part of SAS/ACCESS is what it is made for: connecting to remote systems that are not part of your physical SAS environment."
"The SAS/ACCESS ability to connect creates an elegant simplicity."
"The most valuable aspect of the solution is the ease of access to the data in those databases."
"The most valuable aspect of the solution is the ease of access to the data in those databases."
"The most valuable feature is you have native access to the external databases."
"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."
"Ease of implementation and flexibility to hold the business logic are the most valuable features."
"CentraSite for governance and life cycle management frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."
"This solution is flexible and can be used across a number of projects."
"The scope of abilities for webMethods is pretty much unlimited."
"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."
"The product supports various types of digital documents, including XMLs and EDI."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
 

Cons

"The solution's pricing and licensing are expensive."
"The solution can provide access to the newer databases that come out sooner."
"I can't really recall any missing feature or general improvement that is needed. We don't really add too many new kinds of databases and therefore our needs are already met."
"The pricing model needs to be reconsidered and adjusted."
"The primary way that this product can be improved is by adjusting their pricing model."
"Programming model with flow is hopelessly outdated."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
"Scalability and connectors to different cloud applications is lacking."
"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."
"The installation process should be simplified for first time users and be made more user-friendly."
"This solution could be improved by offering subscription based licensing."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
 

Pricing and Cost Advice

"The pricing model is complex and is based on modular packages as well as the size of the applicable environment."
"The solution's pricing and licensing are expensive."
"The solution’s pricing is too high."
"There is a license needed to use the webMethods Integration Server."
"I am not involved in the licensing side of things."
"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."
"The vendor is flexible with respect to pricing."
"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."
"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."
"The pricing is a yearly license."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
15%
Financial Services Firm
14%
Comms Service Provider
8%
Manufacturing Company
8%
Manufacturing Company
13%
Financial Services Firm
11%
Computer Software Company
9%
Comms Service Provider
5%
 

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

Ask a question
Earn 20 points
What needs improvement with webMethods Integration Server?
The alignment of on-premise and cloud versions needs improvement.
What needs improvement with webMethods Trading Networks?
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 w...
What is your primary use case for webMethods Trading Networks?
I use webMethods.io primarily for the integration of APIs. Could you please describe a few use cases for it?
 

Also Known As

SAS/Access
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Los Angeles County, West Midlands Police, Credit Guarantee Corporation, Canada Post, Allianz Global Corporate & Specialty
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about SAS Access vs. webMethods.io and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.