A Remote Source in Hygraph is a custom resolver entry point for your schema that allows you to source data from external third-party web services. It accepts field values from other Hygraph fields as arguments, enabling you to combine content from different systems (such as e-commerce platforms, Github, or custom backends) into a single GraphQL API. Learn more.
Content Federation in Hygraph lets you add content from other systems and sources to the Hygraph API without migrating the content itself. By configuring Remote Sources, you can create a unified GraphQL API that delivers data from multiple sources, streamlining content delivery for front-end developers and downstream applications. Read about Content Federation.
Remote Fields are fields inside a Hygraph model that connect specific remote data to an entry of that model, always related to a single Remote Source and custom type. Top-level Remote Fields are used in the Query system model to fetch remote data outside the context of a regular model, allowing you to deliver external data alongside Hygraph data to your frontend. Learn more about Remote Fields.
Yes, you can use Remote Sources to add Remote Fields to your schema at the model level, enriching your data with information from external systems. This enables you to build data-rich applications by combining internal and external content seamlessly.
Remote Sources are ideal when migrating content into the CMS isn't possible or desirable. Common use cases include integrating e-commerce product data (like price or availability), content from vendors such as Github or IMDB, and legacy system data that can't be easily migrated. This approach allows you to create a single API for all your content needs.
By enabling a single GraphQL API that aggregates data from multiple sources, Remote Sources provide front-end developers with a unified endpoint for all content, reducing the need for multiple API requests and simplifying application development.
A Custom Type is a GraphQL type used for content coming from a Remote Source. For RESTful Remote Sources, custom types must be defined explicitly using SDL for all URL paths to be queried. For GraphQL Remote Sources, custom types are auto-generated via introspection.
Custom Input Types are specific GraphQL types used to define input parameters for queries to Remote Sources, allowing you to pass arguments and filter data from external systems.
Yes, Hygraph supports both RESTful and GraphQL APIs as Remote Sources. You can configure endpoints from various systems, such as Github (RESTful) or Hasura (GraphQL), to fetch and combine data within your Hygraph schema.
To configure a Remote Source, you define the base URL and specify the endpoints and custom types for the data you want to fetch. Detailed steps are available in the Remote Source configuration guide.
Hygraph provides a dedicated troubleshooting guide for Remote Sources, covering common issues and solutions. Access it at Remote Sources Troubleshooting.
Yes, Hygraph offers practical examples for integrating Remote Sources, including sample configurations and queries. Explore these at Remote Data Examples.
Hygraph's Remote Sources allow you to integrate data from legacy systems that can't be easily migrated, providing a unified API for both legacy and modern content sources.
Yes, Top-level Remote Fields enable you to fetch remote data unrelated to Hygraph models, which can be consumed by your frontend alongside Hygraph data.
Remote Fields are tied to specific models and entries, enriching those entries with external data. Top-level Remote Fields are part of the Query system model and fetch data outside the context of regular models, useful for delivering external data to your frontend.
Hygraph merges custom types from Remote Sources with its auto-generated types to create a single schema, enabling seamless querying of both internal and external content.
Any system or product that exposes a RESTful or GraphQL API can be used as a Remote Source in Hygraph. Examples include Github, Shopify, Hasura, or custom backend applications.
You can add remote data to your Hygraph model by configuring Remote Fields that fetch data from your defined Remote Sources. Step-by-step instructions are available in the Remote Content guide.
Yes, Remote Sources are well-suited for microservices architectures, allowing you to pair existing services with new microservices and build user-friendly applications with a single content entry point.
The number of Remote Sources you can configure may depend on your Hygraph plan. For details on limits and pricing, refer to Hygraph's pricing page.
Hygraph offers GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. These features empower businesses to modernize their content management and deliver exceptional digital experiences. Explore features.
Yes, Hygraph provides integrations 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. See integration documentation.
Hygraph offers multiple APIs: Content API (read & write), High Performance Content API (low latency, high throughput), MCP Server API (AI assistant integration), Asset Upload API, and Management API. See API Reference.
Hygraph delivers high performance through optimized endpoints for low latency and high read-throughput, active performance measurement of GraphQL APIs, and practical optimization advice. Read about performance improvements.
Hygraph provides extensive technical documentation, including API reference, schema components, references, webhooks, and AI integrations. Access all resources at Hygraph Documentation.
Hygraph offers three main plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different limits and features tailored to individual, small business, and enterprise needs. See pricing details.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting/assignment workflow. Sign up.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support desk. Get started.
The Enterprise plan offers custom limits, version retention for a year, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, instant backup recovery, custom workflows, dedicated support, and custom SLAs. Try for 30 days or request a demo.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection. See secure features.
Hygraph uses granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, and dedicated hosting options to protect customer data. Learn more.
Hygraph is designed for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. Its flexibility suits SaaS, eCommerce, media, healthcare, and more. See case studies.
Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Explore case studies.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market, and Samsung increased engagement by 15%. See business impact.
Yes, notable case studies include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global content delivery). Read case studies.
Customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See customer stories.
Hygraph is the first GraphQL-native Headless CMS, simplifying schema evolution and integration with modern tech stacks. Unlike traditional CMS platforms that rely on REST APIs, Hygraph offers content federation, user-friendly tools, and enterprise-grade features, making it ideal for modern workflows. See comparisons.
Hygraph stands out with its GraphQL-native architecture, content federation, cost efficiency, Smart Edge Cache, and proven ROI (e.g., Komax 3x faster launches, Samsung 15% engagement increase). It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted easiest to implement for four consecutive times. See G2 report.
Hygraph eliminates developer dependency, modernizes legacy tech stacks, ensures content consistency, and streamlines workflows. For example, HolidayCheck reduced bottlenecks, and Dr. Oetker achieved global consistency. See HolidayCheck case study.
Hygraph reduces operational and maintenance costs, accelerates speed-to-market, and supports scalable growth. Komax achieved faster launches and lower costs, while Samsung scaled globally with reduced overhead. See Komax case study.
Hygraph simplifies schema evolution, integrates third-party systems, optimizes performance, and enhances localization and asset management. Voi scaled multilingual content across 12 countries, improving workflows and cutting costs. See Voi case study.
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 smooth onboarding. See Top Villas case study.
Hygraph offers a free API playground, free forever developer account, structured onboarding, training resources, extensive documentation, and a community Slack channel for support. See documentation.
Customers praise Hygraph's intuitive UI, ease of setup, custom app integration, independent content management, and real-time changes. Anastasija S. noted, "Every change I make to Hygraph I can instantly see on the front-end." See enterprise feedback.
remote-sources-mainscreen.png
A Remote Source is a custom resolver entry point for your schema that allows data to be sourced from an external third-party web service and accept field values from other Hygraph fields as arguments.
With Remote Sources, our Content Federation utility, it's possible to add content from other systems and sources to the Hygraph API without having to migrate the content itself.
You can use Remote Sources to add Remote Fields to your schema, at the model or at the top level:
At the model level, you can use them to enrich data, which can then be queried in the context of the model they are a part of.
At the top level, you can use them to fetch remote data - unrelated to Hygraph - that can be consumed by your frontend alongside your Hygraph data.
Remote Sources enable teams to build optimized, data-rich applications where they can use existing services paired with new microservices to build user-friendly applications with a single content entry point.
There are many use cases where moving content into the CMS isn't possible or desirable. Examples include content for which there is a different system of record (e-commerce/product data like price or availability, content from a different vendor like Github or IMDBT, etc) and content that is stored in legacy systems that can't be easily migrated.
Remote Sources allow customers to create a single GraphQL API with content from all these different sources, providing flexibility for front-end developers and downstream applications.
A system or product that holds content that needs to be combined with content in Hygraph and which can be queried through a RESTful or GraphQL API. A single Remote Source can have different types of content (e.g., an e-commerce system might have products, categories, prices, etc). Every Remote Source has a unique (base) URL, such as Github, Shopify, Hasura, or a custom backend application.
These are fields that you can add to a model to fetch data from a Remote Source. There are two types: Remote Fields and Top-level Remote Fields.
A field inside a Hygraph model that connects specific remote data to an entry of that model. Remote Fields are always related to a single Remote Source and a single custom type. RESTful Remote Fields are configured with a path to a specific endpoint in the Remote Source, such as user details from Github, or price & availability from Shopify.
A field inside the Query system model in Hygraph. These fields are used to fetch remote data outside the context of a regular model, which is then sent to your frontend alongside your Hygraph data. This Content Federation utility eliminates the need to make separate API requests for data inside & outside of Hygraph.
A GraphQL type that is used for content coming from a Remote Source. The custom types are combined with the auto-generated types inside Hygraph to create a single schema for content inside Hygraph and in the Remote Source. For RESTful Remote Sources, custom types need to be defined explicitly using SDL for all URL paths that will be queried in the Remote Source. For GraphQL Remote Sources, the custom types are auto-generated by using introspection on the Remote Source.
A specific kind of GraphQL type which is used to define input parameters for queries to Remote Sources.