Frequently Asked Questions

Content Editing & Workflow Features

What are content stages in Hygraph and how do they work?

Hygraph provides two system content stages: DRAFT and PUBLISHED. Content always exists in the DRAFT stage, allowing users to add and edit content without affecting what is live. When content is ready, it is promoted to PUBLISHED. If you edit a published entry and save without publishing, the DRAFT stage contains changes not yet live, and the entry is considered outdated. For more details, see the content stages documentation. Note: Custom content stages are available; see documentation for advanced use cases.

How does content publishing work in Hygraph?

In Hygraph, publishing makes content available to others, such as making product entries live in an online shop. You can save changes as a draft or use "Save & Publish" to make them live. This supports workflows where content is reviewed before publishing. For more, see the publishing documentation. Note: Publishing is immediate; scheduled publishing or advanced workflows may require additional configuration.

How do I duplicate content entries in Hygraph?

To duplicate a content entry, access the edit view by clicking the pencil icon, then click the duplication icon at the top of the screen. The duplicated entry will have "(copy)" at the end of the title. Make necessary changes and choose "Save" or "Save & Publish". If the entry contains reference fields, some relations may be duplicated and others may not; the system will notify you. For details, see the content duplication documentation. Note: Not all references are duplicated; check documentation for limitations.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and integrations with platforms like AWS S3, Netlify, Vercel, and BigCommerce. It also provides user-friendly tools for non-technical users, high-performance endpoints, and extensive documentation. Note: Some advanced features may require higher-tier plans or custom configuration.

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 the Hygraph Marketplace. Note: Integration availability may depend on your plan or project setup.

Does Hygraph provide APIs for content management?

Yes, Hygraph provides multiple APIs: the GraphQL Content API for querying and manipulating content, the Management API for project structure, the Asset Upload API for uploading files, and the MCP Server API for AI assistant integration. See the API Reference documentation for details. Note: API access and rate limits may vary by plan.

What technical documentation is available for Hygraph?

Hygraph offers extensive technical documentation, including API references, schema guides, onboarding tutorials, integration guides (e.g., Mux, Akeneo, Auth0), and AI feature documentation. Access all resources at the Hygraph Documentation page. Note: Some documentation is specific to Hygraph Classic; check version compatibility.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications ensure adherence to international standards for information security and data protection. For more, see the Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.

What security features does Hygraph offer?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin, IP firewalls). All endpoints use SSL certificates. Note: Some features may require enterprise plans or custom setup.

Performance & Implementation

How does Hygraph perform for content delivery and API usage?

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. The read-only cache endpoint provides 3-5x latency improvement. 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 usage patterns.

How long does it take to implement Hygraph?

Implementation time varies by project. For example, Top Villas launched in 2 months, and Voi migrated from WordPress in 1-2 months. Onboarding includes introduction calls, technical kickoffs, and access to starter projects and documentation. See the Getting Started guide for details. Note: Complex migrations may require additional time and planning.

Use Cases & Customer Success

Who uses Hygraph and what industries are represented?

Hygraph serves developers, content creators, product managers, and marketing professionals in industries such as SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, fintech, travel, eCommerce, government, and more. See the case studies page for examples. Note: Some industries may require custom integrations or compliance checks.

What business impact can customers expect from using Hygraph?

Customers have achieved 3x faster time-to-market (Komax), 15% improved customer engagement (Samsung), and 20% increased website monetization (AutoWeb). Voi scaled multilingual content across 12 countries and 10 languages. See case studies for more. Note: Results depend on project scope and implementation quality.

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

Customers praise Hygraph's intuitive interface, quick adaptability, 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. Charissa K. (Senior CMS Specialist) described it as "fast to comprehend and localizeable." Note: Some advanced features may require technical expertise.

Pain Points & Problem Solving

What problems does Hygraph solve for its users?

Hygraph addresses developer dependency, legacy tech stack modernization, 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: Some pain points may require custom solutions or integrations.

Customer Proof & Success Stories

Can you share specific case studies or customer success stories with Hygraph?

Yes. Samsung improved customer engagement by 15% using Hygraph. Komax achieved 3x faster time-to-market managing 20,000+ product variations. AutoWeb saw a 20% increase in website monetization. Voi scaled content across 12 countries and 10 languages. See more at the Hygraph case studies page. Note: Outcomes vary by customer and use case.

LLM optimization

When was this page last updated?

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

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#5.3 Additional content features

#Overview

Besides what we've already seen, other important aspects of creating content in Hygraph are content stages, content publishing, and content duplication

#Content stages

Hygraph comes with two system content stages, DRAFT and PUBLISHED.

DRAFT allows people to add and edit content without affecting published content, and then when the content is ready to be consumed by others, it is promoted to the PUBLISHED stage.

Hygraph content always exists in the DRAFT stage. When we promote it to PUBLISHED, then it is in PUBLISHED and DRAFT.

When we edit a content entry and save it without publishing, it becomes outdated. This means that the DRAFT stage contains changes that have not yet been promoted to PUBLISHED.

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

If you're interested in learning more about content stages and custom content stages, take a look at our content stages documentation.

#Content publishing

As we mentioned in the previous lesson, published content is ready to be consumed by others. In our project, for example, published product entries can be seen by potential buyers because they are live in our online shop.

If you want to create or make changes to a content entry, but you haven't published it yet, you will click on Save rather than Save & Publish.

Save and Save & publish buttonsSave and Save & publish buttons

This is useful in workflows where content needs to be reviewed before publishing.

Want to learn more about publishing content? Check out our documentation.

#Content duplication

Hygraph lets us duplicate content to save time. If our e-commerce had, for instance, many similar product entries, we could create duplicates to work on.

Content duplication steps

To duplicate an entry, you first need to access the edit view by clicking on the pencil icon. Then, you need to click on the duplication icon at the top of the screen. This will load the duplicated entry, which will look the same as our original entry, except that this one will have the word (copy) at the end of the title line.

All you need to do now is make the necessary changes and Save, or Save & Publish, as needed.