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

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

IBM API Connect
Ranking in API Management
8th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
Integration Platform as a Service (iPaaS) (9th)
Tyk
Ranking in API Management
17th
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 July 2025, in the API Management category, the mindshare of IBM API Connect is 6.3%, up from 6.3% compared to the previous year. The mindshare of Tyk is 2.1%, up from 1.7% 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

"This solution is ready to scale and already supports our agile CICD."
"IBM API Connect is a reliable and scalable solution."
"The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed."
"It's quite flexible and easy to deploy, especially for beginners. It has almost all the features that an API gateway should have."
"The interface is very nice. It makes the solution easy to use and navigate."
"The functionalities on offer are very good."
"Security is well organized and managed within the solution."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"The feature I find most valuable is that this solution allows us to manage our security."
"You can set up workflows and write limited pieces of logic."
"The portal for developers that this solution provides has great functionality."
"It is a good product for API management."
"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 most valuable feature is the load balancing with the circuit-breaker function."
 

Cons

"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"Improving the documentation would be beneficial as it currently presents navigation challenges. Incorporating a step-by-step guide could facilitate the integration or migration of various systems, including databases. The existing documentation only comprises plain text, hence incorporating more interactive instructions could enhance its usefulness."
"The initial setup and installation could be easier."
"Firstly, the pricing model, when compared to other open sources, is high. Secondly, the availability of resources in the market, specifically the developers available in the market, is not so much."
"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."
"They seem to have left out a feature for microservices and also a certification module for OIDC."
"The developer portal could be easier to customize."
"The implementation of IBM API Connect is complex, as it's an enterprise solution with many components that require more than one person. It's not a single product that you work on, and this is an area for improvement, but normally, it's good. Having a more structured model for IBM API Connect support is also room for improvement that would help customers better."
"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."
"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."
"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."
"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 can be quite expensive. It's okay for large-scale usage but quite expensive for smaller-scale implementations."
"API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution."
"API Connect is quite pricey."
"The price for IBM API Connect is reasonable. It's $20,000 to $30,000 yearly for a subscription, and the pricing could vary around $40,000 per year, per subscription. Its price is reasonable for customers who have around sixty million API calls yearly for unlimited environments."
"I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud."
"We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee."
"IBM API Connect could be cheaper."
"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."
"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."
"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
860,168 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Educational Organization
13%
Insurance Company
12%
Computer Software Company
9%
Financial Services Firm
26%
Computer Software Company
15%
Comms Service Provider
7%
Healthcare Company
5%
 

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?
Pricing depends on how many instances run across environments. I don't deal with licensing, but compared to other IBM products, the licensing is not significantly higher.
What needs improvement with IBM API Connect?
When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer. Examples include the lack of connectivity to MQ ( /categories/message-queue-mq...
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

 

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: June 2025.
860,168 professionals have used our research since 2012.