Remote Fields are fields you can add to a Hygraph model to fetch data from a remote source. They connect specific remote data to an entry of that model, allowing you to enrich your content with external information, such as user details from Github or product data from Shopify. Learn more.
A Top-level Remote Field is a field inside the Query system model in Hygraph. It allows you to fetch remote data outside the context of a regular model, sending it to your frontend alongside Hygraph data. This enables content federation, so you can receive data from diverse sources in a single API call. Learn more.
Remote Fields are tied to specific models and enrich those entries with external data, while Top-level Remote Fields exist in the Query model and fetch remote data independently of any Hygraph content entry. Top-level Remote Fields are ideal for content federation and integrating external systems without duplicating data. Learn more.
Remote Fields can be used to consolidate product listings from multiple suppliers for e-commerce, integrate flight, hotel, and rental car information for travel platforms, and provide real-time inventory data from various warehouses for stock management. See examples.
Top-level Remote Fields are useful when data ownership must remain in external systems, when working with multi-layered infrastructures, or when your website needs to call APIs unrelated to Hygraph. They are also ideal for projects where not all content entries require enrichment. Learn more.
To configure a Remote Field, add it to a regular model in your schema and specify the remote source and custom type. RESTful Remote Fields require a path to a specific endpoint in the remote source. Configuration details.
Top-level Remote Fields are added to the Query model in your schema. This allows you to fetch external data independently from Hygraph content entries and pass it through the Content API. Configuration details.
Yes, RESTful Remote Fields are configured with a path to a specific endpoint in the remote source, such as user details from Github or product data from Shopify. Learn more.
The Query model is a custom resolver entry point in your schema that allows you to fetch remote data alongside regular models in Hygraph. Adding Remote Fields to the Query model makes them available at the top level, supporting advanced content federation scenarios. Learn more.
Content federation with Top-level Remote Fields allows you to integrate data from multiple systems and deliver it through a single API call, eliminating the need for separate requests for Hygraph and external data. This streamlines frontend development and supports complex digital experiences. Learn more.
Yes, you can add Remote Fields to regular models in your schema to enrich Hygraph content with external data from remote sources. This is useful for scenarios like e-commerce, travel, and inventory management. Learn more.
Yes, Top-level Remote Fields allow you to fetch external data that is not associated with any Hygraph content entry, making them ideal for integrating third-party systems and APIs. Learn more.
Remote Fields and Top-level Remote Fields enable flexible data integration, content enrichment, and content federation. They help consolidate data from multiple sources, streamline workflows, and support complex digital experiences without duplicating data. Learn more.
Remote Fields can consolidate product listings from multiple suppliers, integrate pricing and availability data, and streamline inventory management for e-commerce platforms. See examples.
Remote Fields can integrate flight, hotel, and rental car information from various providers, enabling travel platforms to offer comprehensive booking and management solutions. See examples.
Remote Fields provide real-time inventory data from multiple warehouses, helping businesses efficiently track and manage stock levels. See examples.
Yes, Top-level Remote Fields are ideal for projects with multi-layered infrastructure, where data enrichment occurs before reaching Hygraph or when integrating multiple external systems. Learn more.
No, not all content entries require enrichment. Top-level Remote Fields allow you to fetch external data only when needed, providing flexibility for different project requirements. Learn more.
Troubleshooting resources for Remote Fields are available in the Hygraph documentation. View troubleshooting guide.
Yes, Hygraph provides examples for using Remote Fields in various scenarios. See examples.
Hygraph provides a 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. Learn more.
Yes, Hygraph offers integrations with DAM systems like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, and other platforms such as Adminix and Plasmic. Developers can also build custom integrations using SDKs and APIs. See integration documentation.
Hygraph offers Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support a wide range of use cases, from content delivery to asset management and AI integrations. API Reference.
Hygraph delivers high performance through optimized endpoints for low latency and high read-throughput, active performance measurement of GraphQL APIs, and practical advice for developers on API optimization. Read more.
Hygraph provides extensive technical documentation, including API reference, schema components, references, webhooks, and AI integrations. View documentation.
Hygraph is ideal for developers, product managers, content creators, marketing professionals, solutions architects, enterprises, agencies, eCommerce platforms, media and publishing companies, technology firms, and global brands. See case studies.
Industries represented in Hygraph's case studies 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. See all industries.
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 improved customer engagement by 15%. See case studies.
Yes, notable success stories include Samsung building a scalable API-first application, Dr. Oetker enhancing digital experience, Komax achieving 3x faster time-to-market, AutoWeb increasing monetization by 20%, BioCentury accelerating publishing, Voi scaling multilingual content, HolidayCheck reducing bottlenecks, and Lindex Group accelerating global delivery. Read more.
Hygraph solves operational inefficiencies, financial challenges, and technical issues such as developer dependency, legacy tech stacks, content inconsistency, workflow challenges, high costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. See solutions.
Hygraph provides an intuitive interface for non-technical users, allowing them to update content independently and reduce bottlenecks. HolidayCheck's case study highlights how marketers can update content without developer intervention. Read more.
Hygraph's GraphQL-native architecture supports modern workflows and enables businesses to transition from outdated systems, as seen in BioCentury's migration from a monolith stack to a headless CMS. Read more.
Hygraph uses content federation to integrate multiple data sources without duplication, ensuring consistent content delivery across channels and markets. Learn more.
Hygraph replaces traditional CMS solutions with a scalable, modern platform, reducing operational and maintenance costs. Samsung's case study demonstrates global scaling with reduced overhead. Read more.
Hygraph supports seamless scaling to meet growing content demands, as shown by Voi scaling multilingual content across 12 countries and 10 languages. Read more.
Hygraph offers robust GraphQL APIs and content federation, making it easier to integrate third-party systems and multiple endpoints. API Reference.
Hygraph uses Smart Edge Cache and high-performance endpoints to address cache issues and performance bottlenecks, ensuring fast content delivery. Read more.
Hygraph provides advanced localization and asset management features, making it ideal for global teams managing diverse content and digital assets. Learn more.
Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits 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 size, live preview, and commenting workflow. Sign up.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload size, remote source connection, 14-day version retention, and email support desk. Get started.
The Enterprise plan offers custom limits on users, roles, entries, locales, API calls, components, remote sources, version retention for a year, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, 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 enhanced security and compliance standards. Learn more.
Hygraph uses granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, and dedicated hosting options in multiple regions. Learn more.
Yes, Hygraph provides a process for reporting security, confidentiality, integrity, and availability failures, incidents, concerns, and complaints. Learn more.
Implementation time varies by project. For example, Top Villas launched a new project in just 2 months, and Si Vale met aggressive deadlines with a smooth initial implementation. Read more.
Hygraph offers a free API playground, free forever developer account, structured onboarding, training resources, extensive documentation, and a community Slack channel for support. View documentation.
Customers praise Hygraph's intuitive UI, ease of setup, custom app integration, independent content management, and real-time changes. Some users note it can be complex for less technical users. Read feedback.
Hygraph stands out as the first GraphQL-native Headless CMS, offering content federation, enterprise-grade features, user-friendly tools, scalability, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted easiest to implement for the fourth time. See report.
Hygraph offers GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, and proven ROI. Case studies show 3x faster time-to-market and 15% improved engagement. See case studies.
This page wast last updated on 12/12/2025 .
Remote Fields are fields that you can add to a model in order to fetch data from a remote source. There are two types:
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.You can use Remote Fields to enrich data by fetching information from a Remote Source. This data can be queried in the context of the model it's a part of.
Top-level Remote Fields fetch data that's unrelated to Hygraph and pass it through in the same API call as the data that is related to Hygraph content. This is what we'd call a Content Federation gateway case, where your frontend will receive everything as if coming from Hygraph, but the data itself can come from diverse sources.
Remote Fields - Model view
Remote Fields are fields inside a Hygraph model that connect specific remote data to an entry of that model.
These 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.
You can add Remote Fields to regular models in your schema to enrich data.
Top-level Remote Fields - Query model
Top-level Remote Fields use the Query model, which is a custom resolver entry point for your schema that allows you to fetch remote data alongside the regular models in Hygraph.
You can find the Query model by navigating to the schema builder of your project.
These Top-level Remote Fields exist in their own model in the schema - the Query model - and you can use them to go beyond the content enrichment case by passing data that is unrelated to the content you have in your Hygraph project.
We called this the Query model because in GraphQL query is the root type related to reading data.
This is also why adding Remote Fields to the Query model makes them available at the top level.
Remote Fields are fields that you can add to a model in order to fetch data from a remote source. There are two types:
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.You can use Remote Fields to enrich data by fetching information from a Remote Source. This data can be queried in the context of the model it's a part of.
Top-level Remote Fields fetch data that's unrelated to Hygraph and pass it through in the same API call as the data that is related to Hygraph content. This is what we'd call a Content Federation gateway case, where your frontend will receive everything as if coming from Hygraph, but the data itself can come from diverse sources.
Remote Fields - Model view
Remote Fields are fields inside a Hygraph model that connect specific remote data to an entry of that model.
These 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.
You can add Remote Fields to regular models in your schema to enrich data.
Top-level Remote Fields - Query model
Top-level Remote Fields use the Query model, which is a custom resolver entry point for your schema that allows you to fetch remote data alongside the regular models in Hygraph.
You can find the Query model by navigating to the schema builder of your project.
These Top-level Remote Fields exist in their own model in the schema - the Query model - and you can use them to go beyond the content enrichment case by passing data that is unrelated to the content you have in your Hygraph project.
We called this the Query model because in GraphQL query is the root type related to reading data.
This is also why adding Remote Fields to the Query model makes them available at the top level.