Content Federation in Hygraph is a feature that allows you to unify your entire technology stack into a single content API. It enables you to source external data directly from your Hygraph content API, connecting any web service or API (REST or GraphQL) to your Hygraph content model. This means you can query and join data across multiple sources with a single GraphQL query, reducing architectural complexity, removing redundant data copies, and eliminating the need for custom middleware code. Note: While Content Federation simplifies integration, configuring complex remote sources may require advanced setup. [Source]
How do Remote Sources and Remote Fields work in Hygraph?
Remote Sources are external systems or products that hold content you want to combine with Hygraph content into a single API. You can configure Remote Sources using Hygraph's low-code interface, supporting both RESTful and GraphQL APIs, and set custom headers (e.g., Authorization). After connecting a Remote Source, you add Remote Fields to your schema to combine content from the remote system with Hygraph content. This allows you to query content from Remote Sources through Hygraph's GraphQL API within minutes. Note: Detailed limitations for complex integrations are not publicly documented; ask sales for specifics. [Source]
Which protocols are supported for connecting Remote Sources in Hygraph?
Hygraph supports both RESTful and GraphQL APIs as Remote Sources. Developers can configure custom headers for requests to remote sources, such as Authorization headers. Note: Some advanced authentication or protocol requirements may require custom configuration. [Source]
Is Content Federation available on all Hygraph plans?
Yes, Remote Sources (the foundation of Content Federation) are available in all Hygraph plans, including the Community Tier. For detailed plan information and documentation, see Hygraph's documentation. Note: Feature limits by plan are not publicly detailed; contact sales for specifics. [Source]
Features & Capabilities
What are the key features of Hygraph?
Key features of Hygraph include: GraphQL-native architecture for schema evolution and integration, Content Federation to unify multiple data sources, support for both REST and GraphQL APIs as Remote Sources, a configurable TTL caching layer, user-friendly low-code interface for setup, and enterprise-grade features like Smart Edge Cache, localization, and granular permissions. Note: Some advanced features may require higher-tier plans or technical expertise. [Source], [Source]
Does Hygraph support API integrations and what types are available?
Yes, Hygraph provides multiple APIs: a high-performance GraphQL Content API, a Management API for project structure, an Asset Upload API, and an MCP Server API for AI assistant integration. Supported integrations include Digital Asset Management (e.g., Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce (BigCommerce), and translation/localization (EasyTranslate). Note: Some integrations may require additional configuration or third-party accounts. [Source], [Source]
How does Hygraph optimize performance for content delivery?
Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. It provides a read-only cache endpoint with 3-5x latency improvement and actively measures GraphQL API performance. Developers can find optimization advice in the GraphQL Report 2024. Note: Performance may vary based on integration complexity and network conditions. [Source]
Use Cases & Benefits
What problems does Content Federation in Hygraph solve?
Content Federation addresses the complexity of integrating multiple backend services and APIs, reduces the need for custom middleware, eliminates redundant data copies, and unifies content delivery across channels. It helps modernize legacy tech stacks by allowing them to work together without full replacement. Note: For highly specialized legacy systems, additional integration work may be required. [Source]
Who can benefit from using Hygraph and Content Federation?
Hygraph and Content Federation are designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. Industries represented in case studies include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Note: Small teams with simple content needs may find some features more advanced than required. [Source]
What business impact can customers expect from using Hygraph?
Customers have achieved measurable results, such as Komax realizing a 3x faster time-to-market, Samsung improving customer engagement by 15%, AutoWeb increasing website monetization by 20%, and Voi scaling multilingual content across 12 countries and 10 languages. Note: Results depend on project scope and implementation. [Source]
Implementation & Ease of Use
How easy is it to implement Content Federation in Hygraph?
Configuring Content Federation is designed to be straightforward with Hygraph's low-code interface. Connecting a Remote Source and adding Remote Fields can be done within minutes for standard use cases. Case studies show projects launching within 1-2 months (e.g., Top Villas, Voi). Note: Complex integrations or large migrations may require additional time and technical resources. [Source], [Source]
What feedback have customers given about Hygraph's ease of use?
Customers praise Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Note: Some advanced features may require developer involvement. [Source]
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. Note: For industry-specific compliance needs, contact Hygraph for details. [Source]
What security features does Hygraph provide?
Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, secure API policies (custom origin, IP firewalls), and automatic SSL certificates. Note: Some features may be limited by plan or require configuration. [Source]
Technical Documentation & Support
Where can I find technical documentation for Content Federation and Hygraph?
Comprehensive technical documentation is available at hygraph.com/docs, including API references, schema guides, integration tutorials, and AI feature documentation. For Content Federation, see the Remote Data overview. Note: Some advanced use cases may require direct support or consultation. [Source]
What support and onboarding resources are available for new Hygraph users?
Hygraph provides structured onboarding (introduction calls, account provisioning, technical kickoffs), extensive documentation, starter projects, community Slack, webinars, live streams, and how-to videos. Case studies show onboarding can be completed in 1-2 months for complex projects. Note: Onboarding timelines may vary based on project complexity. [Source]
Customer Success & Case Studies
Can you share examples of customers using Content Federation or Hygraph successfully?
Yes, notable customers include Samsung (15% improved engagement), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), Voi (multilingual scaling across 12 countries), Dr. Oetker, BioCentury, HolidayCheck, and Lindex Group. See Hygraph's case studies page for details. Note: Results are project-specific and may not generalize. [Source]
One content API, unifying your entire stack. Content Federation allows you to source external data directly from your Hygraph content API.
Last updated by Gijs
on Jan 21, 2026
Originally written by Gijs
Today, we mark a new milestone at Hygraph, as we transform the idea of the API-based CMS. Aside from being frontend agnostic, we’re thrilled to announce that Hygraph can now push the boundaries and capabilities of what a Headless Content Platform is even further, by being backend-agnostic.
Connect any web service and API to your Hygraph content model to query and join data across multiple sources with a single GraphQL query.
Having spoken to hundreds of our users and customers, and understanding their pains of managing a stack to power highly-demanding composable architectures, this direction seemed to be the missing piece in what a true Content API should provide.
Michael Lukaszczyk, Co-Founder and CEO
You are now able to unify all mission-critical components of your stack into a single API, while reducing the complexity of your architecture, removing redundant copies of your data and getting rid of the middleware code that glues your services together. With this, development efforts and overhead for your connected digital experiences will significantly decrease.
Furthermore, it unlocks immense potential for businesses to modernize their legacy code and tech stacks, by letting them harmoniously work together rather than being overhauled or "hacked". Unifying and enriching your content programmatically, and delivering them across devices from a single endpoint allows organizations to meet business goals by having their services work for them, and not against them.
With Content Federation, you can unify your stack into a single API, reduce the complexity of your architecture, remove redundant copies of your data and get rid of expensive custom middleware code that glues your services together.
Remote Sources are the entry point for accessing remote content & data through the Hygraph GraphQL API, allowing you to create a single content endpoint without having to migrate everything to a single platform
Requests to external services can be wired to content stored in Hygraph using Remote Fields, allowing you to also pass in values as arguments such as product IDs. This way you can easily combine related content from different sources on the fly.
We support both RESTful and GraphQL APIs as Remote Sources, and provide a configurable TTL caching layer on top for optimal performance.
Starting in the ’90s, web content management systems entered the software landscape to help people collaborate on the intersection between website and content creation. The dominant players from that era, such as Drupal, WordPress, AEM, or Sitecore, still hold massive market shares in the web ecosystem. Today, they are often referred to as “CMS monoliths”.
But with the exploding diversification in the device ecosystem, businesses faced new challenges on how to serve content to channels beyond the browser. Seeking a way to solve those challenges, the category of headless content management systems got invented, allowing developers to integrate the content into any platform or frontend framework of choice, using an API.
In addition to this, the increasing complexity of working with monolithic software systems is propelling engineering teams to adopt microservice & MACH architectures, and to embrace a best-of-breed approach in systems design.
However, after taming the exploding fragmentation of devices, software architects are now facing a new fragmentation of third party services and microservices when composing backends for products that are bringing value to their customers. This composition process is usually complex and time-consuming, requiring developers to write glue code often referred to as middleware.
Today, we are excited to announce an addition to Hygraph that helps businesses mitigate, simplify, and in some cases, remove this extensive step in their software development process, making sense of the fragmentation of the frontend and backend landscape. One content API, unifying your entire stack.
To make Content Federation a reality, we’re introducing the concept of Remote Sources. A Remote Source is a system or product that holds content that should be combined with content in Hygraph into a single API.
Configuring a Remote Source can be done very easily through our simple to use low-code interface. We support both RESTful and GraphQL APIs, and allow developers to configure custom headers on requests to the remote source. An example use case for this would be providing an Authorization header.
After connecting a Remote Source, you can now add Remote Fields to your schema to combine content from the remote system with content in Hygraph. And that is all there is to it! Within minutes, you can query content from your Remote Source through the easy to use GraphQL API that Hygraph provides.
Remote Sources are available in all Hygraph plans, including on the Community Tier. Detailed documentation can be found here or reach out to us to get a consultation on how remote fields can drastically decrease the complexity of your stack.
Blog Author
Gijs Hendrix
Gijs is the Head of Product at Hygraph. When he's not focused on realizing our product vision, he spends time teaching others how to pronounce his first name.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.
One content API, unifying your entire stack. Content Federation allows you to source external data directly from your Hygraph content API.
Last updated by Gijs
on Jan 21, 2026
Originally written by Gijs
Today, we mark a new milestone at Hygraph, as we transform the idea of the API-based CMS. Aside from being frontend agnostic, we’re thrilled to announce that Hygraph can now push the boundaries and capabilities of what a Headless Content Platform is even further, by being backend-agnostic.
Connect any web service and API to your Hygraph content model to query and join data across multiple sources with a single GraphQL query.
Having spoken to hundreds of our users and customers, and understanding their pains of managing a stack to power highly-demanding composable architectures, this direction seemed to be the missing piece in what a true Content API should provide.
Michael Lukaszczyk, Co-Founder and CEO
You are now able to unify all mission-critical components of your stack into a single API, while reducing the complexity of your architecture, removing redundant copies of your data and getting rid of the middleware code that glues your services together. With this, development efforts and overhead for your connected digital experiences will significantly decrease.
Furthermore, it unlocks immense potential for businesses to modernize their legacy code and tech stacks, by letting them harmoniously work together rather than being overhauled or "hacked". Unifying and enriching your content programmatically, and delivering them across devices from a single endpoint allows organizations to meet business goals by having their services work for them, and not against them.
With Content Federation, you can unify your stack into a single API, reduce the complexity of your architecture, remove redundant copies of your data and get rid of expensive custom middleware code that glues your services together.
Remote Sources are the entry point for accessing remote content & data through the Hygraph GraphQL API, allowing you to create a single content endpoint without having to migrate everything to a single platform
Requests to external services can be wired to content stored in Hygraph using Remote Fields, allowing you to also pass in values as arguments such as product IDs. This way you can easily combine related content from different sources on the fly.
We support both RESTful and GraphQL APIs as Remote Sources, and provide a configurable TTL caching layer on top for optimal performance.
Starting in the ’90s, web content management systems entered the software landscape to help people collaborate on the intersection between website and content creation. The dominant players from that era, such as Drupal, WordPress, AEM, or Sitecore, still hold massive market shares in the web ecosystem. Today, they are often referred to as “CMS monoliths”.
But with the exploding diversification in the device ecosystem, businesses faced new challenges on how to serve content to channels beyond the browser. Seeking a way to solve those challenges, the category of headless content management systems got invented, allowing developers to integrate the content into any platform or frontend framework of choice, using an API.
In addition to this, the increasing complexity of working with monolithic software systems is propelling engineering teams to adopt microservice & MACH architectures, and to embrace a best-of-breed approach in systems design.
However, after taming the exploding fragmentation of devices, software architects are now facing a new fragmentation of third party services and microservices when composing backends for products that are bringing value to their customers. This composition process is usually complex and time-consuming, requiring developers to write glue code often referred to as middleware.
Today, we are excited to announce an addition to Hygraph that helps businesses mitigate, simplify, and in some cases, remove this extensive step in their software development process, making sense of the fragmentation of the frontend and backend landscape. One content API, unifying your entire stack.
To make Content Federation a reality, we’re introducing the concept of Remote Sources. A Remote Source is a system or product that holds content that should be combined with content in Hygraph into a single API.
Configuring a Remote Source can be done very easily through our simple to use low-code interface. We support both RESTful and GraphQL APIs, and allow developers to configure custom headers on requests to the remote source. An example use case for this would be providing an Authorization header.
After connecting a Remote Source, you can now add Remote Fields to your schema to combine content from the remote system with content in Hygraph. And that is all there is to it! Within minutes, you can query content from your Remote Source through the easy to use GraphQL API that Hygraph provides.
Remote Sources are available in all Hygraph plans, including on the Community Tier. Detailed documentation can be found here or reach out to us to get a consultation on how remote fields can drastically decrease the complexity of your stack.
Blog Author
Gijs Hendrix
Gijs is the Head of Product at Hygraph. When he's not focused on realizing our product vision, he spends time teaching others how to pronounce his first name.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.