No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon API Gateway 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

Amazon API Gateway
Ranking in API Management
2nd
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
45
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
32nd
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (83rd)
 

Mindshare comparison

As of July 2026, in the API Management category, the mindshare of Amazon API Gateway is 9.5%, down from 12.5% compared to the previous year. The mindshare of OpenLegacy is 1.4%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Amazon API Gateway9.5%
OpenLegacy1.4%
Other89.1%
API Management
 

Featured Reviews

SM
Head - Engineering ,Technology and Enterprise Architecture at a tech consulting company with 201-500 employees
Faced challenges with audit trails and seek better user-level monitoring and control
Regarding built-in authorization, monitoring is quite substantial, and versioning systems is also what we are using. With Amazon API Gateway, we utilize a variety of deployment methods and services they provide, so monitoring services are the important parameter in API control from our side, allowing us to see how the APIs behave and how well they pick up the data from their respective sources. Integration with AWS Lambda has been beneficial since we have event controllers that help identify the APIs, which then call the API from the API services. We're managing this with events that are parameterized through API identification, mostly using Python in Lambda, which has inbuilt features to track API lifecycle parameters. The defined parameterized features in Amazon API Gateway help streamline API lifecycle management. Our AWS system admin team sets these configurations for us. The versioning number gets updated as we deploy revised API versions, which gets monitored on the API monitoring services. The cloud engineering team assists us as we are from a solutions development and deployment team. The importance of Amazon API Gateway's global API deployment for our application's performance is significant in terms of scalability and availability. Amazon API Gateway services have been very good, maintaining a 99.99 SLA, providing us confidence in the global deployment level as it is capable of handling various endpoint types, such as database sites and legacy systems.
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

"It is very helpful, with our API-based applications."
"The scalability is very good."
"A most valuable feature of Amazon API Gateway is how quickly we can connect to backend services and have APIs accessible from anywhere."
"The initial setup is pretty easy. Deployment only takes five minutes."
"One of the most valuable aspects of API Gateway is its native integration with AWS services."
"The initial setup is straightforward."
"The solution is a managed service and requires minimal configuration, which makes it easy to launch an API."
"The Lambda features are very cost-effective since you do not have to run your servers 24/7."
"The product has helped our business by allowing us to become more efficient in data handling."
"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, and we were able to build out the OpenLegacy parts very quickly, putting together a couple hundred APIs in six months."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"Without OpenLegacy, it would take us several months to create the same services."
"OpenLegacy opens the door to connect modern web products to our old legacy system."
 

Cons

"API Gateway could improve by allowing debugging capabilities, particularly when dealing with high volumes. At scale, it is expensive, and latency sometimes occurs."
"The user interface could be improved, as well as customer support and having a local customer representative in a country."
"Amazon API Gateway can improve the user interface in some areas it could be more polished."
"I'm pretty happy with what Amazon API Gateway offers, but as its pricing is on the higher side, that's one area for improvement in the solution."
"Amazon API Gateway is not as complete as Apigee and needs to be improved by adding more features to become a more robust application."
"When it comes to DDoS protection, I would like to see that become available at the API Gateway level."
"The solution should include change data capture (CDC) features that will help reduce workload"
"The solution could improve signature validation."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
"Debugging and logging for programmers could be better."
"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."
"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."
"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."
 

Pricing and Cost Advice

"I am satisfied with the price."
"My understanding is that it easily goes to $14,000 or $15,000 USD each month for each account, and we have several such accounts."
"The solution is expensive. Though the product was previously available at a cheap rate, nowadays it is expensive."
"Since it's a serverless solution, Amazon API Gateway is not so expensive."
"I rate the tool's price as seven on a scale of one to ten, where one means low price and ten means high price."
"There is an annual licensing cost to use Amazon API Gateway."
"This is a pay-per-use service, where you only pay for what you use."
"Fees are volume-based."
"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.
904,680 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
11%
Computer Software Company
8%
Government
6%
Construction Company
24%
Financial Services Firm
13%
Comms Service Provider
12%
Manufacturing Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise12
Large Enterprise21
No data available
 

Questions from the Community

Which is better - Apigee or Amazon API Gateway?
Amazon API Gateway is a platform that supports the creation and publication of API for web applications. The platform can support thousands of simultaneous API calls, and it provides monitoring, ma...
How does Mulesoft Anypoint API Manager compare with Amazon API Gateway?
I have found that Mulesoft Anypoint API Manager is the best integration tool out there for API management. It is easy to implement and learn; it provides several options for deployment, (including ...
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 ...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Autodesk, Fox Digital Consumer Group, iFlix, UK Driver and Vehicle Licensing Agency (DVLA), Miovision, Olympusat, PhotoVogue, Royale International Group, Veracode
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 Amazon API Gateway vs. OpenLegacy and other solutions. Updated: June 2026.
904,680 professionals have used our research since 2012.