Frequently Asked Questions

Product Features & Capabilities

What is Hygraph and how does it work?

Hygraph is a GraphQL-native headless CMS designed to empower businesses to deliver digital experiences at scale. It enables multi-channel content delivery, integrates content from multiple sources, and streamlines content management through a marketer-friendly editorial UI. Hygraph supports both REST and GraphQL APIs, allowing developers to integrate with any frontend or application. Note: Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph support adding remote sources to the schema?

Yes, Hygraph allows you to add remote sources to your project schema. This enables the schema to include queryable types from external REST APIs, which can be fetched alongside Hygraph content. For example, you can connect a REST API using the Hygraph demo API and define custom type definitions using GraphQL SDL to expose external data in your GraphQL schema. Note: Only REST APIs are supported in the tutorial context; for other integrations, see the Marketplace Apps page.

What is Schema Definition Language (SDL) in Hygraph?

Schema Definition Language (SDL) is the syntax used to define types and their fields in a GraphQL schema. In Hygraph, SDL is used to describe the structure of data returned by remote sources, allowing Hygraph to expose those types in the project's GraphQL schema. Note: SDL is specific to GraphQL and may require technical familiarity.

What integrations are available with Hygraph?

Hygraph offers integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. These integrations enable scalable search, analytics, workflow automation, personalized marketing, and product data management. For a full list, visit the Marketplace Apps page. Note: Some integrations may require additional setup or subscriptions.

Does Hygraph provide APIs for content delivery and management?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs. This allows developers to integrate Hygraph with any frontend or application. For more details, see the API documentation. Note: API usage may require technical expertise.

Technical Requirements & Documentation

Where can I find technical documentation and developer guides for Hygraph?

Hygraph provides comprehensive technical documentation and developer guides, including a detailed Getting Started guide, advanced features, and tutorials. Access these resources at Hygraph Documentation. Note: Documentation is available online; some advanced topics may require prior GraphQL knowledge.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 certified since August 2022, uses ISO 27001-certified providers and data centers, and complies with GDPR and CCPA regulations. It offers encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. For more details, visit the security features page. Note: Some compliance requirements may depend on regional hosting options.

Implementation & Onboarding

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

Implementation timelines depend on project complexity. Simple use cases can start within a few days, while complex projects may take longer. Hygraph offers pre-configured starter projects, structured onboarding, extensive documentation, training resources, and community support via Slack (slack.hygraph.com). Note: Implementation speed may vary based on technical requirements and team expertise.

Performance & Scalability

What performance metrics and scalability features does Hygraph offer?

Hygraph features a high-performance CDN, global delivery capabilities, region-based hosting, advanced caching (Smart Edge Cache), and GraphQL-native architecture. Case studies include Gamescom supporting 3.5 million simultaneous sessions and 60 million API operations in three days, and Telenor achieving under 100ms latency on millions of API calls. Note: Performance may depend on chosen hosting region and API usage patterns.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Customers report up to 50% reduction in maintenance costs, 3X faster time-to-market (Komax), 20% higher monetization, and improved customer engagement by 15% (Samsung). Hygraph enables operational efficiency, scalability, and enhanced customer experiences. Note: Actual results may vary based on implementation and industry.

Which industries are represented in Hygraph's case studies?

Hygraph case studies span technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government (Statistics Finland), sports/events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific features may require custom configuration.

Pain Points & Solutions

What core problems does Hygraph solve?

Hygraph addresses dependency on developers, legacy tech stacks, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. Note: Some pain points may require custom workflows or integrations.

Customer Proof & Success Stories

Who are some notable customers of Hygraph?

Hygraph is used by Samsung (15% improved engagement), Coca-Cola, Epic Games, Telenor (under 100ms latency), Dr. Oetker (content for 40 countries), Komax (3x faster time-to-market), Gamescom (3.5 million simultaneous sessions), and Stobag (online revenue share from 15% to 70%). For more, see Hygraph Case Studies. Note: Customer outcomes may vary based on use case and implementation.

Target Audience & Use Cases

Who is the target audience for Hygraph?

Hygraph is designed for marketing/content teams, product managers, developers/engineers, and enterprise/IT teams. It is suited for industries such as technology, consumer goods, telecommunications, media, retail, e-commerce, and more. Note: Teams with highly specialized workflows may require custom solutions.

Limitations & Trade-Offs

Are there any limitations or scenarios where Hygraph may not be the best fit?

Hygraph's limitations are not publicly documented in detail. For edge cases or highly specialized requirements, it is recommended to consult Hygraph sales or technical support for specifics. Note: Always evaluate your use case against available features and integrations.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Lesson 5.1 - Add a remote source

In this lesson, you will add a remote source to the project schema. Before this step, the schema only returns data stored in Hygraph. After it, the schema includes queryable types from an external REST API that can be fetched alongside Hygraph content.

A remote source is a custom resolver entry point in the schema. It accepts field values from other Hygraph fields as arguments, which is what makes it possible to fetch reviews scoped to a specific product in lesson 5.2.

#Configure the remote source

You will connect a REST API using the Hygraph demo API.

Configuring the remote source
  1. Navigate to the Schema editor and click +Add next to Remote Sources.

  2. Fill in the following information:

    FieldInput
    Select remote source typeCustom source
    Display NameHyDemoAPI
    TypeREST
    Base URLhttps://demo-api.hygraph.workers.dev

    The base URL is the root endpoint for all remote fields that use this source. Individual remote fields append their own paths to this base.

  3. Click Add to save the remote source configuration before adding type definitions.

#Add custom type definitions

REST APIs return fixed data structures. To query a REST API as if it were native GraphQL, Hygraph needs to know the shape of the data it will receive. Custom type definitions provide that shape using GraphQL SDL.

  1. For each type definition, click +Add custom type definition and paste the snippets:

  2. Click Add Remote Source to save the configuration.

Your finished remote source should look like this:

Finished remote source

The Reviews type wraps a list of Review entries. These two types are used by the remote fields in lessons 5.2 and 5.3.

#What's next

Lesson 5.2 - Add remote fields

Or, go to the Tutorial overview for the full lesson list.