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

Microsoft Azure API Management vs OpenLegacy 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
6.9
Number of Reviews
82
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
36th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the API Management category, the mindshare of Microsoft Azure API Management is 16.5%, down from 19.7% compared to the previous year. The mindshare of OpenLegacy is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
Microsoft Azure API Management16.5%
OpenLegacy0.5%
Other83.0%
API Management
 

Featured Reviews

Allan Møller - PeerSpot reviewer
Transforms internal APIs with secure, manageable cloud compatibility
Microsoft Azure API Management could be improved by enhancing the preview feature, specifically the workspaces. The feature should allow for better delegation of permissions to specific groups without affecting others. The service is extensive and expensive, and this added flexibility would make it more manageable and less prone to errors.
reviewer1042905 - PeerSpot reviewer
The biggest advantage is how simple the technology was.
I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.

Quotes from Members

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

Pros

"Azure API Management is an API gateway that can be used for different purposes, for example, to monetize APIs."
"The stability and performance are good. It is easy to install, and it scales well too."
"It's easy to use compared to other products. It's easy to set up."
"The integration process is very easy, which is crucial for our organization."
"Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those."
"The price is pretty reasonable for us."
"The product gives API gateway-related features, like throttling, which are easy to use and low-code/no-code."
"It's easier to use and has more features than Google."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
 

Cons

"This solution is only available as a cloud-based deployment and it would be very helpful to have an on-premises version."
"The solution's integration suite needs improvement."
"Technical support could be more helpful and responsive."
"They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet."
"Other products have more customization options."
"I would like to see more security features become available."
"Support for GraphQL could be better."
"The cloud deployment performance could be better."
"Debugging and logging for programmers could be better."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
 

Pricing and Cost Advice

"Since this is a cloud-based solution you have to abide by those financial limits, this creates some different challenges compared to other solutions."
"This is an expensive solution."
"On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten."
"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 developer and standard pricing tiers of Azure API Management are very competitive compared to other products."
"Since everyone is isocentric here, it is reasonable for me."
"There are no additional costs above the main license."
"It's pay as you go. The subscription packages have room for different scales. It's calculated by the number of apps or computers you use. You do not have to use the enterprise subscription. These subscriptions have different pricing, so you can find one to meet your needs for scalability."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
869,566 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
12%
Manufacturing Company
9%
Insurance Company
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise52
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.
Ask a question
Earn 20 points
 

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
Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Find out what your peers are saying about Microsoft Azure API Management vs. OpenLegacy and other solutions. Updated: September 2025.
869,566 professionals have used our research since 2012.