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
30th
Average Rating
7.4
Reviews Sentiment
3.5
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Layer7 API Management
Ranking in API Management
15th
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 May 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.7%, up from 0.2% compared to the previous year. The mindshare of Layer7 API Management is 2.0%, down from 2.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Layer7 API Management2.0%
Apollo GraphOS0.7%
Other97.3%
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 positively impacted our organization by reducing unwanted code and helping us combine multiple services."
"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."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"We are able to go to market and deploy our functionalities very quickly, and we are able to embrace newer security standards easier because of CA API management."
"CA API Gateway provides rich policy sets in regards to XML and REST services, is great for all B2B integrations, and is a very agile component to set up and use."
"I would certainly recommend using this product."
"It's absolutely the best security product in the market from a gateway perspective."
"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."
"Finally, based on all the features, like security, we decided that the CA product is the best suited to the needs of Motorola's business."
"The solution helped us to quickly publish and monetize APIs. I have used versioning responses to publish or send APIs to different customers with different versions."
"We can get more visibility into our data."
 

Cons

"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage."
"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."
"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"One specific feature that we need is the ability to authenticate directly to the server with API data. It's not complex nowadays. This is a feature that we need and CA doesn't have it."
"we cannot add gateways on the fly because there are a lot of moving parts; endpoint connectivity is one of them. If we add more nodes then the rate-limiting feature is affected. This kind of gateway always has the scalability issue. But, I think CA is coming up with its Microgateway, which is in Beta. If they stabilize their Microgateway platform, we could do very well in terms of scalability."
"The API Development tool can be made more user-friendly by providing folder properties."
"The security protocols in CA's product, for financial services, weren't as good as those in API Connect."
"The development toolkit used for creating APIs should be more online and user-friendly. Deployment and tracking could also be improved. Tools like Apigee provide a complete online experience along with RESTful APIs, to manage all activities. It is a very nice and user-friendly solution compared to CA."
"One of the reasons that we chose to go with another tool was because we found that CA API Management was crashing quite often."
"They are getting there. Docker-based containers are there now, but it is not completed, I think."
"Debugging seems a little bit archaic by modern standards. I would like to see better documentation for the development language itself."
 

Pricing and Cost Advice

Information not available
"It's my manager who takes care of the pricing. But I keep on hearing that it's a little pricey, it's on the higher side. That is what he says."
"If you do a TCO of more than five years, then you will see a big jump in costs for some vendors."
"Pricing is competitive. CA is ready to offer attractive discounts."
"For what we are after, the pricing is okay. It is competitive."
"It has a reasonable pricing model by instance."
"CA has great pricing for gateways, so negotiate with your sales team."
"Purchase 4.0 now and wait until they flush out the 4.1 problems."
"Be aware of additional licenses for your warm standby. Ensure you get plenty of non-production licenses."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
University
13%
Manufacturing Company
8%
Construction Company
7%
Financial Services Firm
13%
Construction Company
8%
Marketing Services Firm
7%
Healthcare 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?
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 overla...
What is your primary use case for Apollo GraphOS?
I’ve been using Apollo GraphOS across several mobile and web projects. On the mobile side, I’ve integrated it with React Native and Flutter. For web applications, the usage has been primarily withi...
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: April 2026.
894,738 professionals have used our research since 2012.