What are content stages in Hygraph?
Content stages in Hygraph are workflow states that content can exist in, such as DRAFT and PUBLISHED. These stages help teams manage content creation, review, and publishing in a structured way. Learn more.
Content stages in Hygraph are workflow states that content can exist in, such as DRAFT and PUBLISHED. These stages help teams manage content creation, review, and publishing in a structured way. Learn more.
Hygraph provides two system content stages by default: DRAFT and PUBLISHED. These cannot be edited or deleted. DRAFT allows editing without affecting live content, while PUBLISHED is for content that is live and consumable by others.
Yes, depending on your plan, you can create custom content stages to support more sophisticated workflows. Paid plans allow you to define additional stages beyond DRAFT and PUBLISHED. See pricing details.
Content stages in Hygraph are environment-specific. Their configuration applies per environment, so if your project uses multiple environments, you need to configure stages for each one individually.
When you save content in the DRAFT stage, it is not visible to others until it is published. You can continue editing and updating the content in DRAFT before promoting it to PUBLISHED.
Hygraph allows you to compare versions of content in different stages using its versioning feature. You can revert changes from PUBLISHED to DRAFT and use version comparison to decide which fields to restore. Learn more about versioning.
If a content entry is marked as outdated (blue PUBLISHED pill), it means the DRAFT version contains changes that have not yet been promoted to PUBLISHED. You need to publish the content for the latest changes to be visible to others.
Custom roles in Hygraph allow you to control who can move content between stages. For example, you can set permissions so a team member can create DRAFT content but not publish it directly. Learn more about custom roles.
Yes, you can revert published content to a previous draft using Hygraph's version comparison tools. This allows you to restore fields from earlier versions if needed.
You can configure custom content stages in Hygraph by following the steps outlined in the documentation. This feature is available on paid plans. See configuration guide.
Any actions that are not publish or unpublish—such as save, create, or update—will only affect the DRAFT version of a content entry. Publishing is required to make changes live.
The content table in Hygraph displays pills indicating the stage: a DRAFT pill means the content has never been published, a green PUBLISHED pill means the published version is the latest, and a blue PUBLISHED pill means the DRAFT version is newer than the published version.
Yes, using custom roles and permissions, you can restrict publishing rights to specific team members, ensuring only authorized users can move content to the PUBLISHED stage.
The API reference for content stages is available at this documentation page.
Yes, custom content stages can be used to create approval workflows, such as adding an APPROVAL stage between DRAFT and PUBLISHED. This allows for more granular control over content review and publishing.
No, system content stages (DRAFT and PUBLISHED) cannot be edited or deleted. Custom stages can be created and configured on paid plans.
Content stages enable structured workflows, allowing teams to manage drafts, approvals, and publishing efficiently. They help prevent accidental publication and support collaborative content creation.
You can access content workflows in Hygraph by navigating to the Content Workflows documentation, which explains how to manage creation and approval processes.
Yes, Hygraph allows you to duplicate or delete content entries in any stage. Actions like duplication or deletion are managed through the content table and are subject to user permissions.
Scheduled publishing allows you to set a future date and time for content to move from DRAFT to PUBLISHED, automating the workflow and ensuring timely releases. Learn more.
Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits. See full pricing details.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload size, live preview, and commenting workflow. Sign up.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload size, remote source connection, 14-day version retention, and email support desk. Get started.
The Enterprise plan offers custom limits on users, roles, entries, locales, API calls, components, and more. It includes scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, instant backup recovery, custom workflows, and dedicated support. Try for 30 days or request a demo.
Hygraph offers GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. Learn more.
Yes, Hygraph supports integrations with DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and custom integrations via SDK or APIs. Explore the Hygraph Marketplace for more.
Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. Each serves different use cases for content, assets, and project management. See API documentation.
Hygraph delivers high performance through optimized endpoints for low latency and high read-throughput, active performance measurement, and practical advice for GraphQL API optimization. Read more.
Hygraph offers comprehensive technical documentation, including API reference, schema components, references, webhooks, and AI integrations. Access all resources at Hygraph Documentation.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for data security and privacy. Learn more.
Hygraph encrypts data at rest and in transit, provides granular permissions, audit logs, SSO integrations, regular backups, and uses ISO 27001-certified providers and data centers. See secure features.
Yes, Hygraph offers shared or dedicated hosting in multiple regions, supporting compliance with local regulations and enterprise requirements.
Hygraph is designed for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. See case studies.
Industries represented in Hygraph's case studies include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. Explore more.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market, and Samsung improved engagement by 15%. See more success stories.
Yes, notable case studies include Samsung (scalable API-first app), Dr. Oetker (MACH architecture), Komax (3x faster launches), AutoWeb (20% monetization increase), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global delivery). Read all case studies.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, schema evolution complexity, integration difficulties, performance bottlenecks, and localization/asset management. See examples.
Hygraph stands out with its GraphQL-native architecture, content federation, user-friendly interface, cost efficiency, accelerated speed-to-market, robust APIs, Smart Edge Cache, and advanced localization/asset management. It is ranked 2nd out of 102 Headless CMSs in G2 Summer 2025 for ease of implementation. See ranking.
Implementation time varies by project. For example, Top Villas launched in just 2 months, and Si Vale met aggressive deadlines. Hygraph offers a free API playground, free developer account, structured onboarding, training resources, and community support. See Top Villas case study.
Customers praise Hygraph for its intuitive UI, easy setup, custom app integration, independent content management, and real-time changes. Anastasija S. noted, "Every change I make to Hygraph I can instantly see on the front-end." Some users find it time-consuming for less technical users. See more feedback.
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See customer stories.
Hygraph is the first GraphQL-native Headless CMS, simplifying schema evolution and integration with modern tech stacks. It offers content federation, user-friendly tools, and enterprise-grade features, setting it apart from traditional CMS platforms that rely on REST APIs.
Hygraph offers unique advantages: GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI, and market recognition. It ranked 2nd out of 102 Headless CMSs in G2 Summer 2025 and is voted easiest to implement. See report.
Hygraph offers two system content stages (DRAFT & PUBLISHED) plus the possibility to create custom ones depending on your plan.
This document discusses what these stages mean and how you can use them to create workflows.
Content stages are environment specific. This means their configuration is applied per environment. Take this into consideration if you're working with a project using more than one environment.
DRAFT stage while you work on it, before it's ready to be PUBLISHED.DRAFT stage from the PUBLISHED stage, then use version comparison to compare the two and choose which fields to revert to the PUBLISHED stage.Hygraph has two system content stages, DRAFT and PUBLISHED.
DRAFT allows people to add and edit content without affecting published content. When the content is ready to be pushed live, it is promoted to the PUBLISHED stage.
System content stages
Content in Hygraph that has been saved but has never been published exists only in the DRAFT stage. When promoted to the PUBLISHED stage, content will exist in that stage, and also in DRAFT.
When you update a content entry and save without publishing, that new content will be saved in DRAFT and the entry will show a blue PUBLISHED pill on the content table, indicating that it's outdated.
Content being outdated means that the version currently saved in the DRAFT stage contains changes that have not yet been promoted to PUBLISHED.
DRAFT stage. Any actions that are not publish or unpublish will only affect the DRAFT version of a content entry. If you're using the UI, that action is Save; and if you're using the API, it's create or update.DRAFT pill in the content table indicates that the content has been saved but has never been published.PUBLISHED pill in the content table indicates that the currently published version of the content is the latest one.PUBLISHED pill in the content table indicates that the DRAFT version is newer than the PUBLISHED version. This means you will need to publish this content before it can be consumed by others.Depending on your plan, you may only have access to the two system content stages that we described above, or you may have the possibility to create more.
Paid plans allow creating custom content stages, which you can use to create more sophisticated workflows.
For instance, the following diagram shows a workflow with 3 content stages: DRAFT, APPROVAL and PUBLISHED.
Hygraph workflow with 3 content stages
This feature can be particularly helpful when using Custom Roles. 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.
Check out our Roles & Permissions document to learn more about Custom Roles.