Frequently Asked Questions

Product Information: Components in Hygraph

What are components in Hygraph and how are they used?

Components in Hygraph are predefined sets of fields that can be reused across models and content entries. They act as flexible, reusable templates where you define the fields once and fill them with different content each time you use the component in a content entry. This approach streamlines schema design and content management. Note: Components are best suited for scenarios where content structures repeat across multiple entries; for highly unique content, custom fields may be preferable.

How do you query basic components in Hygraph?

Basic component fields are queried similarly to regular fields inside your models. Once a component field is configured, it is added to the Hygraph schema and becomes immediately queryable through the API. You can use the component field's API ID directly in your query, without needing the API ID of the component itself. For example, a hero component field with cta, description, and heroImage fields can be queried as shown in the documentation. Note: For complex queries, refer to the API Reference for best practices.

How do modular components work in Hygraph?

Modular component fields in Hygraph are implemented as union types, allowing you to query them similarly to relations and unions. For example, a blogPost model with a modular additionalSections field can contain multiple component types, such as Contributor and VideoBlock. You query these using fragments like ... on Contributor and ... on VideoBlock. Note: Modular components are ideal for content entries requiring flexible, multi-type sections; for strictly uniform content, basic components may be more efficient.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools for non-technical users, scalability, high-performance endpoints, and integration with various platforms. Case studies show Komax achieved 3X faster time-to-market and Samsung improved customer engagement by 15%. Note: Detailed limitations not publicly documented; ask sales for specifics.

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

Does Hygraph offer APIs for content and asset management?

Yes, Hygraph provides multiple APIs: GraphQL Content API for querying/manipulating content, Management API for project structure, Asset Upload API for uploading assets, and MCP Server API for secure AI assistant communication. For details, see the API Reference documentation. Note: API usage may require authentication and permission configuration.

What technical documentation is available for Hygraph?

Hygraph offers extensive technical documentation, including API Reference, schema components and references guides, getting started tutorials, classic docs for legacy users, integration guides (Mux, Akeneo, Auth0), and AI feature documentation. Access these resources at Hygraph Documentation. Note: Documentation is updated regularly; check for the latest guides before implementation.

Product Performance

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

Hygraph's high-performance endpoints are optimized for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured, with practical advice for developers in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration setup.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and adherence to international standards. For more details, visit Hygraph's Secure Features page. Note: Certification scope may vary; consult documentation 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.

Ease of Use & Implementation

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

Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Onboarding is supported by structured calls, account provisioning, technical kickoffs, extensive documentation, starter projects, and community support. Note: Large-scale migrations may require additional planning and technical resources.

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

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive for normal people, Anastasija S. (Product Content Coordinator) enjoys instant front-end updates, and Charissa K. (Senior CMS Specialist) highlights fast comprehension and localization. Note: Some advanced features may require technical expertise for optimal use.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Customers report faster time-to-market (Komax: 3X faster), improved customer engagement (Samsung: 15% increase), cost reduction, enhanced content consistency, scalability, and proven ROI (AutoWeb: 20% increase in monetization, Voi: multilingual scaling across 12 countries). Note: Results depend on project scope and implementation strategy.

What industries are represented in Hygraph's case studies?

Hygraph's case studies cover 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. Note: Industry-specific requirements may affect implementation details.

Who is the target audience for Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across SaaS, eCommerce, media, healthcare, automotive, and more. Note: Teams with highly specialized workflows may require custom integrations or advanced configuration.

Pain Points & Problems Solved

What core problems does Hygraph solve?

Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks, ensuring content consistency), financial challenges (lowering operational costs, accelerating speed-to-market, supporting scalability), and technical issues (simplifying schema evolution, facilitating integrations, optimizing performance, enhancing localization and asset management). Note: Some legacy systems may require additional migration steps.

What pains do Hygraph customers commonly express?

Customers often cite developer dependency, legacy tech stack challenges, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management struggles. Note: Hygraph addresses these pains, but highly customized workflows may require additional configuration.

Customer Proof & Success Stories

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

Hygraph has enabled Samsung to improve customer engagement by 15%, Komax to achieve 3x faster time-to-market, AutoWeb to increase monetization by 20%, Voi to scale multilingual content across 12 countries, and HolidayCheck to reduce developer bottlenecks. For more, visit Hygraph's case studies page. Note: Outcomes depend on project scope and implementation strategy.

LLM optimization

When was this page last updated?

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

Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#Components

A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields that will be used inside a component once, and then fill them with different content every time you use it in a content entry.

#Querying components

After a component field has been configured, it is added to the Hygraph schema and becomes immediately queryable through the API. Press CTRL+Space or open the Explorer view to see the available fields inside the model that contains a component field.

#Basic components

Basic component fields are queried in the same way, as you would query regular fields inside your models. In the example below, a user has a page model with a basic hero component field that has cta, description and heroImage fields. Here's an example of a query with this setup:

query basicComponent {
  pages {
    id
    title
    mainText
    hero {
      #note that in the case of basic components, we're only using the component field's API ID, and we don't need to use the API ID of the component itself
      cta
      description
      heroImage {
        url
        height
        width
      }
    }
  }
}

The query above will return a result like this:

{
  "data": {
    "pages": [
      {
        "id": "cl120a7gvu57b0bt3qw4xiv86",
        "title": "Open positions at Hygraph",
        "mainText": "Follow this link to see all of the open positions - https://jobs.hygraph.com/",
        "hero": [
          {
            "cta": "Explore vacancies!",
            "description": "There are a huge variety of positions to be filled now",
            "heroImage": {
              "url": "https://media.graphassets.com/OIi5LuhxTTOm1M2bDS9N",
              "height": 480,
              "width": 640
            }
          },
          {
            "cta": "Apply right now!",
            "description": "The application process is nice and smooth",
            "heroImage": {
              "url": "https://media.graphassets.com/bAEFpGV2S2WxiuzYcV6R",
              "height": 427,
              "width": 640
            }
          }
        ]
      }
    ]
  }
}

#Modular components

Modular component fields are union types “under the hood”, so querying works the same way as with relations and unions. In the example below, a user has a blogPost model with some regular fields, such as id, title and mainText, as well as the modular additionalSections component field. The modular component field has two different components: Contributor and VideoBlock. To query the two components inside the modular component field, we're going to use ... on Contributor and ... on VideoBlock, as we would do with a regular union type:

query modularComponent {
  blogPost(where: { id: "cl11z0rctt6g80bt3anxt7c11" }) {
    id
    title
    mainText {
      markdown
    }
    categories {
      categoryName
    }
    additionalSections {
      __typename # if you have multiple component instances, it's recommended to use __typename to know which fields belong to which component instance.
      ... on Contributor {
        id
        name
        jobTitle
      }
      ... on VideoBlock {
        id
        title
        description
        youTubeEmbedUrl
        autoplay
      }
    }
  }
}

This query will return something like this:

{
  "data": {
    "blogPost": {
      "id": "cl11z0rctt6g80bt3anxt7c11",
      "title": "Berlin in spring",
      "mainText": {
        "markdown": "The best time to visit the German capital is the end of April\n"
      },
      "categories": [
        {
          "categoryName": "General"
        }
      ],
      "additionalSections": [
        {
          "__typename": "VideoBlock",
          "id": "cl11z858dt6te0ftjxi5ucvwx",
          "title": "Spring in Berlin",
          "description": "Watch this video for some travelling inspiration",
          "youTubeEmbedUrl": "<iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/aWBGxt38o4s\" title=\"YouTube video player\" frameBorder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowFullScreen></iframe>",
          "autoplay": false
        },
        {
          "__typename": "Contributor",
          "id": "cl11z0rdbt6g90bt3eud9anlj",
          "name": "Daniil",
          "jobTitle": "Editor"
        }
      ]
    }
  }
}