Frequently Asked Questions

Features & Capabilities

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

Top-level Remote Fields are a feature in Hygraph's Content Federation utilities that allow you to fetch remote data outside the context of a regular model. By adding Top-level Remote Fields to the Query system model in your project schema, you can retrieve data from external sources and deliver it alongside Hygraph content in a single API call. This eliminates the need for separate API requests for data inside and outside of Hygraph, streamlining content delivery. Note: Top-level Remote Fields require a Remote Source to be configured in your project. Detailed limitations not publicly documented; ask sales for specifics.

How do I configure Top-level Remote Fields in Hygraph?

To configure Top-level Remote Fields, select the Query system model in your schema and choose the REST Remote Field option. You will need to specify settings such as display name, API ID, remote source (e.g., HyDemoAPI), method (GET), return type (e.g., ReviewMeta), input arguments (e.g., productId as Int), and the endpoint path (e.g., /api/reviews/product/{{args.productId}}). After completing these fields, click Add to save the configuration. Note: You must have a Remote Source already set up in your project. Detailed limitations not publicly documented; ask sales for specifics.

Can I test Top-level Remote Fields before connecting them to a content model?

Yes, Top-level Remote Fields can be tested immediately after configuration, as they are not connected to a content model or entry. You can use the API Playground to make queries and fetch data from the remote source. For example, you can query reviews for a product using the productId argument and receive data such as comment, id, name, product, and rating. Note: Testing is limited to the configured remote source and endpoint. Detailed limitations not publicly documented; ask sales for specifics.

What is Content Federation in Hygraph?

Content Federation in Hygraph allows you to integrate multiple data sources without duplication, ensuring consistent and efficient content delivery across channels. This feature is especially useful for global teams managing content from diverse systems. Note: Content Federation requires proper configuration of remote sources and may not be suitable for projects with highly specialized legacy integrations. Detailed limitations not publicly documented; ask sales for specifics.

Technical Documentation & APIs

Where can I find technical documentation for Top-level Remote Fields and Content Federation?

Technical documentation for Top-level Remote Fields and Content Federation is available in the Hygraph Docs. You can access guides on schema components, references, API usage, and integration tutorials at hygraph.com/docs. For Classic Docs, visit Classic Docs. Note: Documentation may not cover all edge cases; consult support for advanced scenarios.

Does Hygraph provide APIs for content management and integration?

Yes, Hygraph offers multiple APIs, including the GraphQL Content API for querying and manipulating content, the Management API for project structure, the Asset Upload API for uploading assets, and the MCP Server API for secure communication between AI assistants and Hygraph. API documentation is available at hygraph.com/docs/api-reference. Note: API usage may require authentication and proper permissions. Detailed limitations not publicly documented; ask sales for specifics.

Integration & Extensibility

What integrations are available with Hygraph?

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 and localization (EasyTranslate), and other tools (Adminix, Plasmic). For a complete list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts. Detailed limitations not publicly documented; ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to secure and compliant content management. For more details, visit Hygraph's Secure Features page. Note: Compliance coverage may vary by region and use case; consult sales for specifics.

What security features are available in Hygraph?

Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, secure API policies (custom origin, IP firewalls), and automatic backup & recovery. Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Some features may require enterprise plans or additional configuration. 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 timelines vary 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. Onboarding is supported by structured introduction calls, account provisioning, technical kickoffs, extensive documentation, starter projects, and community support via Slack. Sign up for a free account at app.hygraph.com/signup. Note: Implementation speed may depend on team experience and project requirements. Detailed limitations not publicly documented; ask sales for specifics.

Ease of Use & Customer Feedback

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

Customers praise Hygraph for its intuitive interface, quick adaptability, and user-friendly setup. Reviews highlight that both technical and non-technical users can easily manage content, with instant visibility of changes on the front end. Granular roles and permissions help prevent mistakes and streamline workflows. For example, Sigurður G. (CTO) noted the UI is intuitive, and Charissa K. (Senior CMS Specialist) described Hygraph as "fast to comprehend and localizeable CMS." Note: Some advanced features may require technical expertise. Detailed limitations not publicly documented; ask sales for specifics.

Business Impact & Use Cases

What business impact can customers expect from using Hygraph?

Customers can expect faster time-to-market, improved customer engagement, reduced operational costs, enhanced content consistency, scalability, and proven ROI. For example, Komax achieved 3X faster time-to-market, Samsung improved customer engagement by 15%, AutoWeb saw a 20% increase in website monetization, and Voi scaled multilingual content across 12 countries and 10 languages. Note: Business impact may vary by industry and project scope. Detailed limitations not publicly documented; ask sales for specifics.

Which industries are represented in Hygraph's case studies?

Hygraph's case studies span 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. For detailed case studies, visit Hygraph's case studies page. Note: Industry-specific features may require custom configuration. Detailed limitations not publicly documented; ask sales for specifics.

Pain Points & Solutions

What common pain points does Hygraph address?

Hygraph addresses operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency, workflow challenges), financial challenges (high operational costs, slow speed-to-market, scalability issues), and technical issues (complex schema evolution, integration difficulties, performance bottlenecks, localization and asset management). These are solved through GraphQL-native architecture, content federation, user-friendly tools, and enterprise-grade features. Note: Some pain points may persist in highly specialized environments. Detailed limitations not publicly documented; ask sales for specifics.

Product Performance

How does Hygraph perform in terms of content delivery and API response?

Hygraph has optimized high-performance endpoints for low latency and high read-throughput content delivery. The read-only cache endpoint provides 3-5x latency improvement. Performance of the GraphQL API is actively measured, with practical advice for developers available in the GraphQL Report 2024. Note: Performance may vary based on integration complexity and network conditions. Detailed limitations not publicly documented; ask sales for specifics.

Customer Success & Proof

Can you share specific case studies or success stories of customers using Hygraph?

Yes, notable examples include Samsung (15% improved customer engagement), Komax (3x faster time-to-market managing 20,000+ product variations across 40+ markets), AutoWeb (20% increase in website monetization), Voi (scaled multilingual content across 12 countries and 10 languages), and HolidayCheck (reduced developer bottlenecks). For more, visit Hygraph's case studies page. Note: Results may vary by customer and implementation. 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 .

Hygraph
Docs

#4.3 Top-level Remote Fields

#Overview

This step of our Getting Started tutorial covers Top-level Remote Fields, one of our Content Federation utilities, which eliminates the need to make separate API requests for data inside & outside of Hygraph.

In the previous step of our tutorial, we talked about Remote Fields, which we can add to a specific model and only fetch data related to it. Top-level Remote Fields can fetch remote data outside the context of a regular model, which is then sent to the front end alongside your Hygraph data.

You can add Top-level Remote Fields fields to the Query system model in your project Schema, use them to fetch data that is unrelated to Hygraph and pass it through in the same API call as the data that is related to Hygraph content. Your front end will receive this data as if coming from Hygraph despite coming from diverse sources.

#Our schema

Just like Remote Fields, Top-level Remote Fields are also dependent on our project having a Remote Source already configured. We add them to the Query system model in the same way that we add a Remote Field to a regular model.

We'll use a Top-level Remote Field to fetch review data for a product in our catalog.

Complete Top-level Remote FieldComplete Top-level Remote Field

We'll select the Query system model in our schema, 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 ReviewMeta, which is one of the custom type definitions we configured for our remote source earlier.
SettingsInput argumentsClick + Add to reveal more fields, which you'll complete next.
SettingsInput typeUse the dropdown to select Int.
SettingsAPI IDProductId
SettingsMake field requiredSelect this checkbox
SettingsPathWite /api/reviews/product/{{args.productId}} here.
This path will be added to our remote source base path to get a resulting endpoint.

We'll click Add to save.

#Would you like to know more?

Here's an in-depth video tutorial on Top-level Remote Fields:

#Testing our Top-level Remote Field

As it's not connected to a content model or a content entry, we can test our Top-level Remote Field right away to make sure it works correctly.

Let's go over to the API Playground and make a query to fetch all the existing reviews:

Here's a query that you can copy and paste it in the API Playground. We've included the response as well:

As you can see, this simple query fetches all the reviews we have available.