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

Perforce Acana 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

Perforce Acana
Ranking in API Management
28th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
3
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)
 

Mindshare comparison

As of May 2025, in the API Management category, the mindshare of Perforce Acana is 0.5%, down from 0.7% compared to the previous year. The mindshare of webMethods.io is 2.3%, up from 2.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Saurav Krishna - PeerSpot reviewer
Authentication mechanism is easy to implement but improvement is needed in documentation
For API security purposes, we use the tool to host all our APIs. This allows us to take advantage of the security features provided by the platform. With the solution, we can implement rules such as rate limiting and restricting the number of API calls for each user. It acts as a secure gateway…
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 tool's authentication mechanism is easy to implement. We had to define a few parameters."
"Good interface, intuitive solution."
"It allowed us to publish and replace pre-essential transactions in one place, with a uniformity in terms of control and policies."
"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."
"webMethods Trading Networks is a stable solution."
"Our use case is for integration factory for SAP. It is mostly for SAP integration."
"It's a good tool, and it has a stable messaging broker."
"It has a good integration server, designer, and a very good API portal."
"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."
"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."
"The tool supports gRPC."
 

Cons

"The product has new features that we are going to implement in the next few months, such as API management and analytic reporting."
"Lacks an integrated billing feature."
"Akana API Management needs to improve its documentation."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
"For code version control, you need to use some external software."
"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."
"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."
"The interface needs some work. It is not very user-friendly."
"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."
"Prices should be reduced, ideally by up to 30% for long-term customers like us."
 

Pricing and Cost Advice

"For us, the pricing and licensing policies were for an on-premise installation with a fixed cost structure, that matched our budgeting policies."
"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."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."
"I am not involved in the licensing side of things."
"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 price is high and I give it a five out of ten."
"There is a license needed to use the webMethods Integration Server."
"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.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
14%
Manufacturing Company
12%
Healthcare Company
10%
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 do you like most about Akana API Management?
The tool's authentication mechanism is easy to implement. We had to define a few parameters.
What needs improvement with Akana API Management?
Akana API Management needs to improve its documentation.
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

British American Tobacco, Credit Suisse, Daimler, eBay, FOX, Liberty Mutual, Marriott, Mayo Clinic, Skandia, Tata communications
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Perforce Acana vs. webMethods.io and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.