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.8
Number of Reviews
83
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
37th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (44th)
 

Mindshare comparison

As of January 2026, in the API Management category, the mindshare of Microsoft Azure API Management is 15.0%, down from 19.3% compared to the previous year. The mindshare of OpenLegacy is 0.8%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
Microsoft Azure API Management15.0%
OpenLegacy0.8%
Other84.2%
API Management
 

Featured Reviews

RJ
Database Manager at a manufacturing company with 10,001+ employees
Facilitating seamless integration and robust security support
The integration process is very easy, which is crucial for our organization. Another valuable aspect is the support from Microsoft. Whenever support is required, it is readily available. Additionally, I appreciate the technical expertise Microsoft brings to the table. The security features are highly satisfactory, with various options providing flexibility to implement security measures based on specific compliance requirements.
reviewer1042905 - PeerSpot reviewer
VP, Chief Enterprise Integration Architect at a financial services firm with 10,001+ employees
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

"API Management does not take long to deploy."
"It's very well integrated with the Azure environment."
"The most valuable feature is its role as a linchpin in AI Hub architecture, enhancing data handling."
"The solution is quite stable. We have no issues with it. there have been no crashes and we haven't experienced bugs or glitches. It's been quite reliable."
"Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation."
"Azure APIM's best features are its straightforward access management (it's a single point of access for all monitoring and logging and for policy implementation) and its integration with the Azure Cloud infrastructure."
"Easy to integrate API management platform. It is a stable and scalable solution."
"The ability to easily connect back to Service Fabric is the most important for us."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"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."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"Opens the door to connect modern web products to an old legacy system."
 

Cons

"Microsoft Azure API Management needs to improve stability."
"Latency is an area that needs improvement, especially for multi-tenant applications."
"The integration with other API gateways is where they might try to improve."
"I would like to see more integration with other platforms, as well as increased security."
"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."
"The external policies are impossible to look at and configure."
"Sometimes when immediate support is required, it isn't available."
"In the API you need to delete the suffix. It is annoying that you need to have a suffix. We can add a suffix at the API level, not at the operation level, and that could be improved on."
"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."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"Debugging and logging for programmers could be better."
"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."
"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."
 

Pricing and Cost Advice

"Because of our partner relationship, our pricing is pretty decent. But in general, if I compare pricing, I think the initial offer that we got from Microsoft until the relationship kicked in was more expensive than AWS. There were some unexpected expenses because we had to pause. This was due to our inexperience and because we were doing this significant public cloud migration for the first time. We were using SAP on a public cloud for the first time."
"Azure API Management is the most expensive solution on the market."
"Compared to other solutions the cost is a seven out of ten."
"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 are paying standard fees to use Microsoft Azure API Management."
"The product pricing is reasonable."
"Microsoft is competitively priced."
"The developer and standard pricing tiers of Azure API Management are very competitive compared to other products."
"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.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
10%
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 Enterprise53
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: December 2025.
881,082 professionals have used our research since 2012.