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

Tyk 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

Tyk
Ranking in API Management
20th
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
6
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
9th
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) (9th), 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 Tyk is 2.0%, up from 1.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

MarkDoherty - PeerSpot reviewer
Fastest to get up and running and fewer idiosyncrasies than competitors
In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them. But as a product, it's very difficult to find any major faults.
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 most valuable feature is the load balancing with the circuit-breaker function."
"The feature I find most valuable is that this solution allows us to manage our security."
"It is a good product for API management."
"You can set up workflows and write limited pieces of logic."
"The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good."
"The portal for developers that this solution provides has great functionality."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"From a user perspective, the feature which I like the most about Integration Server is its designer."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"The core product can be used not only for automatic file transfers between applications, but also as an Enterprise Service Bus (ESB)."
"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"
"The performance is good."
"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."
 

Cons

"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
"Sometimes when new features are released, they are not immediately stable."
"We would like a better tool for generating documentation for the APIs to be developed."
"It is a young product and does not have the kind of brand recognition that would make it a more popular solution with our clients."
"We ran it for a while, but then we decided to move away from Tyk, because Tyk's cloud version, the SaaS version, has a significant limitation of limited flexibility, so you can't program very much."
"In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them."
"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."
"It could be more user-friendly."
"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 deployment should be simplified."
"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."
"The solution should include REST API calls."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"Rapid application development has to be considered, especially for UI, where user interference is crucial."
 

Pricing and Cost Advice

"We are using the open-source version of this product, so there are no licensing costs for its use."
"It had a free version, which suited many of our needs, but not all, but we were happy to go ahead with the licensed version as well, which is the paid version."
"The price is low compared to other products of a similar type."
"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."
"The cost curve is far smoother, both in terms of volume and the number of calls it's running on, compared to most competitors. So it's a tad more expensive at the very low end, but the curve is nothing like Apigee or some of the others."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"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."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"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."
"It is worth the cost."
"I would like to see better pricing for the license."
"webMethods.io Integration's pricing is high and has yearly subscription costs."
"The product is expensive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
14%
Healthcare Company
7%
Comms Service Provider
6%
Computer Software Company
13%
Financial Services Firm
13%
Manufacturing Company
13%
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 Tyk?
The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good.
What is your experience regarding pricing and costs for Tyk?
The pricing is actually quite competitive. In Azure environments, it gets beaten by Microsoft API Gateway, but on the other hand, it offers some features that Microsoft lacks. So it really comes do...
What needs improvement with Tyk?
In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly ...
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.
 

Comparisons

 

Also Known As

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Trip Advisor, Juniper Networks, AT&T
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Tyk vs. webMethods.io and other solutions. Updated: April 2025.
851,604 professionals have used our research since 2012.