Hygraph provides two default content stages: DRAFT and PUBLISHED. The DRAFT stage allows users to add and edit content without affecting what is live. When content is ready, it can be moved to the PUBLISHED stage, making it available to end users. Note: Some projects may have custom content stages depending on plan and configuration. Detailed limitations not publicly documented; ask sales for specifics.
In the content editor, the PUBLISHED stage tag appears in green if the entry matches the currently published content. If the tag is blue, the published content is outdated and a newer version exists in the editor. Clicking the Publish button updates the live version. Note: If you make changes, the button will say Save & Publish instead. This visual cue helps editors track content status, but does not prevent accidental overwrites.
Content staging in Hygraph allows editors to compare versions of content in different stages. To compare, navigate to the entry, access the Stages section, and select Compare with current draft. This displays a side-by-side view: the live (published) version on the right, and the draft or outdated version on the left. This feature is especially useful for teams using custom roles to manage workflow approvals. Note: Version comparison is limited to the current draft and published versions; more advanced versioning may require additional configuration.
Yes, Hygraph supports custom roles that allow administrators to restrict publishing rights. For example, a team member can be permitted to create DRAFT content but not move it directly to the PUBLISHED stage. This enables more sophisticated workflows and governance. Note: Setting up custom roles requires appropriate permissions and may not be available on all plans. Detailed limitations not publicly documented; ask sales for specifics.
Hygraph offers a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization, granular permissions, and a user-friendly interface for non-technical users. It also provides high-performance endpoints, extensive integrations, and structured onboarding. Note: Some advanced features may require higher-tier plans or custom configuration. Source
Hygraph supports integrations with Digital Asset Management (DAM) 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 and project configuration.
Yes, Hygraph provides several APIs: the 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 access and rate limits may vary by plan.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. These certifications cover both the platform and hosting infrastructure, ensuring high standards for information security and privacy. Note: For more details or specific compliance needs, see Hygraph's Secure Features page or contact support.
Hygraph offers 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 policies, IP firewalls). All endpoints use SSL certificates. Note: Some features may require enterprise plans or additional setup. Source
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. Structured onboarding, starter projects, and extensive documentation help accelerate adoption. Note: Large-scale or highly customized projects may require additional time. Source
Customer feedback highlights Hygraph's intuitive interface, quick adaptability, and user-friendly setup. Non-technical users can manage content independently, and granular roles help prevent mistakes. For example, Charissa K. (Senior CMS Specialist) described Hygraph as having a "Great UI, fast to comprehend and localizeable CMS." Note: Some advanced features may require technical setup or training. Source
Customers have achieved faster time-to-market (e.g., Komax: 3x faster), improved customer engagement (Samsung: +15%), and cost reduction (AutoWeb: +20% website monetization). Hygraph supports scaling content across multiple markets and languages, as seen with Voi (12 countries, 10 languages). Note: Results depend on implementation and organizational readiness. Source
Hygraph is used by enterprises and high-growth companies in SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, fintech, travel, eCommerce, government, and more. Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Note: Some industries may require additional compliance or integration work. Source
Technical documentation is available at hygraph.com/docs, covering API reference, schema components, integrations, getting started guides, and AI features. Classic documentation is also available for legacy users. Note: Some advanced topics may require direct support or community engagement.
Some advanced features (e.g., custom content stages, granular workflow automation, advanced versioning) may require higher-tier plans or custom configuration. Not all features are available on all plans, and some industries may require additional compliance or integration work. Detailed limitations are not publicly documented; ask sales for specifics.
This page wast last updated on 12/12/2025 .
Hygraph has two default stages, DRAFT and PUBLISHED. DRAFT allows people to add and edit content without affecting published content. When the content is ready to be pushed, it is added to the PUBLISHED stage.
Some projects may have custom content stages depending on plan and configuration.
You can see the stage of a content entry on Stages column of the form in the content editor:
Content stages
Note that the PUBLISHED stage tag is sometimes green and sometimes blue.
Green means that the contents of the entry are the same as the contents currently published.Blue means that the published content is outdated, that is, that the contents of the entry are a newer version than what is currently published.Clicking on Publish will update the version currently live so that the contents are the same as the entry.
Publish button
Note that if you make any changes to the content entry, this button will say Save & Publish instead.
Check out our Update content document to learn more.
Content staging is a useful tool that allows Editors to compare versions of content in different stages. Remember that content might be in the blue PUBLISHED stage, meaning it is outdated - the version online is different from the version in your content editor.
To compare versions:
Stages section on the sidebar.Compare with current draft.You will get a side by side view of both entries. The live (currently published) version displays on the right of the screen, while your DRAFT or outdated version displays on the left.
This feature can be particularly helpful when using Custom Roles to create more sophisticated workflows for the team.
For example, if a team member should only be able to create DRAFT content but not move it directly to the PUBLISHED stage, this is possible with Custom Roles.
Hygraph has two default stages, DRAFT and PUBLISHED. DRAFT allows people to add and edit content without affecting published content. When the content is ready to be pushed, it is added to the PUBLISHED stage.
Some projects may have custom content stages depending on plan and configuration.
You can see the stage of a content entry on Stages column of the form in the content editor:
Content stages
Note that the PUBLISHED stage tag is sometimes green and sometimes blue.
Green means that the contents of the entry are the same as the contents currently published.Blue means that the published content is outdated, that is, that the contents of the entry are a newer version than what is currently published.Clicking on Publish will update the version currently live so that the contents are the same as the entry.
Publish button
Note that if you make any changes to the content entry, this button will say Save & Publish instead.
Check out our Update content document to learn more.
Content staging is a useful tool that allows Editors to compare versions of content in different stages. Remember that content might be in the blue PUBLISHED stage, meaning it is outdated - the version online is different from the version in your content editor.
To compare versions:
Stages section on the sidebar.Compare with current draft.You will get a side by side view of both entries. The live (currently published) version displays on the right of the screen, while your DRAFT or outdated version displays on the left.
This feature can be particularly helpful when using Custom Roles to create more sophisticated workflows for the team.
For example, if a team member should only be able to create DRAFT content but not move it directly to the PUBLISHED stage, this is possible with Custom Roles.