Amazon API Gateway vs OpenLegacy comparison

Amazon Web Services (AWS) and OpenLegacy are both solutions in the API Management category. Amazon Web Services (AWS) is ranked #2 with an average rating of 8.1, while OpenLegacy is ranked #32. Amazon Web Services (AWS) holds a 9.5% mindshare in APIM, compared to OpenLegacy’s 1.4% mindshare. Additionally, 93% of Amazon Web Services (AWS) users are willing to recommend the solution, compared to 80% of OpenLegacy users who would recommend it.

Amazon API Gateway

Read 45 Amazon API Gateway reviews

12,309 Views
12,309 Comparison Views

93% willing to recommend

OpenLegacy

Read 5 OpenLegacy reviews

2,017 Views
1,311 Comparison Views

80% willing to recommend

Amazon API Gateway

OpenLegacy

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

Amazon API Gateway and OpenLegacy are competing products in API management and integration. Amazon API Gateway has the upper hand in environments using AWS services due to its seamless integration and cloud-native attributes, whereas OpenLegacy is preferred for modernizing legacy systems with robust support.

Features: Amazon API Gateway offers seamless integration with AWS services, exceptional scalability, and advanced security capabilities. OpenLegacy efficiently exposes and modernizes legacy systems, provides flexibility integrating with diverse back-end systems, and effectively reduces the complexity of adapting to legacy architectures.

Room for Improvement: Amazon API Gateway could enhance support for non-AWS environments, improve monitoring tools, and offer more flexible pricing options. OpenLegacy may benefit from optimizing its documentation, strengthening security features for cloud environments, and expanding support for different legacy systems to cover a wider range of technologies.

Ease of Deployment and Customer Service: Amazon API Gateway, being cloud-based, supports streamlined deployment processes with comprehensive AWS integration and documentation. OpenLegacy offers flexible deployment with on-premise and cloud options, prioritizing tailored support for complex legacy integrations and providing practical solutions for hybrid environments.

Pricing and ROI: Amazon API Gateway's pay-as-you-go pricing model supports cost predictability for scalable AWS environments, offering significant ROI for cloud-native applications. OpenLegacy involves higher initial setup costs due to its tailored solutions but yields high ROI in legacy modernization projects, making it invaluable for transforming outdated systems.

To learn more, read our detailed Amazon API Gateway vs. OpenLegacy Report (Updated: June 2026).

Buyer's Guide

Amazon API Gateway vs. OpenLegacy

June 2026

Download the complete report

Helped 904,836 peers since 2012

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

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

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
Product	Mindshare (%)
Amazon API Gateway	9.5%
OpenLegacy	1.4%
Other	89.1%

API Management

Featured Reviews

Subrata Maity

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.

Read full review

reviewer1042905

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.

Read full review

Quotes from Members

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

Pros

"This solution gives you a unified way to have your API accessed."

"The most valuable feature of the solution is that it is a stable solution with an uptime of 99.99 percent."

"The best features of Amazon API Gateway include security and metering, which involves the analytical part of how the APIs are being consumed since it's for consumer APIs built for use by other applications."

"The Lambda features are very cost-effective since you do not have to run your servers 24/7."

"It is easy for integrations if it is deployed in AWS Services."

"It allows us to expose our APIs and provides tools for managing them."

"In terms of the most valuable features, I would say that it is really easy to start working with it."

"It provides the flexibility to configure, switch, and manage configurations through cloud permissions or performance settings."

More Amazon API Gateway pros

"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."

"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 produces a war file which includes everything you need to deploy a Tomcat server."

"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."

"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."

"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."

"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 opens the door to connect modern web products to our old legacy system."

More OpenLegacy pros

Cons

"There are features lacking in API Gateway, such as the timeout settings, which currently are set at 29 seconds."

"The solution should include change data capture (CDC) features that will help reduce workload"

"From a use cases perspective, you need to have an internal and external gateway. AWS can only handle external traffic so has to be used together with another solution."

"We would like to see more UI-based monitoring."

"An interface more friendly for new users would be helpful."

"The course management needs improvement. It's always an issue to set up the course management, especially when you use data form."

"I would say Amazon API Gateway is a bit costly, but considering the feature level, it is very good."

"Currently, I'm not facing any issues with Amazon API Gateway, which satisfies my requirements. 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. What I'd like to see in the next release of Amazon API Gateway is an improvement in the status checks you get from the monitoring feature of the solution. Currently, you get the number of requests received, the number of reports, etc., but if there are more details than what's given by Amazon API Gateway, that will improve the solution."

More Amazon API Gateway cons

"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."

"Debugging and logging for programmers could be better."

"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."

"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'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."

Pricing and Cost Advice

"The product can be described as a medium-priced solution, but its cost is higher than Azure."

"It is somewhat costly, particularly when it introduces server-related features, which are often scheduled on our end."

"The pricing model for API Gateway is advantageous due to its serverless nature, as it depends on traffic volume."

"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."

"AWS charges for data ingress and egress, which could be further reduced. This would be helpful for customers dealing with large amounts of data coming in or going out from their systems."

"Amazon API Gateway has various pricing plans, but I cannot give the exact cost, though I can say that it's expensive. On a scale of one to five, I'd rate the pricing for Amazon API Gateway as two, as the solution is one of the most expensive products in the market for API management."

"There are no licensing fees."

More Amazon API Gateway pricing and cost advice

"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."

See which vendors are best for you

Use our free recommendation engine to learn which API Management solutions are best for your needs.

See recommendations

904,836 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

13%

Manufacturing Company

11%

Computer Software Company

Government

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 Size	Count
Small Business	13
Midsize Enterprise	12
Large Enterprise	21

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...

See all answers

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 ...

See all answers

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 ...

See all answers

Ask a question

Earn 20 points

Comparisons

Microsoft Azure API Management vs Amazon API Gateway

Compared 68% of the time

Apigee vs Amazon API Gateway

Compared 4% of the time

MuleSoft API Manager vs Amazon API Gateway

Compared 3% of the time

WSO2 API Manager vs Amazon API Gateway

Compared 2% of the time

Axway AMPLIFY API Management vs Amazon API Gateway

Compared 2% of the time

More Amazon API Gateway Competitors

IBM DataPower Gateway vs OpenLegacy

Compared 14% of the time

Pipedream vs OpenLegacy

Compared 10% of the time

IBM API Connect vs OpenLegacy

Compared 9% of the time

MuleSoft API Manager vs OpenLegacy

Compared 9% of the time

TIBCO Cloud API Management vs OpenLegacy

Compared 2% of the time

More OpenLegacy Competitors

Product Reports

Buyer's Guide

Amazon API Gateway

July 2026

Download Amazon API Gateway product report

Buyer's Guide

OpenLegacy

June 2026

Download OpenLegacy product report

Overview

Amazon API Gateway stands out for its seamless integration with AWS, ease of use, scalability, and support for secure API management, benefiting from a serverless architecture that helps control costs while ensuring efficient backend connectivity.

Amazon API Gateway offers significant capabilities for managing APIs, integrating smoothly with AWS Lambda for serverless operations. It provides robust security with authentication, authorization, and input validation. The gateway supports API traffic management, rate limiting, and enhances accessibility while facing areas for potential improvements in pricing, documentation, interface usability, monitoring, security, latency, analytics, and debugging tools. Expanded integration features and AI-based development aids are desirable.

What features make Amazon API Gateway effective?

Ease of Use: Provides a straightforward way to set up and manage APIs.
Scalability: Handles growing API demands effectively.
Integration: Seamless connection with AWS services.
Security: Implements authentication and authorization measures.
Serverless Architecture: Manages costs efficiently with AWS Lambda.
Traffic Management: Supports rate limiting and traffic controls.

What benefits should users focus on in reviews?

Cost Management: Reduces expenses with serverless options.
Efficient Connectivity: Rapidly links backend services.
Enhanced Security: Safeguards API interactions.
Flexibility: Supports diverse API configurations.
API Accessibility: Facilitates external service exposure.

Amazon API Gateway is frequently employed in industries like mobile development and public services to ensure secure, efficient interactions between front-end and back-end systems. It's instrumental in managing APIs, integrating microservices, and offering controlled API access, notably in environments requiring robust security and service exposure.

Amazon Web Services (AWS)

OpenLegacy integrates legacy customer data with REST APIs, speeding up mobile transactions and code updates while simplifying API development. Its open-source platform offers flexibility, benefiting mainframe environments and Tomcat server deployments.

OpenLegacy is crucial for organizations aiming to integrate modern web applications with legacy systems. The platform is widely used in financial and logistics sectors to enable quick access to customer data and transactions, effectively monetizing mainframe assets. By facilitating the rapid creation of numerous APIs, OpenLegacy supports seamless interactions between applications, allowing modern web form inputs into legacy systems. Its flexibility and extensive capabilities simplify API development and deployment, proving valuable for those managing day-to-day banking and transaction data. However, room for improvement includes better debugging, logging, SSL integration, flexible pricing options, and support availability, especially for Hogan mainframe users.

What features define OpenLegacy?

REST API Integration: Facilitates integration with mobile transactions.
Faster Code Updates: Delivers efficiency in code changes for mainframe environments.
Open-Source Flexibility: Offers customization and broad capabilities.
Tomcat Deployment: Supports straightforward deployment via Tomcat servers.
Rapid API Development: Enables swift creation of multiple APIs.

What ROI benefits should users expect?

Legacy System Monetization: Transforms mainframe assets into profit.
Improved Integration: Enhances access to critical customer data and transactions.
Efficient Operations: Streamlines daily banking and transaction management.
Cost-Effectiveness: Flexibility and open-source nature reduce expenses.
Enhanced Interoperability: Allows seamless interaction between old and new applications.

Financial and logistics companies leverage OpenLegacy to link web applications with legacy systems, ensuring quick customer data and transaction access. This integration supports rapid solution building and efficient management of banking and transaction data, particularly benefiting institutions like US Bank and Wells Fargo needing comprehensive Hogan mainframe connectors.

OpenLegacy

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...

Buyer's Guide

Amazon API Gateway vs. OpenLegacy

June 2026

Free Report: Amazon API Gateway vs. OpenLegacy

Find out what your peers are saying about Amazon API Gateway vs. OpenLegacy and other solutions. Updated: June 2026.

DOWNLOAD NOW

904,836 professionals have used our research since 2012.

See our Amazon API Gateway vs. OpenLegacy report.

See our list of best API Management vendors.

We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.