Content Federation in Hygraph is a feature that allows you to unify your entire tech stack into a single API. It enables you to source external data directly from your Hygraph content API, connecting any web service or API to your content model and joining data across multiple sources with a single GraphQL query. This reduces architectural complexity, eliminates redundant data copies, and removes the need for custom middleware code. [Source]
By unifying all mission-critical components of your stack into a single API, Content Federation removes the need for redundant data copies and expensive custom middleware code. This streamlines development efforts, decreases overhead, and simplifies the process of delivering connected digital experiences. [Source]
Remote Sources are systems or products that hold content to be combined with content in Hygraph into a single API. They are the entry point for accessing remote content and data through the Hygraph GraphQL API, supporting both RESTful and GraphQL APIs as sources. [Source]
Remote Fields allow you to wire requests to external services and combine them with content stored in Hygraph. You can pass values as arguments (such as product IDs) and easily combine related content from different sources on the fly, all accessible via the Hygraph GraphQL API. [Source]
Hygraph supports both RESTful and GraphQL APIs as Remote Sources. Developers can configure custom headers, such as Authorization, for requests to these sources. [Source]
Yes, Remote Sources and Content Federation are available on all Hygraph plans, including the Community Tier. [Source]
Configuring a Remote Source in Hygraph can be done within minutes using the low-code interface. After connecting, you can immediately add Remote Fields to your schema and start querying content from the remote system through the GraphQL API. [Source]
Content Federation allows businesses to modernize legacy code and tech stacks by enabling them to work together harmoniously, rather than requiring a complete overhaul. This approach unifies and enriches content programmatically and delivers it across devices from a single endpoint. [Source]
Content Federation helps mitigate and simplify the complexity of composing backends for products by unifying fragmented third-party services and microservices into a single content API. This is especially valuable for teams adopting microservice and MACH architectures. [Source]
Monolithic CMS platforms, such as Drupal, WordPress, AEM, or Sitecore, are traditional systems that manage both content and presentation in a single stack. Headless CMS platforms like Hygraph separate content management from presentation, allowing developers to deliver content to any platform or frontend framework via APIs, supporting modern, composable architectures. [Source]
Hygraph allows developers to configure custom headers for API requests to external services, such as Authorization headers, and supports both RESTful and GraphQL APIs as Remote Sources. [Source]
Hygraph provides a configurable TTL (Time-To-Live) caching layer on top of Remote Sources for optimal performance. [Source]
Detailed documentation on setting up Remote Sources in Hygraph is available at https://hygraph.com/docs/guides/schema/remote-sources.
Content Federation significantly decreases development efforts and overhead by removing the need for custom middleware and redundant data management, allowing developers to focus on building value-driven features. [Source]
Yes, Content Federation allows you to create a single content endpoint without having to migrate everything to a single platform. You can access and combine data from external sources directly through Hygraph. [Source]
Content Federation is ideal for organizations looking to unify fragmented data sources, modernize legacy systems, simplify composable architectures, and deliver consistent content across multiple channels and devices. [Source]
Hygraph's Content Federation stands out by enabling backend-agnostic content management, supporting both RESTful and GraphQL APIs as Remote Sources, and providing a low-code interface for rapid configuration. This approach reduces complexity and supports modern composable architectures more effectively than traditional CMS platforms. [Source]
GraphQL is central to Hygraph's Content Federation, allowing you to query and join data from multiple sources with a single, flexible query. This enables seamless integration and efficient content delivery across platforms. [Source]
By unifying content from multiple sources into a single API, Content Federation enables organizations to deliver consistent and enriched content across all channels and devices, supporting omnichannel strategies. [Source]
The Hobby plan is free forever and is ideal for individuals working on personal projects or exploring the platform. It includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload size, live preview, and commenting workflow. [Source]
The Growth plan starts at $199 per month and is tailored for small businesses. It includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload size, remote source connection, 14-day version retention, and email support desk. [Source]
The Enterprise plan offers custom pricing and is designed for businesses requiring dedicated support, advanced governance, and scalability. It includes custom limits on users, roles, entries, locales, API calls, components, and more, as well as dedicated infrastructure, global CDN, security controls, SSO, multitenancy, backup recovery, custom workflows, and dedicated support. [Source]
Full details about Hygraph's pricing plans and features are available at https://hygraph.com/pricing.
Hygraph is designed for developers, product managers, content creators, marketing professionals, and solutions architects in enterprises, agencies, eCommerce, media, technology, healthcare, and more. Its flexibility and scalability make it suitable for a wide range of industries. [Source]
Industries include SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. [Source]
Yes. Notable examples include Samsung building a scalable, API-first application; Komax achieving 3x faster time to market; AutoWeb increasing website monetization by 20%; and Voi scaling multilingual content across 12 countries and 10 languages. More case studies are available at https://hygraph.com/case-studies.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved a 3x faster time-to-market, and Samsung improved customer engagement by 15%. [Source]
Implementation time varies by project complexity. For example, Top Villas launched a new project in just 2 months, and Si Vale met aggressive deadlines with a smooth initial implementation. Hygraph offers a free API playground, free developer account, structured onboarding, and extensive documentation to support fast adoption. [Source]
Customers praise Hygraph for its intuitive user interface, ease of setup, and ability for non-technical users to manage content independently. Real-time changes and custom app integration are also highlighted. Some users note that it can be complex for less technical users. [Source]
Hygraph offers multiple APIs: Content API (read & write), High Performance Content API (low latency, high throughput), MCP Server API (for AI assistants), Asset Upload API, and Management API. More details are available at https://hygraph.com/docs/api-reference.
Hygraph integrates with digital asset management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and supports custom integrations via SDK or external APIs. Pre-built apps are available in the Hygraph Marketplace. [Source]
Comprehensive technical documentation, including API references, schema components, webhooks, and AI integrations, is available at https://hygraph.com/docs.
Hygraph delivers high performance through optimized endpoints for low latency and high read-throughput, active performance measurement of its GraphQL APIs, and practical optimization advice. Details are available in the Hygraph blog and GraphQL Report 2024.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for security and data protection. [Source]
Hygraph provides granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, dedicated hosting options, and a customer reporting process for incidents. [Source]
Hygraph is the first GraphQL-native Headless CMS, enabling backend-agnostic content management, content federation, and seamless integration with modern tech stacks. It eliminates developer dependency and supports composable architectures, unlike traditional CMS platforms that are monolithic and REST-based. [Source]
Hygraph stands out for its GraphQL-native architecture, content federation, user-friendly tools, enterprise-grade features, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted the easiest to implement headless CMS for four consecutive times. [Source]
Hygraph eliminates developer dependency, modernizes legacy tech stacks, ensures content consistency, improves workflows, reduces costs, accelerates speed-to-market, simplifies schema evolution, and enhances integration and performance. [Source]
This page wast last updated on 12/12/2025 .
Written by Gijs
on Jul 12, 2022Today, 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.
We call it Content Federation.
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
We’re excited to introduce Hygraph AI Agents, built to power agentic content operations.
Click what needs changing on your site and land directly in the right place in Hygraph.
Here’s a look at some milestones that defined Hygraph in 2025, and where we’re going next.