Frequently Asked Questions

Remote Fields & Content Federation

What are Remote Fields in Hygraph and how do they work?

Remote Fields in Hygraph allow you to enrich your content models by connecting to external data sources. You can add a Remote Field to a model in your schema, which fetches data from a configured Remote Source and links it to a specific entry in that model. For example, you can add a Remote Field to a Product model to fetch review data from an external API and display it on your front end. Note: You must configure a Remote Source before adding a Remote Field. Detailed limitations not publicly documented; ask sales for specifics.

How do I add a Remote Field to a model in Hygraph?

To add a Remote Field, first ensure you have configured a Remote Source. Then, in your schema, select the model (e.g., Product), choose the REST Remote Field option, and fill in the required settings such as display name, remote source, method (GET), return type (e.g., Reviews), and path (e.g., /api/reviews/product/{{doc.productSlug}}). This setup allows you to fetch data for specific entries. Note: Only one remote source and custom type can be linked per Remote Field. Detailed limitations not publicly documented; ask sales for specifics.

What are common use cases for Remote Fields in Hygraph?

Common use cases include consolidating product listings from multiple suppliers in e-commerce, enriching content with external review data, or integrating third-party information into your models. For example, you can fetch and display product reviews from an external API directly on your product pages. Note: Use cases requiring complex multi-source joins may require additional configuration. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools for non-technical users, high-performance endpoints, and extensive integration capabilities. It also provides Smart Edge Cache, localization, granular permissions, and structured onboarding resources. Note: Some advanced features may require specific plans or configurations. Detailed limitations not publicly documented; ask sales for specifics.

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and others like Adminix and Plasmic. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or third-party accounts. Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph provide APIs for content management?

Yes, Hygraph provides several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure AI assistant communication. Documentation is available at Hygraph API Reference. Note: API usage may be subject to rate limits or plan restrictions. Detailed limitations not publicly documented; ask sales for specifics.

Implementation & Onboarding

How long does it take to implement Hygraph and how easy is it to start?

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. Hygraph offers structured onboarding, starter projects, and extensive documentation to help users get started quickly. Note: Large-scale migrations or highly customized setups may require additional time. Detailed limitations not publicly documented; ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. Note: For industry-specific compliance needs, contact Hygraph sales. Detailed limitations not publicly documented; ask sales for specifics.

What security features does Hygraph offer?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies including custom origin policies and IP firewalls. All endpoints have SSL certificates. Note: Some features may be available only on specific plans. Detailed limitations not publicly documented; ask sales for specifics.

Performance & Reliability

How does Hygraph ensure high performance and reliability?

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint delivers 3-5x latency improvement. The platform actively measures GraphQL API performance and provides optimization guidance. For more, see the performance improvements blog post and GraphQL Report 2024. Note: Actual performance may vary based on usage patterns and integration complexity. Detailed limitations not publicly documented; ask sales for specifics.

Use Cases & Industries

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is used across industries such as SaaS, eCommerce, media, healthcare, automotive, fintech, education, and more. Note: Teams with highly specialized legacy systems may require additional integration work. Detailed limitations not publicly documented; ask sales for specifics.

What business impact can customers expect from using Hygraph?

Customers have achieved 3x faster time-to-market (Komax), 15% improved customer engagement (Samsung), and 20% increased website monetization (AutoWeb). Hygraph supports scaling multilingual content (Voi: 12 countries, 10 languages) and reduces developer bottlenecks (HolidayCheck). For more, see Hygraph case studies. Note: Results may vary based on implementation and business context. Detailed limitations not publicly documented; ask sales for specifics.

Customer Feedback & Recognition

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Charissa K. (Senior CMS Specialist) described it as fast to comprehend and localizable. Note: Some advanced configurations may require technical expertise. Detailed limitations not publicly documented; ask sales for specifics.

What industry recognition has Hygraph received?

Hygraph ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted the easiest to implement headless CMS for the fourth time. Note: Rankings are based on G2 user reviews and may change over time. Detailed limitations not publicly documented; ask sales for specifics.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#4.2 Remote Fields

#Overview

This step of our Getting Started tutorial covers Remote Fields, one of our Content Federation features.

We use Remote Fields for data enrichment. You can add them to a model in your schema to fetch data from a Remote Source. This type of field connects remote data to a specific entry in that model, and it's always related to a single remote source & custom type.

To be able to add a Remote Field to a model in your Schema, you need to have configured a Remote Source first, so make sure you have followed the previous step of our tutorial before you start this one.

#The use case

A common use case is to use Remote Fields to facilitate e-commerce by consolidating product listings from multiple suppliers onto one platform. For the purposes of this tutorial, we will add a Remote Field to our Product model and use it to fetch review data from the DEMO Hygraph API that we connected in our remote sources lesson, so it can be displayed on our front end.

#Adding a Remote Field

We're going to use the Remote Source that we configured in the previous lesson to add a Remote Field to our Product Model.

Add a Remote Field to Product model

Let's go to our Schema, select the model, and then click on the REST Remote Field option on the right sidebar.

We'll use the following information:

TabFieldInput
SettingsDisplay nameReviews
SettingsAPI IDCompleting the display name will autocomplete the API ID field. We'll leave this value as it is.
SettingsRemote sourceHyDemoAPI is selected by default. We'll leave this value as it is.
SettingsMethodGET is selected by default. We'll leave this value as it is.
SettingsReturn typeUse the dropdown to select Reviews, because we want to fetch review data for your Product model.
What we just did here is select one of the custom type definitions that we configured for our remote source in the last lesson.
SettingsPathWite /api/reviews/product/{{doc.productSlug}} here.
This path will be added to our remote source base path to get a resulting endpoint. doc.productSlug references the content entry, so we'll be able to fetch reviews for specific products.

We'll click Add to save.