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

Apollo GraphOS vs Informatica Intelligent Data Management Cloud (IDMC) comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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
19th
Average Rating
7.6
Reviews Sentiment
4.4
Number of Reviews
7
Ranking in other categories
No ranking in other categories
Informatica Intelligent Dat...
Ranking in API Management
5th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
215
Ranking in other categories
Data Integration (1st), Data Quality (1st), Business Process Management (BPM) (6th), Business-to-Business Middleware (1st), Cloud Data Integration (3rd), Data Governance (3rd), Test Data Management (2nd), Cloud Master Data Management (MDM) (1st), Data Management Platforms (DMP) (2nd), Data Masking (2nd), Metadata Management (2nd), Integration Platform as a Service (iPaaS) (3rd), Test Data Management Services (3rd), Product Information Management (PIM) (1st), Data Observability (2nd), AI Data Analysis (1st)
 

Mindshare comparison

As of September 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.8%, up from 0.4% compared to the previous year. The mindshare of Informatica Intelligent Data Management Cloud (IDMC) is 1.6%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Informatica Intelligent Data Management Cloud (IDMC)1.6%
Apollo GraphOS0.8%
Other97.6%
API Management
 

Featured Reviews

MB
Business Development Manager at Digitaltrack
Unified schemas have streamlined team collaboration and have reduced API-related deployment issues
We had a positive experience with Apollo GraphOS, but there are a few areas where I think it could be improved. One area is the learning curve around GraphQL Federation and schema governance. Teams that are new to federated architectures often need to understand best practices. More guided onboarding, built-in recommendations, and practical examples would make adoption easier. I also think the observability and troubleshooting experience could be enhanced, particularly when diagnosing issues that span multiple subgraphs. While the platform provides useful insights, tracing complex requests across a federated environment can still require additional investigations. Another improvement would be more granular administrative controls and reporting, especially for larger organizations where different teams manage different parts of the GraphQL platform. Although the CI/CD integration is one of the product's strengths, having more out-of-the-box integrations and similar configurations for popular DevOps tools would reduce the initial setup effort. These suggestions would make the platform easier to adopt, operate, and scale, particularly for organizations that are beginning their GraphQL Federation journey. One thing I would like to see in future releases is deeper operational visibility for large-scale federated environments. As the number of subgraphs and development teams grows, it becomes more important to quickly identify where performance bottlenecks or schema-related issues are originating without having to correlate information from multiple tools. More built-in governance capabilities would be valuable, such as stronger policy enforcement, approval workflows for schema changes, and richer reporting for platform administrators. Another area that could be improved is the onboarding experience. While the documentation is comprehensive, having more guided setup wizards, architectures, and real-world implementation examples would help new teams become productive more quickly. I would also like to see even broader integrations with common enterprise monitoring, security, and development platforms so organizations can manage Apollo GraphOS as part of their existing operational ecosystem rather than relying on additional customization. These points would make day-to-day administration easier and improve the experience for organizations running GraphQL at a larger scale.
RC
Contractor at Sanlam
Cloud data catalog has streamlined lineage and quality while leaving more automation to improve
I have not explored IDMC's automation capabilities driven by AI and metadata too much at the moment, but it is on the cards. We are basically creating the foundation, as the whole migration has taken place recently and it is still early days. I think Informatica Intelligent Data Management Cloud (IDMC) is evolving, and as the vendors move forward, they pick up new concepts from each other. I have seen that products leapfrog each other, and from my experience over the years, the big players tend to copy features or add enhancements based on industry trends. I feel whatever the tool does not have now, there is a feedback loop allowing us to request new features, and we continually ask for different ways to do things as we have a pipeline into the product management team. It is difficult to say what additional features I would prefer to see in the next release of IDMC. I would appreciate more automation on the lineage front, with more AI to seamlessly join independent sources and create seamless lineage between different technologies, such as from file into database A into a different database and landing up in a reporting system such as Cognos, Qlik, Qlik Sense, QlikView, or Power BI.

Quotes from Members

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

Pros

"Apollo GraphOS positively impacts my organization by providing a complete platform for API orchestration, schema governance, observability, and federation."
"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."
"Apollo GraphOS has had a positive impact on our organization by making our API development process more structured, predictable, and collaborative."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
"Apollo GraphOS has had a positive impact by improving the way we manage and evolve our GraphQL APIs."
"Overall, Apollo GraphOS has been a valuable asset."
"The product is scalable and excellent for enterprise-level organizations."
"The most valuable feature of Informatica Enterprise Data Catalog is it provides clients with a full view of the enterprise data assets. For example, how many data assets they have and who owns them."
"The user-friendliness and performance of Informatica is quite impressive."
"The metadata management of Informatica is great."
"Performance and flexibility-wise, they're very user-friendly."
"Informatica comes with a predefined data model which is the way in which you enrich your products, acting not only as master data but also as a product enrichment tool, providing flexibility with an undefined number of attributes that define a product and the ability to plug it in with any e-commerce website."
"I rate the solution's scalability a ten out of ten."
"The most valuable features of Informatica MDM are it is cloud-enabled and has all the elements that are supposed to have in terms of MDM as a solution. All the features that are there. It is very well-integrated with any of the SAP and non-SAP applications. It is quite user-friendly. The user experience that you receive in Informatica MDM is quite good."
 

Cons

"I rated it six out of ten because while it offers useful capabilities such as schema management, schema validation, and API observability, I feel there are several areas that need improvement."
"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."
"Apollo GraphOS could be improved with simpler pricing, more transparent usage and cost reporting, easier onboarding for new teams and learners, and more detailed documentation and troubleshooting guidance for complex GraphQL."
"The reason I held back from giving it a perfect score is that some enterprise scenarios still require additional effort."
"I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, making the platform seem more complex than necessary for smaller teams."
"For products Master Data Management or related to MDM or Data Governance, there is no way by which we can directly practice, and my team struggles at that point."
"We would like to have accessibility to the repository."
"The one thing that I think could be improved is connectivity with the Salesforce because if you're loading a huge amount of data, whatever optimization is carried out, takes some time and it could be a little faster."
"In general, it is good. We used to face some Java application problems, approximately two issues a month."
"The initial setup is very, very difficult."
"The main issue preventing Brazilian companies from migrating to Informatica Cloud Data Integration from on-prem is the price."
"User/group administration could use improvement."
"If I compare it with other MDM solutions in the market, one thing that can definitely be improved is automation to help with the configuration. Currently, when we are creating any staging of base object tables, all the columns have to be configured manually in the Informatica Hub Console. A lot of tables and different kinds of business columns have to be configured manually. There should be an automated process for this, especially in the Dev environment. When people are creating tables and columns from scratch, if there is a backend automated process for that, it would be really helpful. In Stibo, a similar feature is there wherein you can tag attributes to certain objects. It would be helpful if Informatica also provides a similar option. It would reduce the manual effort. It could be that such a feature is already there, but I am not aware of it."
 

Pricing and Cost Advice

Information not available
"We have licenses, and we are provided with certain particular services in the solution."
"We got a 50% discount."
"Informatica is very expensive."
"I rate the licensing cost of Informatica MDM a five out of ten."
"Informatica MDM's pricing is not cheap but comparable to other vendors."
"Informatica MDM's price could be lower."
"Pricing is determined by the number of licensed users as well as the number of Core CPUs."
"I rate the product's pricing a five on a scale of one to ten, where one is cheap and ten is expensive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
12%
University
10%
Program Development Consultancy
10%
Financial Services Firm
10%
Financial Services Firm
12%
Manufacturing Company
10%
Outsourcing Company
9%
Construction Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise3
By reviewers
Company SizeCount
Small Business51
Midsize Enterprise27
Large Enterprise155
 

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?
I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, ma...
What is your primary use case for Apollo GraphOS?
My main use case for Apollo GraphOS is creating APIs with GraphQL. I create subgraphs and schema composition, contracts, schema registry, and change validation, which helps me prevent breaking chan...
How does Azure Data Factory compare with Informatica Cloud Data Integration?
Azure Data Factory is a solid product offering many transformation functions; It has pre-load and post-load transformations, allowing users to apply transformations either in code by using Power Q...
Which Informatica product would you choose - PowerCenter or Cloud Data Integration?
Complex transformations can easily be achieved using PowerCenter, which has all the features and tools to establish a real data governance strategy. Additionally, PowerCenter is able to manage huge...
What are the biggest benefits of using Informatica Cloud Data Integration?
When it comes to cloud data integration, this solution can provide you with multiple benefits, including: Overhead reduction by integrating data on any cloud in various ways Effective integration ...
 

Also Known As

No data available
ActiveVOS, Active Endpoints, Address Verification, Persistent Data Masking
 

Overview

 

Sample Customers

Information Not Available
The Travel Company, Carbonite
Find out what your peers are saying about Apollo GraphOS vs. Informatica Intelligent Data Management Cloud (IDMC) and other solutions. Updated: September 2026.
913,683 professionals have used our research since 2012.