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

Apigee 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

Apigee
Ranking in API Management
3rd
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
89
Ranking in other categories
API Testing Tools (10th)
OpenLegacy
Ranking in API Management
34th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (91st)
 

Mindshare comparison

As of April 2026, in the API Management category, the mindshare of Apigee is 7.3%, down from 14.1% compared to the previous year. The mindshare of OpenLegacy is 1.1%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apigee7.3%
OpenLegacy1.1%
Other91.6%
API Management
 

Featured Reviews

IM
consultant at Allstate
Apigee empowers effective API management while needing improvements in technical support
There is room for improvement with Apigee as OPDK private cloud enhancements have stopped, focusing only on Apigee hybrid and Apigee X, with Google no longer adding new features to OPDK private cloud. I am not currently utilizing AI in the private cloud with Apigee, but I'm unsure about hybrid and Apigee X.
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

"We have been able to fulfill all of our use cases with Apigee."
"API/proxy lifecycle workflow for API providers is quite good and one of Apigee's strongest features."
"Technical support is good with everything."
"The ability to convert from language to language using a single tool."
"I would recommend this solution to others who are interested in using it."
"It's a good return on my investment."
"The most valuable feature is the API gateway."
"I use it because it's simple, it automatically updates, and It hasn't given me any issues."
"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."
"Without OpenLegacy, it would take us several months to create the same services."
"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."
"The product has helped our business by allowing us to become more efficient in data handling."
"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."
"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."
 

Cons

"More documentation on the Open Banking Standard will help."
"Apigee has a lot of components, which means that management will be a bit difficult."
"They should improve the monitoring tools for on-premises environments."
"Pricing is an area that can be improved, as it is a little on the higher side."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"Sometimes there are glitches, which means there's still room for improvement in the platform."
"One feature they have to invest time into is the developer portal they use."
"Technical support model for OPDK should be more exposed and mature in terms of providing support during installation, run, and debug of Apigee in production on OPDK mode."
"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."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case."
"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'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."
"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."
"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."
 

Pricing and Cost Advice

"It is a bit on the expensive side. Its licensing cost is a bit high, and that's where we've seen people going back on their decisions."
"It is more expensive when you compare to open-source products or other vendors."
"The prices are comparable."
"The current version of Apigee is not too expensive, but we are currently in talks with Google to understand their roadmap for Apigee X. However, we anticipate that with the introduction of Apigee X, the pricing will likely increase."
"Based on your usage of the APIs you can take a decision to go with either an on-cloud or OPDK version. Get in touch with the sales representatives of Apigee."
"I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited."
"Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive."
"As most of the customers say, the tool is a bit expensive."
"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.
887,041 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
10%
Manufacturing Company
9%
Insurance Company
6%
Construction Company
27%
Comms Service Provider
12%
Financial Services Firm
12%
Insurance Company
11%
 

Company Size

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

Comparisons

 

Overview

 

Sample Customers

Adobe, advance.net, Amadeus, AT&T, Bechtel, Belly, Burberry, Chegg, Citrix, Dell, eBay, Equifax, GameStop, First Data, Globe, HCSC, Intralinks, Kao, Meredith, Mitchell, Orange, Pearson
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 Apigee vs. OpenLegacy and other solutions. Updated: April 2026.
887,041 professionals have used our research since 2012.