Content federation lets you combine data from multiple systems and expose it through a single GraphQL API endpoint without migrating the content itself. Instead of moving product data from a commerce platform, inventory from a warehouse system, or reviews from a third-party service into Hygraph, you connect those sources directly and query everything from one place.
Content Federation
#How content management has evolved
The relationship between content management and content delivery has changed significantly over time.
Traditional CMSs created a one-to-one relationship. Content was managed and presented by the same system, tightly coupled together.
The headless CMS decoupled content management from the presentation layer, enabling a one-to-many relationship. Content is managed in one place and served via API to websites, apps, smart TVs, and more.
Today, organizations need to go further. Content no longer lives in a single system. It is spread across legacy CMSs, PIMs, DAMs, SaaS tools, commerce platforms, and more. This creates the need for a many-to-many relationship, where content from multiple sources can be unified and delivered to multiple frontends. That is what content federation enables.
What is Content Federation?
#What is content federation?
Content federation is the process of sourcing data from multiple systems and making it available through a single GraphQL API, without duplicating or migrating the underlying content.
In Hygraph, this is powered by remote sources. Remote sources allow you to connect external APIs, whether GraphQL or REST, directly to your Hygraph project. Once connected, content editors can reference data from those sources alongside native Hygraph content, and developers can fetch everything in a single API call.
The use cases below show what content federation looks like in practice.
#Use cases
#E-commerce
An e-commerce team typically manages product descriptions, editorial content, and campaign pages in Hygraph, while product pricing, stock levels, images, and categories live in a commerce platform such as Shopify, BigCommerce, or commercetools. Without content federation, keeping these in sync requires either migrating data into Hygraph or building custom middleware to stitch them together on the frontend.
With content federation, editors reference products directly from the commerce platform using a product picker or SKU. When a page is rendered, Hygraph fetches the latest pricing and inventory from the commerce system automatically. Developers make one API call and get everything back in a single response. Pricing changes, stock updates, and product launches are reflected immediately, with no manual updates required in Hygraph.
#Travel
A travel platform aggregates content from multiple providers, such as flight schedules from an airline API, hotel availability from a booking platform, and car rental options from a separate fleet management system. Managing this in a traditional CMS would require syncing data from all three sources on a schedule, which introduces lag and risks serving outdated availability or pricing to users.
With content federation, Hygraph connects directly to each provider's API. Editorial content, such as destination guides, travel tips, and curated itineraries, lives natively in Hygraph, while live availability and pricing are pulled from the provider APIs at query time. Customers see accurate, real-time information without the content team having to manage data imports or the development team having to maintain a separate aggregation layer.
#Stock and inventory management
A manufacturer or retailer operating across multiple warehouses needs to surface real-time inventory data on their website or internal tools. Stock levels change constantly and vary by location, making it impractical to maintain a copy of that data in the CMS.
With content federation, Hygraph connects to the warehouse management system or ERP and pulls live inventory data alongside product content. Editors manage product descriptions, specifications, and marketing copy in Hygraph, while stock levels, lead times, and availability by location come directly from the source system. The result is a product page that always reflects actual inventory, with no synchronization scripts and no stale data.
#Benefits
Eliminates content silos
Content federation sources data directly from existing systems through a single API. Teams no longer need to migrate data from legacy platforms, and the frontend always receives the most current version.
Supports live data
For data that changes frequently, such as pricing, inventory, availability, and weather, content federation ensures the frontend always reflects the latest state. There is no risk of stale data from manual updates or scheduled syncs.
Preserves data integrity
With a single source of truth per data type, content federation removes the duplication that leads to inconsistencies. Data is not copied across systems. Instead, it is referenced programmatically from its origin.
Reuses existing content
Content that already exists in other systems can be brought into Hygraph without transformation or re-entry. Teams choose the best tool for each job and federate the results rather than consolidating everything into one platform.
Gives editors more autonomy
Because data flows through Hygraph rather than being stitched together on the frontend, editors can control what gets displayed on the final pages without requiring developer involvement for every change.
Connects third-party APIs
Hygraph can federate content from any API, regardless of whether it is GraphQL or REST, and expose it through a unified GraphQL endpoint. This includes public databases, review platforms, travel aggregators, stock management systems, and more.
#What's next
To start using content federation, configure a remote source in your Hygraph project.