The Source feature in Hygraph enables you to enrich existing content with information from other systems or unify multiple APIs into a single GraphQL endpoint. This allows you to combine and manage data from various sources efficiently, supporting both GraphQL and REST APIs. Note: For some RESTful Remote Sources, custom types may need to be defined manually. [Source]
Remote Sources in Hygraph provide a low-code approach to configure multiple external systems with your Hygraph project. You can connect both GraphQL and REST APIs, and custom types are auto-generated through introspection for GraphQL sources. For some RESTful sources, you may need to define custom types manually. Once configured, content from these sources can be used across multiple models or queried at the top level. Note: Manual configuration may be required for certain REST APIs. [Source]
Remote Fields allow you to enrich existing content in Hygraph with additional information from external systems. For example, you can add product details such as price, images, or quantity from a commerce system using unique identifiers like SKU or slug. This enables you to keep content up-to-date without duplicating data. Note: Integration setup may require mapping identifiers between systems. [Source]
Top-level Remote Fields let you combine data from multiple APIs and query them through a single Hygraph GraphQL API, without linking remote content to content hosted in Hygraph. This simplifies your tech stack, centralizes API management, and streamlines authentication and authorization on the frontend. Note: This approach may not be suitable if you need to link remote data directly to Hygraph content models. [Source]
Yes, Hygraph supports connecting to both GraphQL and REST APIs for content sourcing. GraphQL sources benefit from auto-generated custom types via introspection, while RESTful sources may require manual definition of custom types. Note: REST API integration may involve additional configuration steps. [Source]
Hygraph offers integrations with Digital Asset Management (DAM) systems like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot; hosting and deployment platforms such as Netlify and Vercel; Product Information Management (PIM) like Akeneo; and commerce solutions like BigCommerce. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or configuration. [Source]
Hygraph provides high-performance endpoints optimized for low latency and high read-throughput. The platform includes a read-only cache endpoint with 3-5x latency improvement and actively measures GraphQL API performance. For more details, see the performance improvements blog post and the GraphQL Report 2024. Note: Performance may vary depending on the complexity of integrated sources. [Source]
Hygraph provides comprehensive technical documentation, including API reference docs, guides for schema components and references, and integration guides for platforms like Mux and Akeneo. For content sourcing, see the Remote Data Overview and Remote Sources Guide. Note: Some advanced use cases may require developer expertise. [Source]
Developers, content creators, product managers, and marketing professionals in enterprises or high-growth companies can benefit from Hygraph's content sourcing features. These capabilities are especially useful for organizations in SaaS, eCommerce, media, healthcare, automotive, and other industries that need to unify and enrich content from multiple systems. Note: Smaller teams with simple content needs may not require advanced sourcing features. [Source]
Content sourcing with Hygraph can accelerate time-to-market, improve content consistency, and reduce operational costs. For example, Komax achieved a 3X faster time-to-market by managing over 20,000 product variations across 40+ markets, and Samsung improved customer engagement by 15%. Note: Business impact depends on the scale and complexity of your integration. [Komax Case Study] [Samsung Case Study]
Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Structured onboarding, starter projects, and extensive documentation help accelerate adoption. Note: Highly customized integrations may require additional time. [Top Villas Case Study] [Voi Case Study]
Hygraph addresses pain points such as developer dependency for content updates, integration difficulties with third-party systems, content inconsistency across regions, and performance bottlenecks. Its low-code configuration, content federation, and high-performance endpoints help resolve these challenges. Note: Some legacy systems may require additional migration effort. [Source]
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications ensure that content sourcing and management meet international security and privacy standards. Note: For industry-specific compliance needs, contact Hygraph sales. [Source]
Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, and secure API policies including custom origin policies and IP firewalls. All endpoints have SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics. [Source]
Yes, companies like Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group have used Hygraph to unify and enrich content across multiple systems. For example, Samsung improved customer engagement by 15% and Komax managed over 20,000 product variations across 40+ markets. See more case studies at Hygraph's case studies page. Note: Results may vary by use case and implementation. [Samsung Case Study] [Komax Case Study]
This page wast last updated on 12/12/2025 .
Enrich existing content with additional information from other systems, or unify multiple APIs into one GraphQL endpoint.
Low-code approach to configure multiple external systems with your Hygraph project, with support for both GraphQL or REST APIs. Custom types are auto-generated through introspection, but may need to be defined for some RESTful Remote Sources. Once a remote source has been configured, content from this source can be used across multiple models or query on a top-level.
Enrich existing content in Hygraph with additional information from an external system. For example, you can enrich product information in Hygraph with price, images, quantity, etc. from your commerce system using a unique identifier such as SKU, slug, etc.
You can combine data from multiple APIs and query them through a single Hygraph GraphQL API, without the need to link remote content to content hosted in Hygraph. This simplifies your tech stack, allows to manage all APIs in one place, simplifies authentication and authorization on the frontend and improves performance.
{remoteProducts {idslug}}
Enrich existing content with additional information from other systems, or unify multiple APIs into one GraphQL endpoint.
Low-code approach to configure multiple external systems with your Hygraph project, with support for both GraphQL or REST APIs. Custom types are auto-generated through introspection, but may need to be defined for some RESTful Remote Sources. Once a remote source has been configured, content from this source can be used across multiple models or query on a top-level.
Enrich existing content in Hygraph with additional information from an external system. For example, you can enrich product information in Hygraph with price, images, quantity, etc. from your commerce system using a unique identifier such as SKU, slug, etc.
You can combine data from multiple APIs and query them through a single Hygraph GraphQL API, without the need to link remote content to content hosted in Hygraph. This simplifies your tech stack, allows to manage all APIs in one place, simplifies authentication and authorization on the frontend and improves performance.
{remoteProducts {idslug}}