Frequently Asked Questions

Content Modeling & Schema Design

How do I model products with variants in Hygraph for an e-commerce store?

Hygraph recommends using a single Product model with a modular component field called Product Variant. This approach allows you to select the relevant fields based on the product type (Clothing, Shoes, Accessories, or Decor) in the content editor. For example, shoes require a shoe size, clothing needs a clothing size, and accessories or decor only need color fields. This avoids creating separate models for each product type and keeps your schema flexible. Note: This method works best for stores with distinct product types; highly complex product catalogs may require additional customization. Source.

What enumerations are used for product sizes and colors in Hygraph's e-commerce schema?

The recommended enumerations for product sizes and colors are: Clothes size (XS, S, M, L, XL), Shoes size (Size_35 through Size_44), Wearable items color (Red, Green, Blue, Black, White), and Decor items color (Gold, Silver, Bronze, Cobalt). These enumerations help standardize product attributes for filtering and display. Note: Enumerations should be tailored to your store's inventory; custom values may be needed for unique products. Source.

How does Hygraph handle product reviews in an e-commerce schema?

Product reviews are not stored directly in Hygraph. Instead, reviews are fetched from an external REST API using Content Federation. This is configured as a Remote Field on the Product model and a Top-level Remote Field on the Query model. Review data appears in the API response alongside Hygraph content, avoiding data duplication and synchronization issues. Note: If your review source changes frequently, ensure your API integration is robust and monitored. Source.

Features & Capabilities

What are the key features of Hygraph for content modeling and management?

Hygraph offers a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), modular components for flexible schema design, enumerations for standardized attributes, and remote fields for integrating external data. It also provides a marketer-friendly editorial UI, localization workflows, and AI Assist for content generation and optimization. Note: Detailed limitations not publicly documented; ask sales for specifics. Source, Source.

Does Hygraph support API-first content delivery?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. This enables developers to integrate Hygraph with any frontend or application. Note: API rate limits and advanced usage scenarios may require enterprise support. Source.

What integrations are available with Hygraph?

Hygraph provides 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, personalization, and commerce experiences. For a full list, visit Hygraph Marketplace Apps. Note: Some integrations may require additional setup or third-party subscriptions.

Technical Requirements & Documentation

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

Hygraph provides comprehensive technical documentation, including getting started guides, advanced feature tutorials, and onboarding resources. Access these at Hygraph Documentation. Note: For highly specialized use cases, consult Hygraph support or community forums for additional guidance.

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

Implementation timelines vary by project complexity. Simple use cases can be started 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 to accelerate adoption. Note: Large enterprise migrations may require custom planning and technical assistance. Source.

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 is GDPR and CCPA compliant. It offers encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and global hosting options. Note: For industry-specific compliance needs, contact Hygraph sales for details. Source.

Performance & Scalability

How does Hygraph perform under high-traffic scenarios?

Hygraph's global CDN, region-based hosting, and Smart Edge Cache ensure fast and reliable content delivery. For example, Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Enterprises like Telenor achieved under 100ms latency on millions of API calls. Note: Performance may vary based on integration complexity and geographic distribution. Source, Source.

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), and up to 20% higher monetization on websites. Hygraph enables personalized and localized content delivery, improving customer engagement (Samsung saw a 15% improvement). Note: Results depend on implementation quality and organizational readiness. Source, Source.

Who are some notable customers of Hygraph?

Hygraph is used by Samsung (global content management, 15% engagement improvement), Coca-Cola (scalable content delivery), Epic Games (high-traffic operations), 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%). Note: Customer outcomes may vary based on project scope. Source.

What industries are represented in Hygraph's case studies?

Hygraph's 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 and public sector (Statistics Finland), sports and events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific requirements may necessitate custom schema design. Source.

Pain Points & Problem Solving

What core problems does Hygraph solve for content teams?

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/asset management challenges. Note: Teams with highly specialized workflows may require custom extensions or integrations. Source.

Target Audience & Use Cases

Who is the target audience for Hygraph?

Hygraph is designed for marketing and content teams, product managers, developers, engineering teams, and enterprise/IT professionals. It is particularly suited for companies in technology, consumer goods, telecommunications, media, retail, e-commerce, and other sectors where content management at scale is critical. Note: Small teams with limited technical resources may need additional onboarding support. Source.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#1.1 Design your content models

In this lesson, you will map the content structure the project requires before building anything in the schema editor. This lesson has no steps to complete in Hygraph. The decisions made here determine every field, reference, and component configured in the lessons that follow.

#The project

The e-commerce project sells wearables and home goods. Before opening the schema editor, you need to map the content structure against what the store must do.

Content modelingContent modeling

The store has four goals:

  • Display product listings with enough detail for a buyer to make a decision: image, size, color, price, description, and reviews.
  • Organize products into categories, where one product can belong to multiple categories and one category can contain multiple products.
  • Display related products on each product page to encourage further exploration.
  • Support a landing page, a blog, seller information, and a navigation structure.

Reviews come from an external source. You will not store them in Hygraph. Instead, you will fetch them from a remote API using Content Federation.

#Proposed content flow

Based on those goals, here is what the schema will contain.

Project structureProject structure

Models

ModelPurpose
ProductProduct listings with name, slug, images, description, price, and variant
Product categoryCategories that products can be assigned to
Blog postArticles promoting products
Seller informationBusiness details referenced from the landing page
Landing pageFlexible pages built from component sections
NavigationSite navigation built from Link components

Components

ComponentPurpose
Product VariantModular component for product type selection (Clothing, Shoes, Accessories, or Decor)
ClothingSize and color fields for clothing items
ShoesSize and color fields for footwear
AccessoriesColor field for accessories
DecorColor field for decor items
Related productsA set of product references for related product sections
Call to ActionHeading, body, image, and button for CTA sections
ButtonText and URL for use inside CTA components
Product GridHeadline, description, and product references for grid sections
LinkDisplay text, URL, and page reference for navigation links

Product Variant as a modular component, not separate models. The store sells clothing, shoes, accessories, and decor. Each product type requires different fields. Shoes need a shoe size, clothing needs a clothing size, accessories need neither. Rather than creating four separate product models, the schema uses a single Product model with a modular component field. The component presents only the relevant fields based on the product type selected in the content editor.

Enumerations

EnumerationValues
Clothes sizeXS, S, M, L, XL
Shoes sizeSize_35 through Size_44
Wearable items colorRed, Green, Blue, Black, White
Decor items colorGold, Silver, Bronze, Cobalt

Remote source

SourcePurpose
HyDemoAPIFetches product reviews from an external REST API. Configured as a Remote Field on the Product model and a Top-level Remote Field on the Query model.

Reviews as a remote field, not a model. Reviews exist in a third-party system. Migrating them into Hygraph would duplicate data and create a synchronization problem. A remote source connects to the origin directly. Review data appears in the API response alongside Hygraph content, with no migration required.

#What's next

Lesson 1.2 - Build your content models

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