Frequently Asked Questions

Features & Capabilities

What are Top-level Remote Fields in Hygraph?

Top-level Remote Fields in Hygraph allow you to directly fetch content from remote systems using a single Hygraph API, without the need to link remote content to content hosted in Hygraph. This enables you to unify data from multiple sources—such as e-commerce platforms (e.g., Shopify), digital asset management systems (e.g., Cloudinary), and content stored in Hygraph—into a single GraphQL query. [Source]

How do Top-level Remote Fields differ from Model-level Remote Fields?

Model-level Remote Fields require a unique identifier (such as an ID or SKU) present in both Hygraph and the remote system, and are used to enrich existing Hygraph content with additional data from a remote API. In contrast, Top-level Remote Fields allow you to fetch data directly from remote systems without needing a corresponding content entry in Hygraph, streamlining data integration and reducing duplication. [Source]

What are the benefits of using Top-level Remote Fields?

Top-level Remote Fields offer several benefits, including:

[Source]

Does Hygraph support GraphQL APIs?

Yes, Hygraph provides a powerful GraphQL API that allows you to fetch and manage content efficiently. You can learn more about it at the Hygraph API Reference. [Source]

What integrations does Hygraph offer?

Hygraph offers a wide range of integrations, including:

For more details, visit the Hygraph Integrations page. [Source]

Technical Requirements

Are Top-level Remote Fields available on all Hygraph plans?

Yes, the new Top-level Remote Fields are available in all Hygraph plans, including the Community Tier. [Source]

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

You can access comprehensive technical documentation for Top-level Remote Fields and all Hygraph features at this documentation page and the main Hygraph Documentation. [Source]

Pricing & Plans

What is Hygraph's pricing model?

Hygraph offers a free forever Hobby plan, a Growth plan starting at $199/month, and custom Enterprise plans. For more details, visit the Hygraph pricing page. [Source]

Use Cases & Benefits

What problems does Hygraph solve for businesses?

Hygraph addresses operational pains (such as reliance on developers for content updates, outdated tech stacks, and clunky user experiences), financial pains (high operational costs, slow speed-to-market, expensive maintenance, and scalability challenges), and technical pains (boilerplate code, overwhelming queries, evolving schemas, and integration challenges). Hygraph's solutions include an intuitive interface, GraphQL-native architecture, content federation, and scalability. [Source]

Who can benefit from using Hygraph?

Hygraph is designed for developers, IT decision-makers, content creators, project/program managers, agencies, solution partners, and technology partners. It is especially beneficial for modern software companies, enterprises looking to modernize their technologies, and brands aiming to scale across geographies, improve development velocity, or re-platform from traditional solutions. [Source]

What are some real-world use cases for Top-level Remote Fields?

Top-level Remote Fields are ideal for scenarios where you need to federate multiple APIs into one, such as fetching product data from e-commerce systems (e.g., Shopify), digital assets from DAMs (e.g., Cloudinary), and rich content from Hygraph—all in a single query. This is especially useful for e-commerce, media, and multi-brand organizations that require unified content delivery without duplicating data across systems. [Source]

What business impact can customers expect from using Hygraph?

Customers can expect significant business impacts, including time-saving through streamlined workflows, ease of use with an intuitive interface, faster speed-to-market for digital products, and enhanced customer experience through consistent and scalable content delivery. These benefits help businesses modernize their tech stack and achieve operational efficiency. [Source]

Support & Implementation

How easy is it to get started with Hygraph and Top-level Remote Fields?

Getting started with Hygraph is straightforward. You can sign up for a free-forever account and access resources like the Hygraph Documentation, video tutorials, and onboarding guides. Top-level Remote Fields are available on all plans, and you can follow the detailed documentation to implement them quickly. [Source]

What support is available for implementing and troubleshooting Top-level Remote Fields?

Hygraph offers 24/7 support via chat, email, and phone. Enterprise customers receive dedicated onboarding and expert guidance. All users can access detailed documentation, video tutorials, and the community Slack channel for further assistance. [Source]

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 Compliant, ISO 27001 Certified, and GDPR compliant. These certifications ensure the highest levels of data protection and security for users. For more details, visit the Hygraph Security Features page. [Source]

What security features does Hygraph provide?

Hygraph provides enterprise-grade security features, including SSO integrations, audit logs, encryption at rest and in transit, and sandbox environments to protect sensitive data and meet regulatory standards. [Source]

Customer Success & Case Studies

Can you share some customer success stories using Hygraph?

Yes, Hygraph has several notable success stories. For example, Komax achieved a 3X faster time to market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement with a scalable platform, and Dr. Oetker enhanced their digital experience using MACH architecture. More case studies are available on the Hygraph Case Studies page. [Source]

What industries are represented in Hygraph's case studies?

Hygraph's case studies cover a wide range of industries, including Food and Beverage (e.g., Dr. Oetker), Consumer Electronics (e.g., Samsung), Automotive (e.g., AutoWeb), Healthcare (e.g., Vision Healthcare), Travel and Hospitality (e.g., HolidayCheck), Media and Publishing, eCommerce, SaaS (e.g., Bellhop), Marketplace, Education Technology, and Wellness and Fitness. [Source]

Product Information

What is the primary purpose of Hygraph?

Hygraph's primary purpose is to unify data and enable content federation, allowing businesses to create impactful digital experiences. Its GraphQL-native architecture removes traditional content management pain points and offers scalability, flexibility, and efficient data querying. [Source]

What is the overarching vision and mission of Hygraph?

Hygraph's vision is to unify data and enable content federation, empowering businesses to create impactful digital experiences. Its mission is to remove traditional content management pain points through a GraphQL-native architecture, taking the concept of a Headless CMS to the next level. [Source]

Velocity at Scale: Join the Launch of Hygraph’s Latest AI Innovations

Introducing Top-level Remote Fields

You can now directly fetch content from remote systems using one single Hygraph API, without the need to link remote content to content hosted in Hygraph.
Shahan Syed

Written by Shahan 

Jun 27, 2023
Mobile image

Our new top-level Federation capabilities allow you to connect multiple remote sources to Hygraph and query them directly through our API layer.

Rather than making multiple API calls to different systems, you can now fetch all content and data from a single Hygraph GraphQL endpoint.

Consider an e-commerce example, where you'd want to fetch product data from your commerce system (e.g. Shopify), digital assets from your DAM (e.g. Cloudinary), and rich content stored in Hygraph.

You can now fetch all of this data from Hygraph's content API, in one single query, for example:

query {
shopifyProducts {
title
description
totalInventory
onlineStoreUrl
}
cloudinaryAssets {
image {
url
}
}
blogArticles {
title
body
}
}

The benefits

  • Simplification: Simplify your tech stack by having all frontend applications query data from one universal Hygraph API.
  • Unification: Manage all your APIs in one place.
  • GraphQL and typesafe: Even if the underlying APIs are REST, the final endpoint to query data from is GraphQL.
  • Authentication and authorization: One API means a simpler process for authentication and authorization by frontend applications.
  • Low-code approach: Hygraph eliminates the need to write and maintain middleware code to stitch multiple systems together.
  • Content integrity: Eliminate duplicates and ensure that any changes are consistently reflected across all frontend applications the data is used at.
  • Performance improvements: Querying content from a single API and Hygraph's advanced caching capabilities allow for more high-performance distribution of content.

#How are the new top-level capabilities different?

Model-level Remote Fields

We previously offered model-level content federation capabilities that allowed you to enrich existing content in Hygraph with more information from a remote API on a field level.

This meant that you needed to have a content entry in Hygraph with a unique identifier present (such as an ID) that is common across the two systems, which is then passed as an input argument to fetch additional information from the remote API.

For example, you could fetch price data from a commerce system using the unique SKU code for each product. However, the SKU code needs to be stored as part of an entry in Hygraph.

query {
HygraphProduct {
sku #unique identifier in both APIs
ShopifyRemoteSource {
title
description
totalInventory
onlineStoreUrl
}
}

New Top-level Remote Fields

While content enrichment is important, we understand that there might be other cases where you need to federate multiple APIs into one, while ensuring data ownership stays within the external system and not be mirrored into another system.

The new top-level federation capabilities help here by streamlining the process further, allowing you to directly fetch content from remote systems using one single Hygraph API, without the need to have corresponding content entries in Hygraph.

Read the documentation

Both of our content federation capabilities serve their own purpose, and in combination help you distribute content stored across multiple systems, to any destination of choice, without duplication.

The new top-level remote sources are available in all Hygraph plans, including the Community Tier.

Get started by going through our detailed documentation, or feel free to reach out to us to get a consultation on how remote fields can drastically decrease the complexity of your stack.

Blog Author

Shahan Syed

Shahan Syed

Shahan is the Product Marketing Manager at Hygraph. Living in Pakistan, he loves to spend time exploring places, pencil sketching, reading, and watching science fiction and K-dramas.

Share with others

Sign up for our newsletter!

Be the first to know about releases and industry news and insights.