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

Apollo GraphOS vs Layer7 API Management comparison

 

Comparison Buyer's Guide

Executive Summary

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

Apollo GraphOS
Ranking in API Management
29th
Average Rating
7.4
Reviews Sentiment
3.7
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Layer7 API Management
Ranking in API Management
16th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
112
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.7%, up from 0.3% compared to the previous year. The mindshare of Layer7 API Management is 1.9%, down from 2.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Layer7 API Management1.9%
Apollo GraphOS0.7%
Other97.4%
API Management
 

Featured Reviews

NA
Artificial Intelligence Consultant at Medallion Technologies
Access data seamlessly with robust community support without current improvement needs
So far, I could say that Apollo GraphOS is quite comprehensive, there’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API. More granular access control and role-based visibility within the platform would help enterprise teams better manage who can change what. Enhanced support for real-time use cases (e.g., subscriptions at scale) could also take it to the next level and give a better developer experience These might also be beneficial to have a more in-depth analytics around client usage and field-level insights to drive better decisions around deprecation or optimization.
Integration capabilities excel and support for varied platforms enhances communication across backend systems
We mainly use REST APIs, and the solution's integration capabilities are excellent. It allows communication with a number of back-end providers and data consolidation. The flexibility to develop APIs for various platforms, from front-end applications to ATM machines, is valuable. Code changes and migration are straightforward, and it supports identity and access management integration.

Quotes from Members

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

Pros

"Apollo GraphOS has significantly enhanced both the developer experience and product delivery timelines by offering a centralized approach to managing GraphQL schemas and services, helping reduce overhead and improve collaboration between frontend and backend teams."
"Apollo GraphOS has positively impacted our organization by reducing unwanted code and helping us combine multiple services."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"Every API that we get from external or from internal goes through this layer first, and it should not be a bottleneck. That was the problem we had before. Now it's no longer a bottleneck. It's more like a throughput, this process is less than 10 milliseconds for any particular API."
"The main difference was AWS and Apigee to this solution is they have a lower price but they do not have all the features that this solution has."
"It's pretty easy to use, and once we have templating set up we can add new APIs, at least through the gateway, and apply the security to them; it takes a minute."
"The product, by itself, is great, and the flexibility that CA has given us out of this product is really great."
"The Mobile API Gateway is also great."
"Compared to other tools, like Apigee, this is the best tool that I have used."
"It is flexible in how it creates custom policies and uses builds with impressive methods."
"Because of the efficiency of the product actually doing that, pulling data from disparate sources, and integrating it into the response format that I want, that my customer demands, that's so easy."
 

Cons

"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage. It sometimes takes longer than three seconds, which can affect loading times and lead to user dissatisfaction. I would like to see improved performance."
"As well as the SOA Gateway - that is, the API Gateway; we call it the SOA Gateway - we also are now deploying the developer portal component of the SOA Gateway. That has limitations."
"Some of the things that we see as room of improvement are how do you integrate with other systems out there."
"The interface should be improved."
"There are old algorithms that the tool does not support - and it shouldn't, in my opinion. But sometimes customers need old algorithms, from old use cases and old applications, migrated to the platform. At those times, there are hiccups that happen."
"The current version of it is not at the level of the functionality of the previous 3.5 version. That's quite a problem for us because we expected some functions in the Portal which are currently not available."
"The only issue we have is that we have to buy an APM license separately for end-to-end monitoring."
"Broadcom's push for upgrades from version nine to ten, ten to 10.3, and onwards to twelve needs improvement in migration processes, especially with service dependencies."
"In my opinion, the policies need to be simplified so that developers are able to understand and taking that into consideration they can build their APIs."
 

Pricing and Cost Advice

Information not available
"If the CA pricing for API management would be a little lower, they would be able to cover a broader market."
"I think it's competitive. It's not that expensive when you compare CA with the Oracle product."
"Do not buy piecemeal."
"APIs can be developed to provide security. We can show them in one single pane of glass, such as the CA API Management API Developer Portal. It is there that we can provide the monetization for their APIs and what is happening on third-party applications, like Paytm or BookMyShow."
"I feel that it is costly for medium-sized companies."
"Keep in mind the non-product licensing, e.g., if you opt not to use the embedded SQL."
"Pricing is competitive. CA is ready to offer attractive discounts."
"The price of Layer7 API Management is too high and should be reduced. However, it is a good solution in the market."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
University
13%
Manufacturing Company
11%
Construction Company
6%
Financial Services Firm
14%
Construction Company
14%
Marketing Services Firm
7%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise13
Large Enterprise84
 

Questions from the Community

What is your experience regarding pricing and costs for Apollo GraphOS?
I am not sensitive to nor very knowledgeable about the pricing and setup cost.
What needs improvement with Apollo GraphOS?
Apollo GraphOS is a strong platform, but there are a few areas where it could improve. The onboarding experience could be simpler for teams that are new to GraphQL. There are many powerful capabili...
What is your primary use case for Apollo GraphOS?
My main use case for Apollo GraphOS is managing and monitoring GraphQL APIs across multiple services. From a quality engineering perspective, I use it to understand schema changes, identify potenti...
What is your experience regarding pricing and costs for Layer7 API Management?
Pricing is more than average. While I am used to Layer7 API Management ( /products/layer7-api-management-reviews ), seeing other products makes the tool's pricing seem high.
What needs improvement with Layer7 API Management?
Broadcom's push for upgrades from version nine to ten, ten to 10.3, and onwards to twelve needs improvement in migration processes, especially with service dependencies. The migration path sometime...
What is your primary use case for Layer7 API Management?
I am not the client. I implement Layer7 API Management ( /products/layer7-api-management-reviews ) for the clients. I have worked on multiple projects as a developer, implementing for Hydro Tasmani...
 

Also Known As

No data available
CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway
 

Overview

 

Sample Customers

Information Not Available
1. IBM  2. Microsoft  3. Oracle  4. Salesforce  5. SAP  6. Cisco  7. Dell  8. HP  9. Adobe  10. VMware  11. Accenture  12. Capgemini  13. Deloitte  14. PwC  15. Ernst & Young  16. Infosys  17. TCS (Tata Consultancy Services)  18. Wipro  19. Cognizant  20. HCL Technologies  21. Tech Mahindra  22. Fujitsu  23. Hitachi  24. NEC  25. NTT Data  26. Ericsson  27. Nokia  28. Siemens  29. AT&T  30. Verizon  31. Vodafone  32. Orange
Find out what your peers are saying about Apollo GraphOS vs. Layer7 API Management and other solutions. Updated: June 2026.
902,988 professionals have used our research since 2012.