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
27th
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 May 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.3%, up from 2.0% 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

"Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers)."
"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 ."
"The solution is a good general API manager. They have a few propriety features but are offering items that are standard in the industry as well."
"Very few outages or SLA issues."
"The platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads."
"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."
"When we did the product evaluation, we saw that TIBCO Mashery offers end-to-end API life cycle management. It provides all API features that are required for managing the complete life cycle. It includes the developer portal and tools for API monitorization. The out-of-box security features that TIBCO Mashery provides are enterprise-grade, which gives it an edge over other API products."
"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."
"It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."
"Our use case is for integration factory for SAP. It is mostly for SAP integration."
"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."
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"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."
"It is a very stable product."
"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."
 

Cons

"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."
"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."
"TIBCO Cloud API Management should improve its installation and make it easy."
"Policy management has been a bit of a concern."
"I'd like to see TIBCO integrate authentication and security features into Mashery."
"It lacks many features at the API gateway compared to other solutions."
"The way agile life cycle is working needs improvement. I also want to see more support for open API standards. I want to see some improvement on the protocol transformation. That is quite missing now. These are the three main issues."
"Monetization is not that great in API management. You need customization. Improvements are needed with sandbox local as well as with monetization. Those features are missing."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."
"It is quite expensive."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."
"Prices should be reduced, ideally by up to 30% for long-term customers like us."
 

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."
"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."
"Licensing is quite flexible."
"The vendor is flexible with respect to pricing."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"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."
"There is a license needed to use the webMethods Integration Server."
"The price is a little bit high, especially regarding their support."
"The price is high and I give it a five out of ten."
"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."
"I would like to see better pricing for the license."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
23%
Financial Services Firm
16%
Manufacturing Company
10%
Retailer
6%
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: April 2025.
849,686 professionals have used our research since 2012.