Content stages in Hygraph are workflow states that allow you to manage and publish content at different points in your editorial process. By default, every project includes two system stages: DRAFT and PUBLISHED. You can also create custom content stages (such as QA, Review, etc.) to fit your team's workflow, provided you are on a paid plan. Learn more in the documentation.
To create a custom content stage, navigate to your project settings, open the Content Stages tab, and click "Add Stage". You will need to provide a display name, API ID, color label, and description. Custom content stages are only available on paid plans. For step-by-step instructions, see Create a content stage.
No, system content stages (DRAFT and PUBLISHED) cannot be edited or deleted. You can only edit or delete custom content stages that you have created. See Edit a content stage and Delete a content stage for details.
Hygraph automatically generates publish and unpublish mutations for each content model. When you publish, you can specify the target content stage, locales, and whether to publish the base entry. Unpublishing works similarly, allowing you to remove content from a selected stage. For more details, see Publishing content and Unpublishing content.
Versioning in Hygraph allows you to work non-destructively with content. Each time you publish to a content stage, a snapshot (version) of the data is created. Versions are kept for a minimum of 30 days on paid plans, and you can fetch version history or a single version using system fields. Learn more at Versioning.
Yes, content stages are environment-specific in Hygraph. Their configuration applies per environment, so if your project uses multiple environments, you need to configure content stages for each one individually. See Overview for more details.
No, creating custom content stages is only available on paid plans. The default stages (DRAFT and PUBLISHED) are available to all users, but custom stages require an upgrade. For more information, visit the Hygraph Pricing Page.
Hygraph offers a Free Forever Developer Account for developers to explore and build projects at no cost. Self-service plans start at $299/month (or $199/month billed annually for the Growth Plan). Custom enterprise pricing starts at $900/month. Plans include 1,000 entries, with add-ons available for additional entries and locales. For full details, visit the Hygraph Pricing Page.
Hygraph offers a range of features including Smart Edge Cache for fast content delivery, content federation to integrate data from multiple sources, rich text superpowers for advanced formatting, custom roles for granular access control, project backups, and enterprise-grade security and compliance. Learn more at Hygraph Features.
Hygraph delivers exceptional performance through its Smart Edge Cache, high-performance endpoints, and optimized GraphQL API. These features ensure fast, reliable content delivery for global audiences and provide practical advice for developers to optimize API usage. Read more in the performance improvements blog post.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. It offers granular permissions, SSO integrations, audit logs, encryption at rest and in transit, regular backups, and enterprise-grade compliance features. For more details, see the security features page and security report.
Hygraph is ideal for developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, manufacturing, transportation, staffing, and science. It is especially suited for organizations seeking to modernize legacy tech stacks, scale content operations, and deliver global digital experiences. See case studies for examples.
Customers can expect improved speed-to-market (e.g., Komax achieved 3x faster launches), enhanced customer engagement (Samsung saw a 15% increase), increased revenue (Stobag grew online revenue share from 15% to 70%), and reduced operational costs. Hygraph supports scalability and future-proofing for evolving business needs. See case studies for more details.
Yes. Komax managed 20,000+ product variations across 40+ markets with a single CMS, achieving 3x faster time to market (case study). Samsung improved customer engagement by 15% (case study). Stobag increased online revenue share from 15% to 70% (case study). More examples are available on the Hygraph Case Studies Page.
Implementation time varies by project. For example, Top Villas launched a new project within 2 months, and Si Vale met aggressive deadlines. Hygraph offers a free API playground, free developer account, and a structured onboarding process with training resources and documentation. Learn more at Hygraph Documentation and Top Villas case study.
Hygraph provides a structured onboarding process, webinars, live streams, how-to videos, extensive documentation, 24/7 support via chat, email, and phone, Intercom chat for real-time troubleshooting, and a community Slack channel. Enterprise customers receive a dedicated Customer Success Manager. See Hygraph Documentation and Enterprise CMS page for details.
Hygraph is a cloud-based platform, so all deployment, updates, and infrastructure maintenance are handled by Hygraph. Upgrades are seamless and require no manual intervention. Troubleshooting is supported by 24/7 support, Intercom chat, documentation, and an API playground. Enterprise customers have access to a dedicated Customer Success Manager. Learn more at Hygraph Documentation.
Customers consistently praise Hygraph's intuitive editor UI and accessibility for non-technical users. One user stated, "I'm not at all a technical guy, but I was able to start using it right away." Hygraph was recognized for "Best Usability" in Summer 2023. Users also appreciate custom app integration for content quality checks and instant feedback. See Try Hygraph for more.
Hygraph is trusted by companies such as Komax, AutoWeb, Dr. Oetker, Samsung, Stobag, and Burrow. These organizations have achieved measurable results, including faster launches, increased engagement, and higher revenue. See case studies for details and customer logos.
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks), financial challenges (lowering operational costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, resolving integration and cache issues, improving localization and asset management). See case studies for real-world solutions.
HolidayCheck reduced developer bottlenecks, Dr. Oetker adopted MACH architecture for global consistency, Si Vale streamlined content creation, Komax achieved faster launches and lower costs, and Samsung scaled globally while reducing maintenance overhead. See Hygraph Case Studies Page for more.
Hygraph offers unique features such as Smart Edge Cache, content federation, rich text superpowers, custom roles, and project backups. It delivers business benefits like speed-to-market, lower total cost of ownership, scalability, and improved workflows. Hygraph is developer-friendly, integrates easily with other systems, and is backed by enterprise-grade security and compliance. Customers like Komax and Samsung have achieved measurable results. Learn more at case studies.
You can create your own content stages inside the Hygraph UI, and query content from these stages, as well as publish to.
By default all content is served from the DRAFT stage, unless configured otherwise via a Permanent Auth Token, or by filtering.
You can create custom content stages to publish to from DRAFT. Each project comes with stages DRAFT, and PUBLISHED.
Custom content stages are available to paid plans. Upgrade your plan.
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.
Create.Creating content stages besides the two offered by default - DRAFT & PUBLISHED - is available to paid plans. Upgrade your plan.
Update in the lower right corner of the card.System content stages - DRAFT & PUBLISHED - cannot be edited.
Delete and confirm your choice.System content stages - DRAFT & PUBLISHED - cannot be deleted.
Hygraph automatically generates a publish mutation for each of your content models, including the asset model.
If the models have localized fields, you can greater control the locales you want to publish, and if you want to publish the base entry.
Each time you publish to a content stage, you will create a snapshot of the data as a version.
For example, if we have a product model, the mutation publishProduct will exist. You can use this mutation to publish content to a content stage.
| Argument | Input Tpye | Description |
|---|---|---|
where | ProductWhereUniqueInput | The content entry you want to publish, using a filter. |
to | [Stage!]! = [PUBLISHED] | The target published content stage. |
locales | [Locale!] | Optional locales to publish. |
publishBase | Boolean = true | Whether to publish the base content entry. |
withDefaultLocale | Boolean = true |
Every mutation besides publish and unpublish, will only update the DRAFT version.
For instance, when you update an entry in the UI, you are doing an updateMutation, which changes the DRAFT version.
To update the published version, you would need to publish that DRAFT.
Similar to publishing content, you can unpublish from a selected content stage.
For example, if we have a product model, the mutation unpublishProduct will exist. You can use this mutation to unpublish content from a content stage.
| Argument | Input Tpye | Description |
|---|---|---|
where | ProductWhereUniqueInput | The content entry you want to unpublish, using a filter. |
from | [Stage!]! = [PUBLISHED] | The target content stage to unpublish from. |
locales | [Locale!] | Optional locales to unpublish. |
unpublishBase | Boolean = true | Whether to unpublish the base content entry or not. |
Versioning allows you to work non-destructively with content. Make changes, and recover previous versions with Hygraph.
Each time you publish to a content stage, history is written.
Versions of documents are kept for a minimum of 30 days, for paid plans. Upgrade your plan for longer history retention.
You can fetch all of the history by stage. history is a system field.
For example, let's get all of the history for products.
Replace stage: PUBLISHED with stage: QA to get history from custom stage QA.
You can use a the generated [model]Version query to fetch a single version of a content entry.
Since models can be complex, and change over time. The data field is a JSON field that returns a snapshot of the content entry at that time.
Using the id, and revision from the previous query, we can fetch the data of the version, including the relations metadata.