Apigee vs OpenLegacy comparison

Read 5 OpenLegacy reviews

477 Views
316 Comparison Views

80% willing to recommend

Apigee

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

Apigee and OpenLegacy are competing API management platforms. Apigee has the upper hand due to its extensive feature set and robust customer support, appealing to enterprises with complex API needs, while OpenLegacy is favored for cost-effectiveness and legacy system integration.

Features: Apigee offers API analytics, developer management, and security features, suitable for enterprises with complex API requirements. OpenLegacy provides specialized integration for legacy systems, aiding in the modernization of outdated infrastructures. Apigee has a comprehensive suite of management tools compared to OpenLegacy's focus on legacy integration.

Room for Improvement: Apigee could improve its pricing to offer more cost-effective solutions for businesses with budget constraints. Another area is simplifying integration to enhance ease of use. Additionally, expanding its legacy system compatibility could attract more businesses. OpenLegacy can enhance its customer support to match Apigee's robust service. Its analytics capabilities might be expanded for better performance tracking, and improving cloud deployment options could increase its appeal.

Ease of Deployment and Customer Service: Apigee offers cloud-based deployment facilitating rapid setup with scalable solutions, benefiting cloud-first enterprises with robust customer service support. OpenLegacy's hybrid deployment model allows organizations to use existing on-premises investments with cloud capabilities, highlighting its flexibility.

Pricing and ROI: Apigee's setup costs are higher due to a comprehensive feature set, providing substantial ROI through operational efficiency and extensive support. OpenLegacy offers a cost-effective initial setup, ensuring excellent ROI for companies focused on modernizing legacy systems within budget constraints.

To learn more, read our detailed Apigee vs. OpenLegacy Report (Updated: January 2025).

Apigee vs. OpenLegacy

Download the complete report

Helped 831,265 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

Apigee

Ranking in API Management

2nd

Average Rating

8.2

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

API Testing Tools (6th)

OpenLegacy

Ranking in API Management

34th

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of January 2025, in the API Management category, the mindshare of Apigee is 15.0%, up from 15.1% compared to the previous year. The mindshare of OpenLegacy is 0.2%, down from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.

API Management

Featured Reviews

ShawkyFoda

Senior Consultant at Goverment

Provides high visibility and control with good traffic monitoring

Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability. The replication process between Master and Slave for disaster recovery takes too long. Dependencies on analytics impact the performance of the user interface, which should be separate. The complex setup process on-premises, especially with multi-node installations, could also be improved. Additional control in product declarations, based on operations like POST and GET, is needed.

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

"A simple platform that's easier to work with than IBM API Connect. Support for it is really good and gives it advantage over other providers."

"I have found the most valuable features to be tracing a proxy, and managing proxy versions and revisions via the Edge UI component."

"Anyone with basic knowledge can build an API."

"It's stable."

"I use it because it's simple, it automatically updates, and It hasn't given me any issues."

"Apigee is very easy to use, and you can code in any language."

"The stability of the solution is good. There aren't issues surrounding bugs or glitches. We don't find that it crashes or freezes. It's pretty reliable."

"Tracing in Apigee is a very good feature."

More Apigee pros

"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."

"Opens the door to connect modern web products to an old legacy system."

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

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

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

"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 mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."

Cons

"Apigee could do more to make users aware of what is available in the add-ons."

"I would like to see better integration and some architectural improvements in future releases of the solution."

"The setup and installation process could be improved with a container-based system."

"We are experiencing some performance issues."

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

"Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud."

"We do not have control over the installation."

"When there is an update on a new version or an automatic update, you have to be present and double-check that the update is reflected in the environment with no issues."

More Apigee cons

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

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

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

"The prices are comparable."

"The solution is a bit expensive. It's not for organizations in the early stages of their lifecycle but is more suited for mid- to enterprise-level platforms. Pricing varies by deployment model, with SaaS being the cheapest, costing around $100,000 per year for a subscription. For hybrid and on-prem deployments, the price increases. The on-prem model includes a license and additional installation and configuration professional service costs, which can be at least $40,000 to $60,000 for the initial setup. While it's not cheap, it offers long-term value and can be worthwhile."

"Its price is reasonable for the features they provide and the maturity of the platform."

"Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive."

"It is an expensive solution."

"The cost of the licensing is based on the number of API calls that are made."

"The cost increases as the usage increases."

"We have a contract for three years. I don't know the cost."

More Apigee 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

831,265 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

22%

Computer Software Company

12%

Manufacturing Company

Insurance Company

Financial Services Firm

33%

Computer Software Company

12%

Insurance Company

11%

Real Estate/Law Firm

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

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

See all answers

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

What do you like most about Apigee?

We can customize the dashboard.

See all answers

Ask a question

Earn 20 points

Comparisons

Microsoft Azure API Management vs Apigee

Compared 33% of the time

IBM API Connect vs Apigee

Compared 9% of the time

WSO2 API Manager vs Apigee

Compared 8% of the time

Layer7 API Management vs Apigee

Compared 7% of the time

Amazon API Gateway vs Apigee

Compared 6% of the time

More Apigee Competitors

Kong Gateway Enterprise vs OpenLegacy

Compared 44% of the time

MuleSoft API Manager vs OpenLegacy

Compared 22% of the time

IBM API Connect vs OpenLegacy

Compared 19% of the time

webMethods.io vs OpenLegacy

Compared 15% of the time

More OpenLegacy Competitors

Product Reports

Apigee

Download Apigee product report

Download OpenLegacy product report

Learn More

Google

Overview

Apigee is a platform for developing and managing APIs. Apigee offers an interface for your core services by wrapping them with a proxy layer which is then accessed by other developers. With Apigee, you can design and build APIs and then securely share their services and data without exposing any code.

Because app developers make HTTP requests to an API proxy rather than directly to your services, your services are separated from the developers. All the developer needs to know is the URL of the API proxy endpoint, necessary query parameters, authorization credentials (if they exist), and the response data format.

The API proxy isolates the app developer from your backend service. Therefore, you are free to change the service implementation if the public API remains consistent. By maintaining a consistent frontend API, existing client apps will continue to work regardless of changes on the backend.

Key capabilities of the Apigee API management platform include:

Security: Protect APIs, messages, and backends with configurable policies such as OAuth, API key verification, XML/JSON threat protection, and access control.
API gateway: Secure and mediate the traffic between clients and backends, and between a company’s APIs and the developers who use the APIs.
Developer portal: Attract and engage application developers, enabling them to discover, explore, purchase, and test APIs and register to access and use the APIs.
API console: The console helps developers learn and work with APIs.
API lifecycle management: Manage the process of designing, developing, publishing, deploying, and versioning APIs.
Automated documentation: Automate the development of API documentation and software development kits.
Machine learning: Utilize machine learning and analytics to generate actionable insights and reports.

API monitoring: Apigee offers monitoring tools for API troubleshooting, security, and optimization.

Reviews from Real Users:

Apigee stands out among its competitors for a number of reasons. Several major ones are its rich developer portal, its advanced analytics, and its central monitoring system.

Carlos R., a software architect at Caja Los Andes writes, “The central monitoring feature is the most valuable. It also provides security for the APIs and high availability for our use cases. Apigee is the best product in the industry in comparison to other API management solutions. It helps in fast development, which is a top point. It also supports a lot of industry standards and has excellent documentation.”

An associate vice president at a tech services company notes, “The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features. The authentication mechanisms are quite easily built into Apigee, which is something that most of the other products have also now started supporting.”

OpenLegacy helps organizations quickly launch innovative digital services by extending their core back-end systems to the web, mobile and cloud in days or weeks versus months. Our microservice-enabled API integration and management software quickly reduces project backlog by automating and accelerating microservices and API creation, deployment, testing and management from core applications, mainframes and databases. Together, business and IT teams can quickly, easily and securely meet consumer, partner or employee demands for digital services without modernizing or replacing core systems, and without special programming skills or invasive changes to existing systems and architectures. OpenLegacy is designed for ongoing management of microservices APIs and is based on open standards, so our software plays nice with your current technology stack and supports agile, DevOps and continuous development. Learn why leading companies choose OpenLegacy at www.openlegacy.com.

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

Apigee vs. OpenLegacy