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

TIBCO Cloud API Management vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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

TIBCO Cloud API Management
Ranking in API Management
28th
Average Rating
7.0
Reviews Sentiment
6.5
Number of Reviews
11
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 March 2025, in the API Management category, the mindshare of TIBCO Cloud API Management is 0.9%, down from 1.0% compared to the previous year. The mindshare of webMethods.io is 2.1%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Amitava Roy - PeerSpot reviewer
Offers pre-built packages for quick and easy onboarding of APIs but configuration is not that easy
The configuration is not that easy. It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either. There are certain things where the performance is not that great. When the traffic is huge, we see some lag in performance.
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

"We can completely manage the APIs at the org level and BU (business unit) level."
"It has something called packages. In that way, it's good because we have some pre-built packages. So, if you want to onboard different APIs, we can just add them to the package, and it's there."
"The most valuable feature is the ability to have different packages based on the API keys. The same core system can have different packages based on different environments."
"The control that we have and the security features are very valuable. With regard to API implementation or API orchestration, it works very well in the cloud because as soon as you create an API with one click, you can actually expose your APIs."
"It is easy to work with ."
"This has provided a new stream of traffic and exposure of our catalogue beyond the normal web store offering."
"The most valuable aspect of Mashery is its stability."
"Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers)."
"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."
"Ease of implementation and flexibility to hold the business logic are the most valuable features."
"The messaging part is the most valuable feature."
"EDI is robust and integration with SAP is good."
"The solution is scalable."
"From a user perspective, the feature which I like the most about Integration Server is its designer."
"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."
"The product supports various types of digital documents, including XMLs and EDI."
 

Cons

"It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either."
"We observed delays under heavy load conditions, and without proper tuning, changes could take an extended period to filter and become effective."
"TIBCO Cloud API Management should improve its installation and make it easy."
"The security needs improvement, specifically, propagation of security to an API. Calling other APIs is something that is missing in the product and that makes us think about going to a competitor."
"They can fix some stability issues and probably make it more user-friendly so that not only an IT savvy person but an end-user can also easily navigate through this solution."
"I'd like to see TIBCO integrate authentication and security features into Mashery."
"The management console of API and customers' applications are not the most intuitive."
"Policy management has been a bit of a concern."
"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."
"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."
"webMethods Integration Server needs to add more adapters."
"It is quite expensive."
"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."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."
 

Pricing and Cost Advice

"We have secured terms on which we have been happy to renew for a number of years."
"TIBCO Cloud API Management is not an expensive solution."
"Licensing is quite flexible."
"Its price is pretty reasonable. There are some lightweight API options available in the market, but given the feature set that TIBCO provides, its price is really reasonable."
"It's a good deal for the money that we pay."
"Most of my clients would like the price of the solution to be reduced."
"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."
"The product is expensive."
"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."
"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."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"It is a cost-effective solution."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
842,388 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
24%
Financial Services Firm
15%
Manufacturing Company
10%
Real Estate/Law Firm
5%
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 TIBCO Cloud API Management?
The platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads.
What is your experience regarding pricing and costs for TIBCO Cloud API Management?
My primary role was to assess the solution from a capability perspective. So, there are some issues with the licensing cost.
What needs improvement with TIBCO Cloud API Management?
The configuration is not that easy. It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either. There are certain things whe...
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

Mashery API Management
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

uShip, Sabre, TouchTunes, Best Buy, Cisco, Comcast, athenahealth, Coca-Cola Enterprises, CentralIndex.com, Constant Contact, Edmunds.com, FoodEssentials, Getty Images, Klout, Rovi, Rotten Tomatoes, Sportradar, TomTom, ACTIVE.com
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about TIBCO Cloud API Management vs. webMethods.io and other solutions. Updated: March 2025.
842,388 professionals have used our research since 2012.