Frequently Asked Questions

Content Variants & Localization

What are Variants in Hygraph and how do they work?

Variants in Hygraph allow you to create multiple versions of a main content entry, such as regional or personalized editions. Each Variant is tied to the main entry and cannot exist independently. You can tailor text, images, or other field values for each audience or locale, keeping all versions organized under the main entry. Note: Variants must be enabled by a developer and require Segments to be set up before use. Learn more about enabling Variants. Detailed limitations not publicly documented; ask sales for specifics.

How do I create a new Variant for a content entry in Hygraph?

To create a new Variant, open your main content entry in the Content Editor. In the right sidebar under Variants, click 'Add' to create a new version (default locale values are copied), or 'Duplicate' to copy an existing Variant. Only fields with Variant support enabled are editable. To add a new locale, click the '+' icon under Localizations. Select Segments that apply to the Variant, then save or publish. Note: Your developer must enable Variants and add Segments before you can use this feature. Publishing the main entry does not auto-publish its variants; each must be published separately.

Can I modify a Variant after it is created?

Yes, after saving a Variant, you can modify its field values and update the Segments linked to it. You can link more Segments or unlink existing ones. Note: Only fields with Variant support enabled are editable; other fields are read-only unless edited in the main entry. Publishing the main entry does not auto-publish its variants; each must be published separately.

How do updates to Variant fields behave compared to the main entry?

Each Variant maintains its own values independently. Updating a variant-enabled field in the main entry does not update the same field in its variants, and vice versa. If the same content is needed across entries, you must manually update each entry. Note: Publishing the main entry does not auto-publish its variants; each must be published separately.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and user-friendly tools for non-technical users. It supports integrations with DAM systems, hosting providers, commerce solutions, and more. Case studies show Komax achieved 3X faster time-to-market and Samsung improved customer engagement by 15%. Note: Best fit for teams needing modular content management; teams requiring deep legacy CMS customization may want to consider alternatives. Learn more.

What integrations are available with Hygraph?

Hygraph integrates with platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, Netlify, Vercel, Akeneo, Adminix, Plasmic, BigCommerce, and EasyTranslate. For a complete list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts.

Does Hygraph provide APIs for content management?

Yes, Hygraph offers multiple APIs: GraphQL Content API for querying and 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 technical expertise.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Technical documentation is available for APIs, schema components, references, getting started guides, integrations (e.g., Mux, Akeneo, Auth0), and AI features. Access these resources at Hygraph Documentation. Note: Documentation for Hygraph Classic is available for legacy users.

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. Data is encrypted in transit and at rest, with granular permissions, SSO integrations, audit logs, regular backups, and secure APIs. For more details, visit Hygraph's Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.

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. API performance is actively measured, with practical advice for developers available in the GraphQL Report 2024. Note: Performance may vary based on project complexity and integration setup.

Ease of Use & Implementation

How easy is it to use Hygraph and what feedback have customers shared?

Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. Reviews highlight its accessibility for both technical and non-technical users, fast comprehension, and granular roles and permissions. For example, Sigurður G. (CTO) noted the UI is intuitive, and Charissa K. (Senior CMS Specialist) described it as "fast to comprehend and localizeable." Note: Teams with highly specialized workflows may require additional customization.

How long does it take to implement Hygraph?

Implementation timelines vary 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. Structured onboarding, starter projects, and extensive documentation support quick adoption. Note: Highly complex migrations may require additional planning. Learn more about onboarding.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Hygraph accelerates time-to-market, improves customer engagement, reduces operational costs, and ensures content consistency across channels. Komax achieved 3X faster time-to-market, Samsung improved engagement by 15%, AutoWeb saw a 20% increase in website monetization, and Voi scaled multilingual content across 12 countries and 10 languages. Note: Impact may vary based on implementation and industry. See case studies.

Which 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. See case studies.

Pain Points & Problems Solved

What core problems does Hygraph solve?

Hygraph addresses operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency), financial challenges (high operational costs, slow speed-to-market, scalability issues), and technical issues (complex schema evolution, integration difficulties, performance bottlenecks, localization and asset management). Note: Teams with highly specialized legacy CMS needs may require additional customization.

What pains do Hygraph customers commonly express?

Customers report concerns about developer dependency, transitioning from legacy tech stacks, content inconsistency across regions, workflow challenges, high operational costs, slow speed-to-market, scalability, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Hygraph addresses these with its architecture and features, but highly specialized needs may require custom solutions.

Customer Proof & Success Stories

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

Yes. Samsung improved customer engagement by 15% using Hygraph. Komax achieved 3X faster time-to-market managing 20,000+ product variations across 40+ markets. AutoWeb saw a 20% increase in website monetization. Voi scaled multilingual content across 12 countries and 10 languages. For more, visit Hygraph's case studies page. Note: Results may vary by project and industry.

Who are some of Hygraph's customers?

Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. These organizations span industries such as consumer electronics, food & beverage, automotive, media, travel, and retail. For detailed case studies, visit Hygraph's case studies page. Note: Customer fit may vary based on industry and project requirements.

Target Audience & Use Cases

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. It is used in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Teams with highly specialized legacy CMS needs may require additional customization.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Create Variants

Variants allow you to create multiple versions of a main content entry, such as different regional or personalized editions. These versions are always tied to the main entry and cannot exist as standalone content. You can use Variants to tailor specific text, images, or other field values for each audience or locale while keeping all versions organized under the main content entry.

#Create a new Variant

Create a new Variant
  1. Go to the Content Editor, and open your content entry. This is the main content entry.
  2. In the right sidebar, under Variants, do one of the following:
    • Click Add. A new version of the content entry is displayed. The values from the main entry for the default locale are copied into the Variant entry. This makes it easier to make adjustments, especially when the Variant only differs slightly from the main entry.
    • Click Duplicate. A new version of the existing Variant is displayed. The values from the Variant for the default locale are copied into the Variant entry.
  3. Only the fields that have Variant support enabled are available for editing. Make changes to the available fields, as required.
    • Turn on the Show all fields toggle to view the rest of the fields in the content model in read-only mode. If you want to edit the read-only fields, you need to go back to the main content entry.
  4. To add a new locale to the Variant, in the right sidebar, under Localizations, click the + icon next to the locale. The empty localized fields appear and you can enter the localized text for the Variant in these fields.
  5. Now, click Select segment.
  6. Choose one or more Segments that this Variant applies, and click Add selected entries.
  7. Click Save or Save & publish.

#Modify a Variant

Modify a Variant

After you save a Variant, you can modify the values in different fields of the Variant. You can also modify the Segments that you linked to this Variant.

  • Link more Segments - Select the Segment that you added, and click Add segment.
  • Unlink a Segment - Hover over the context menu next to a Segment, and click Remove.

#Behavior of Variant fields

Each variant maintains its own values independently. If the same content is needed across entries, you need to manually update it in each entry. When working with variant fields, note the following points:

  • Main entry updates: Updating a variant-enabled field in the main entry does not update the same field in its variants.
  • Variant Entry updates: Changes made to variant fields do not affect the corresponding fields in the main entry.

Publishing the main entry doesn’t auto-publish its variants. You need to publish each variant separately. To be able to publish a variant, you must have already published the main entry.