Frequently Asked Questions

Product Information & Getting Started

What is Hygraph and what is its primary purpose?

Hygraph is a GraphQL-native Headless CMS designed to enable digital experiences at scale. Its primary purpose is to help businesses integrate multiple data sources and deliver content efficiently across channels, supporting modular and composable architectures. Hygraph addresses operational inefficiencies, reduces developer dependency, modernizes legacy tech stacks, and ensures content consistency through content federation. Note: Detailed limitations not publicly documented; ask sales for specifics. Source

How do I add components to models in Hygraph?

To add components to models in Hygraph, select your target model in the Schema, then add a Basic component or Modular component field from the right sidebar. For example, to add a Product Variant to the Product model, set the Display Name to "Product Variant", API ID to "ProductVariant", and select the appropriate component from the dropdown. For modular components (e.g., on a Landing Page), you can allow multiple values and select allowed components like "Call to Action" and "Product Grid". Note: The process may require schema planning for complex use cases. Source

What technical documentation is available for Hygraph users?

Hygraph provides extensive technical documentation, including API references, schema component guides, onboarding tutorials, integration guides (e.g., Mux, Akeneo, Auth0), and AI feature documentation. Classic documentation is also available for legacy users. Access all resources at https://hygraph.com/docs. Note: Some advanced use cases may require direct support or consultation. Source

Features & Capabilities

What are the key features and benefits of Hygraph?

Key features include GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, user-friendly tools for non-technical users, scalability, and integration capabilities with platforms like DAM, hosting, and commerce solutions. Hygraph is ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. Note: Some features may require higher-tier plans or custom configuration. Source

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 more. For a full list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts. Source

Does Hygraph offer APIs for content management and integration?

Yes, Hygraph provides several APIs: 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 AI assistant communication. Detailed API documentation is available at https://hygraph.com/docs/api-reference. Note: API usage may be subject to rate limits or authentication requirements. Source

How does Hygraph perform in terms of speed and reliability?

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. The read-only cache endpoint provides a 3-5x latency improvement for faster content delivery. Performance is actively measured, and developers can find optimization advice in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and infrastructure. Source

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 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 more details, visit Hygraph's Secure Features page. Source

What security features does Hygraph provide?

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, and automatic SSL certificates for all endpoints. Enterprise-grade guardrails include automatic backup and recovery and trusted data centers. Note: Some features may be available only on enterprise plans. Source

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. Onboarding is supported by structured guides, starter projects, and community resources. Users can sign up for free and access onboarding at https://hygraph.com/docs/getting-started. Note: Large-scale migrations may require additional planning. Source

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is suitable for developers, content creators, product managers, and marketing professionals. It serves enterprises and high-growth companies in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Teams with highly specialized CMS needs may require custom solutions. Source

What industries are represented in Hygraph's case studies?

Industries include 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. Source

Can you share specific customer success stories with Hygraph?

Yes. For example, Samsung improved customer engagement by 15%, Komax achieved 3x faster time-to-market, AutoWeb saw a 20% increase in website monetization, and Voi scaled multilingual content across 12 countries and 10 languages. More case studies are available at https://hygraph.com/case-studies. Note: Results may vary by implementation. Source

Pain Points & Problem Solving

What common problems does Hygraph solve for its users?

Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. Note: Some highly specialized requirements may need custom development. Source

Customer Feedback & Ease of Use

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

Customers praise Hygraph for its intuitive interface, quick adaptability, user-friendly setup, 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. Note: Some advanced features may require technical expertise. Source

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#3.2 Add components to your models

#Overview

#Adding the components to our models

In this step of the tutorial, we'll combine the models we created at the start with the components we created in the last lesson.

#Product

In this step, we'll add our Product Variant & Related product components to our Product model.

Let's start with Product Variant: We'll select the Product model on the Schema and add a Basic component field to it from the right sidebar.

We'll use the following information:

FieldInput
Display NameProduct Variant
API IDProductVariant
Select componentSelect Product Variant from the dropdown

Click Add to save your component.

We just created a basic component field that will allow us to select a product type with its own set of fields to complete every time we create a product entry.

For our related products section, we'll add a Basic component field from the right sidebar using this information:

FieldInput
Display NameRelated products
API IDrelatedProducts
DescriptionAdd related products
Select componentSelect Related products from the dropdown

Click Add to save your component.

We just created a basic component field containing the Related products component we configured before.

Your Product model should look like this:

Finished Product model with fieldsFinished Product model with fields

#Landing page

We're going to add a modular component to our Landing page, which we will later use to add CTA and Product grid as sections. Adding this as a modular component that allows multiple values will give us more flexibility in the future.

We'll select the Landing Page model on the Schema and add a Modular component field to it following the same steps as when we added a modular component in a previous lesson.

We'll use the following information:

FieldInput
Display NameStripes
API IDstripes
DescriptionSections
Field optionsSelect the Allow multiple values checkbox
Select allowed componentsSelect Call to Action & Product Grid from the dropdown

Click Add to save your component.

Your Landing page model should look like this:

Finished Landing Page model with fieldsFinished Landing Page model with fields

#Included in the project

In previous lessons, we looked into the Navigation model. This model was missing something: We need to be able to add links in order to create our e-commerce website navigation.

Later on, we created the Link component, where we added a reference that related it to the Blog post, Landing page, and Product models. This is the component we will now add to the Navigation model, so we can create the navigation links later.

Let's get into the Navigation model and add a Basic component field using the following information:

Complete basic componentComplete basic component

FieldInput
Display NameNav Link
API IDnavLink
DescriptionSections
Field optionsSelect the Allow multiple values checkbox. This will allow us to use it to create the navigation items for our e-commerce.
Select componentSelect Link from the dropdown

Click Add to save.

Now that our Navigation model is complete, it should look like this:

Finished Navigation modelFinished Navigation model

If we go to the content editor, we can see that the Navigation model lets us add references from the models we configured in the Link component, and because we can add multiple values, we can simply add the component as many times as we need to build the list of links that we want our navigation to have.

Navigation content entry creationNavigation content entry creation