Frequently Asked Questions

Content Stages & Editorial Workflow

What are content stages in Hygraph and how do they affect my frontend?

Content stages in Hygraph determine what the Content API returns and what your frontend displays. There are two system stages: DRAFT and PUBLISHED. Every content entry starts in DRAFT. When you click Save & Publish, the entry is promoted to PUBLISHED and exists in both stages. Editing a published entry and saving without publishing makes the entry outdated; the DRAFT stage contains changes not yet promoted, while the frontend continues to show the last published version. Note: Only entries in PUBLISHED are visible to unauthenticated public access. Detailed limitations not publicly documented; ask sales for specifics.

How do Save and Save & Publish actions work in Hygraph?

"Save" stores changes in the DRAFT stage only, keeping the published version unchanged. Use this when content needs review before going live. "Save & Publish" stores changes in DRAFT and promotes them to PUBLISHED simultaneously, making them available to the frontend. If you use "Save" only, entries will not appear in responses configured for the PUBLISHED stage. Note: If your frontend is missing content, check whether the relevant entries have been published. Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph support custom content stages?

Yes, Hygraph supports custom content stages, such as a Review stage between DRAFT and PUBLISHED for editorial workflows requiring approval before publishing. For more details, see Content stages documentation. Note: Custom stages may require additional configuration and permissions. Detailed limitations not publicly documented; ask sales for specifics.

How does content duplication work in Hygraph?

Hygraph lets you duplicate content entries to save time when creating similar entries. To duplicate an entry, open it in the edit view and click the duplication icon. The duplicate loads with the same field values as the original, with (copy) appended to the title. If a duplicated entry contains reference fields, some relations are duplicated and others are not; the system notifies you when this occurs. For details, see Duplicating content documentation. Note: Not all relations are preserved during duplication. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, rich editing capabilities, localization, scalability, speed-to-market, enhanced customer experience, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), AI Assist for content generation and optimization, and proven ROI with case studies like Komax (3X faster time-to-market) and Samsung (15% improved engagement). Note: Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph provide APIs for integration?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. Developers can integrate Hygraph with any frontend or application. For more details, see API documentation. Note: API usage may require configuration of permissions and tokens. Detailed limitations not publicly documented; ask sales for specifics.

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. For a full list, visit Marketplace Apps page. Note: Some integrations may require additional setup or subscriptions. Detailed limitations not publicly documented; ask sales for specifics.

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 24/7 infrastructure monitoring. For more details, visit security features page. Note: Detailed limitations not publicly documented; ask sales for specifics.

Performance & Scalability

How does Hygraph perform under high-traffic scenarios?

Hygraph's global CDN minimizes latency and supports region-based hosting. It handled 3.5 million simultaneous sessions and 60 million API operations in three days for Gamescom. Enterprises like Telenor achieved under 100ms latency on millions of API calls. Smart Edge Cache optimizes content delivery for low latency and high read-throughput. Note: Best fit for high-traffic use cases; teams needing specialized caching or custom CDN may want to consider alternatives.

Implementation & Onboarding

How long does it take to implement Hygraph?

Implementation timelines depend on project complexity. Simple use cases can start within a few days. Structured onboarding, pre-configured starter projects, and extensive documentation help accelerate setup. For more complex implementations, timelines may extend, but onboarding support is available. Note: Best fit for teams seeking rapid deployment; highly customized projects may require additional time.

What technical documentation is available for Hygraph?

Hygraph provides comprehensive technical documentation, including getting started guides, advanced tutorials, and developer resources. Access documentation at Getting Started Documentation. Note: Documentation covers most use cases; highly specialized scenarios may require direct support.

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 15% improved customer engagement (Samsung). Hygraph supports high-traffic use cases (Gamescom: 3.5 million sessions, 60 million API ops), global content management (Dr. Oetker: 40 countries), and operational efficiency (HolidayCheck: eliminated developer bottlenecks). Note: Best fit for teams seeking measurable ROI; teams with highly specialized requirements may need additional evaluation.

Who are some notable customers of Hygraph?

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

What industries are represented in Hygraph's case studies?

Industries include 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 requirements may require tailored solutions.

Pain Points & Problems Solved

What problems does Hygraph solve for its customers?

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. Teams benefit from multi-channel reuse, AI-assisted optimization, flexible schema modeling, and global CDN. Note: Best fit for teams seeking modernization; highly specialized legacy integrations may require custom solutions.

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 companies in technology, consumer goods, telecommunications, media, retail, e-commerce, and more. Note: Teams with highly specialized requirements may need additional evaluation.

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

#6.3 Understand content stages

Content stages in Hygraph are not just an editorial workflow feature. They determine what the Content API returns and what your frontend displays. Understanding this now prevents the most common source of confusion when connecting the frontend in lesson 8.

#DRAFT and PUBLISHED

Hygraph provides two system content stages: DRAFT and PUBLISHED.

Every content entry starts in DRAFT. When you click Save & Publish, the entry is promoted to PUBLISHED. At that point, the entry exists in both stages simultaneously. DRAFT always reflects the current state of the entry, and PUBLISHED reflects the last published version.

When you edit a published entry and click Save without publishing, the entry becomes outdated. The DRAFT stage contains changes that have not yet been promoted to PUBLISHED. The published version on the frontend remains unchanged until you publish again.

Table showing content in stages DRAFT, PUBLISHED, and outdatedTable showing content in stages DRAFT, PUBLISHED, and outdated

The API consequence: Hygraph uses a single Content API endpoint. Which stage you read depends on how access is configured via public permissions, a Permanent Auth Token (PAT), or stage headers and query parameters. Unauthenticated public access with default permissions only returns entries that have been published. If an entry has never been published, those requests return no data for that entry.

In lesson 8.2, you will configure a Permanent Auth Token (PAT) that grants the frontend access to draft content for preview purposes. The public storefront uses unauthenticated access configured for the PUBLISHED stage. Understanding the distinction now means that when you see different results in the API Playground versus the frontend, you will know why.

#Save vs Save & Publish

Every time you create or edit a content entry, you choose between two actions:

  • Save stores the changes in the DRAFT stage only. The published version is not updated. Use this when content needs review before going live.
  • Save & Publish stores the changes in DRAFT and promotes them to PUBLISHED simultaneously. Use this when content is ready to be consumed by the frontend.

Save and Save & publish buttonsSave and Save & publish buttons

All entries created in lesson 6.1 used Save & Publish, which means they exist in both DRAFT and PUBLISHED. If you used Save only at any point, those entries will not appear in responses configured for the PUBLISHED stage, including in the connected storefront.

#Content duplication

Hygraph lets you duplicate content entries to save time when creating similar entries.

To duplicate an entry, open it in the edit view and click the duplication icon at the top of the screen. The duplicate loads with the same field values as the original, with (copy) appended to the title field.

Content duplication

#What's next

Lesson 7 - Queries and mutations

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