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

IBM API Connect vs Tyk comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024
 

Categories and Ranking

IBM API Connect
Ranking in API Management
5th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
75
Ranking in other categories
Integration Platform as a Service (iPaaS) (7th)
Tyk
Ranking in API Management
19th
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the API Management category, the mindshare of IBM API Connect is 6.5%, up from 6.4% compared to the previous year. The mindshare of Tyk is 2.0%, up from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Shanmugasundaram Shanmuganathan - PeerSpot reviewer
Offers basic API orchestration and provides robust security and governance features
While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome. Overall, I would rate the scalability an eight out of ten. Almost all applications we've been exposing lately go through this middleware, so it's used extensively. There are around sixty applications directly using it, but six Kubernetes clusters serve those applications. It's heavily used for integration, including system-to-system integration and product integrations. Our usage has been increasing year-on-year based on our needs.
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It allows enterprises to expose some of their tech to outside stakeholders."
"One of the most valuable features is the easy-to-use web interface."
"Since it runs on top of Datapower, all Datapower based custom policies can be utilized and exported to API connect but its not straightforward/simple process."
"In-built policies and security functions."
"The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster."
"The most valuable feature for me is the ability to distribute work among our API developers, so we don't have to do all the work as IBM API Connect administrators and IBM DataPower administrators."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"The solution is very stable."
"You can set up workflows and write limited pieces of logic."
"It is a good product for API management."
"The most valuable feature is the load balancing with the circuit-breaker function."
"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 feature I find most valuable is that this solution allows us to manage our security."
 

Cons

"While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome."
"The installation process could use improvement. I hope that in the next release, the installation process is easier."
"Different versions of the same thing can mean unnecessary duplication."
"The developmental process is not quite user-friendly."
"Extracting the data could be improved."
"Documentation for the CLI is not very complete. Also, the support could be improved, and we have had several problems with backing up and restoring the product."
"One thing about API Connect that could be improved is the security schemes. There are so many security schemes, and from a product perspective, IBM could improve the user experience of the configuration security scheme."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"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."
"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."
"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 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."
 

Pricing and Cost Advice

"API Connect was highly expensive for us, but the decision to switch was made before I joined the company. It seems like the company bought it, but they didn't know how to use it. After two years, they decided to reevaluate and conduct some cost estimates."
"It should be cheaper. It has a yearly licensing."
"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"It can be quite expensive. It's okay for large-scale usage but quite expensive for smaller-scale implementations."
"The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight."
"Pricing for IBM API Connect varies, e.g. it could be subscription-based. Deploying it on private cloud also means you have to own most of the software licensing."
"It is a pretty expensive tool."
"It's an expensive product."
"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."
"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."
"We are using the open-source version of this product, so there are no licensing costs for its use."
"The price is low compared to other products of a similar type."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
825,625 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
21%
Financial Services Firm
19%
Insurance Company
10%
Computer Software Company
9%
Financial Services Firm
24%
Computer Software Company
16%
Healthcare Company
7%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about IBM API Connect?
Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules.
What is your experience regarding pricing and costs for IBM API Connect?
It is a pretty expensive tool. The tool is expensive if I consider how products like WSO2 are available in the market. You have pretty much many options in the open-source community, considering ho...
What needs improvement with IBM API Connect?
The only downside where improvements are needed is probably on the licensing side. Scalability is an issue with IBM API Connect, making it an area where improvements are required.
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 ...
 

Comparisons

 

Learn More

Video not available
 

Overview

 

Sample Customers

Heineken, Tine, Finologee, Axis Bank
Trip Advisor, Juniper Networks, AT&T
Find out what your peers are saying about IBM API Connect vs. Tyk and other solutions. Updated: December 2024.
825,625 professionals have used our research since 2012.