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

Microsoft Azure API Management 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

Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
81
Ranking in other categories
No ranking in other categories
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
 

Mindshare comparison

As of May 2025, in the API Management category, the mindshare of Microsoft Azure API Management is 17.9%, down from 19.8% compared to the previous year. The mindshare of Tyk is 2.0%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Rajiv Bala Balasubramanian - PeerSpot reviewer
Efficiently manages and monetizes API
It is a scalable solution. You can add more computing power to your APM gateway. It also gives you the ability to have VNet integrations with your on-prem. It is one of the leading products in the API management space. It is not just software for users but software to handle requests. For example, for a B2C e-commerce store, all requests that users make from within the store pass through this API gateway. So it is defined by the number of requests to the API gateway, not by the number of actual users who use it. If you look at the number of requests, it would be a lot from all the different systems we have within Pampers.
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

"The user management is pretty seamless."
"The Azure Active Directory Synchronization is quite good."
"The most valuable features of the solution are its importing and publishing."
"The API management and the hosting of the API platform are great."
"The tool is very easy to use and manage APIs."
"Microsoft Azure API Management serves as a gateway for all API management within our tech environment and is a basic part of our DevOps toolchain."
"We're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting."
"The integration and API Connect are valuable when we need to connect with web services and REST APIs."
"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."
"It is a good product for API management."
"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."
"You can set up workflows and write limited pieces of logic."
"The portal for developers that this solution provides has great functionality."
 

Cons

"Documentations for implementing certain product features are very difficult to find"
"I would like to see better scalability and better performance."
"The solution's integration suite needs improvement."
"Previously, our company's cloud services were shut down, and we used to take more time to update services, so such issues are areas where improvements are needed."
"It would be better if it were easier to transition to Azure from JIRA. For example, different nomenclature must be performed when you shift to Azure from JIRA. JIRA's storage, tasks, and ethics are treated differently from Azure. Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. If someone has to get into the nomenclature, then there can be different tasks from clients, and here, they may be treated as functions. JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between ethics and a function and a story are different, and people may have to learn to adapt to the new nomenclature."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"Security could be improved."
"The cloud deployment performance could be better."
"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."
"We would like a better tool for generating documentation for the APIs to be developed."
"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."
"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."
 

Pricing and Cost Advice

"The developer and standard pricing tiers of Azure API Management are very competitive compared to other products."
"Azure is a pay-as-you-go model. You build out your virtual environment and pay a monthly price depending on CPU cores, storage, etc."
"It costs around 30,000 Kronas a month, which translates to about $3,000 dollars monthly."
"The licensing fees are expensive."
"The licensing cost for Microsoft Azure API Management is publicly available and goes from a developer edition that costs $26 to $30 per month. It may have changed, but it's in the neighborhood of $30 per month. I believe there's also the enterprise edition, which is highly capable and costs $2,500 per month."
"We pay for a yearly license."
"It's free for less than ten users. If you want to go beyond that, it's around $3.50 per user per month. If you want a DevOps integration, it's about $7.50 per user per month. Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all three flavors for $7.50 per user per month."
"The solution appears cheaper because it's a cloud SaaS model."
"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."
"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."
"We are using the open-source version of this product, so there are no licensing costs for its use."
"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.
850,671 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
9%
Insurance Company
7%
Financial Services Firm
28%
Computer Software Company
15%
Healthcare Company
7%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
What do you like most about Microsoft Azure API Management?
Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.
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 ...
 

Also Known As

Azure API Management, MS Azure API Management
No data available
 

Overview

 

Sample Customers

adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Trip Advisor, Juniper Networks, AT&T
Find out what your peers are saying about Microsoft Azure API Management vs. Tyk and other solutions. Updated: April 2025.
850,671 professionals have used our research since 2012.