What are the key new features in the latest version of Hygraph?
The latest version of Hygraph introduces a new GraphQL core engine with performance gains of up to 40x in response times, and up to 100x for complex queries. New features include content stages (draft and published, with custom stages coming soon), union types (polymorphic relations), sortable relations and assets, advanced filters, granular webhooks, and a redesigned API playground with statement history. Note: Custom content stages and UI extensions are planned for future releases; current limitations may apply for highly specialized workflows. Source
How does Hygraph's GraphQL-native architecture benefit users?
Hygraph's GraphQL-native architecture simplifies schema evolution, enables seamless integration with modern tech stacks, and supports complex content structures through union types and polymorphic relations. This approach reduces boilerplate code and makes it easier for developers to manage APIs and datasets. Note: Teams unfamiliar with GraphQL may require additional onboarding time. Source
What performance improvements have been made in Hygraph?
Hygraph's new GraphQL core engine delivers up to 40x faster response times, with some complex queries achieving nearly 100x speed gains. The platform also features high-performance endpoints, a read-only cache endpoint with 3-5x latency improvement, and optimized API throughput. Note: Performance may vary based on query complexity and project size. Source
What integrations are available with Hygraph?
Hygraph offers 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 other tools (Adminix, Plasmic). For a full list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts. Source
Does Hygraph provide APIs for content and asset management?
Yes, Hygraph provides multiple APIs: GraphQL Content API for querying/manipulating content, Management API for project structure, Asset Upload API for uploading files, and MCP Server API for secure AI assistant communication. Detailed documentation is available at API Reference. Note: API usage may require authentication and permissions setup. Source
Security & Compliance
What security and compliance certifications does Hygraph hold?
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. The platform also adheres to the German Data Protection Act (BDSG) and Telemedia Act (TMG). Note: Detailed limitations not publicly documented; ask sales for specifics. Source
What security features are included in Hygraph?
Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, secure API policies (custom origin, IP firewalls), and SSL certificates for all endpoints. Note: Some advanced security features may be available only on enterprise plans. Source
Implementation & Onboarding
How long does it take to implement Hygraph?
Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Note: Highly customized migrations may require additional planning. Source
How easy is it to start using Hygraph?
Hygraph offers a smooth onboarding process with free account signup, structured onboarding (introduction calls, account provisioning, technical kickoffs), extensive documentation, starter projects, community Slack, and training resources (webinars, live streams, how-to videos). Note: Teams with legacy systems may require additional migration support. Source
Ease of Use & Editorial Experience
What feedback have customers given about Hygraph's ease of use?
Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Reviews highlight instant front-end updates, clear setup, granular roles/permissions, and enhanced editor experience. Note: Some advanced features may require technical knowledge for optimal use. Source
Use Cases & Target Audience
Who is the target audience for Hygraph?
Hygraph serves developers, content creators, product managers, and marketing professionals. It is ideal for enterprises and high-growth companies in SaaS, eCommerce, media, healthcare, automotive, and more. Note: Small teams with limited technical resources may need additional onboarding support. Source
What industries are represented in Hygraph's case studies?
Can you share specific case studies or success stories of customers using Hygraph?
Hygraph has enabled Samsung to improve customer engagement by 15%, Komax to achieve 3x faster time-to-market, AutoWeb to increase website monetization by 20%, Voi to scale multilingual content across 12 countries and 10 languages, and HolidayCheck to reduce developer bottlenecks. For more, visit Hygraph's case studies page. Note: Results may vary based on project scope and implementation. Source
Who are some of Hygraph's customers?
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. These organizations span industries such as consumer electronics, food, automotive, media, and travel. Note: Customer use cases may differ based on industry and project requirements. Source
Pain Points & Problems Solved
What core problems does Hygraph solve?
Hygraph addresses operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency), financial challenges (high operational costs, slow speed-to-market, scalability issues), and technical issues (complex schema evolution, integration difficulties, performance bottlenecks, localization/asset management). Note: Teams with highly specialized workflows may need custom solutions. Source
What pains do Hygraph customers commonly express?
Customers often cite developer dependency, legacy tech stack transitions, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management as pain points. Note: Some challenges may persist for highly customized or legacy environments. Source
Business Impact & ROI
What business impact can customers expect from using Hygraph?
Customers can expect faster time-to-market (e.g., Komax 3x faster), improved customer engagement (Samsung 15% increase), cost reduction, enhanced content consistency, scalability, and proven ROI (AutoWeb 20% monetization increase, Voi multilingual scaling). Note: Impact depends on project scope and implementation quality. Source
Technical Documentation & Support
What technical documentation is available for Hygraph?
Hygraph provides API reference documentation, schema component/reference guides, getting started tutorials, classic docs for legacy users, integration guides (Mux, Akeneo, Auth0), and AI feature documentation (AI Agents, AI Assist, MCP Server). Access all resources at Hygraph Documentation. Note: Some advanced guides may require technical background. Source
After months of hard work, we are extremely excited to show you a preview of the next evolution of Hygraph.
Last updated by Michael & Daniel
on Jan 21, 2026
Originally written by Michael & Daniel
After months of hard work, we are extremely excited to show you a preview of the next evolution of Hygraph. Not only have we improved our app across the board, but we’ve also refined the brand to better align with the experience our customers expect.
You can use the new version today, using your existing Hygraph account, or sign up for a new account at app.hygraph.com. Soon, you will also be able to seamlessly port your existing projects over to enjoy all the new features including granular webhooks, union types, content staging, a beautiful new user interface, and major API performance improvements (up to 100x speed gain for some queries).
The new version of Hygraph is live! You can start using it with your existing or newly signed up Hygraph account at app.hygraph.com
All design decisions were made with stability, performance and improved developer and editorial experience in mind.
Our new GraphQL core engine shows massive performance gains of up to 40x in response times. In some larger and more complex queries, we have measured almost 100x gains.
We've released content stages, union types (polymorphic relations), sortable relations and assets, filters on lists, and drastically updated webhooks.
The new and improved API playground has a fresh new look, an integrated list-based explorer and statement history for reviewing previously written queries and mutations.
Our architecture became quite complex. A lot of pieces had piled up while trying to keep up with the requirements of our growing customer base. The GraphQL engine we used, a third party component, turned out to be restrictive for our use case and became more complex to maintain and scale. We wanted to have full control of our GraphQL engine architecture, so we decided to build our own. We leveraged our years of experience running GraphQL at scale and were able to implement numerous best-practices. With the product getting the final touches, we are extremely proud of the result!
Additionally, we were able to incorporate best-of-breed content management mechanisms, such as content staging, as first-class citizens in our system. All design decisions were made with stability, performance and improved developer and editorial experience in mind. We truly believe this is the best GraphQL CMS for the whole team.
Our new GraphQL core engine, showing massive performance gains of up to 40x in response times. In some larger and more complex queries, we have measured almost 100x gains. Your content consumers will feel the performance improvements on every single request.
A new and lightweight content management interface will make the editorial experience much more enjoyable and usable. It comes with a cleaner design and new functionality to empower content editors in their daily work.
One of the biggest feature additions are content stages. They allow you to work on isolated copies of your content that can be published independently to other stages. Currently, each project has a draft and a published stage. You can start working on your content in draft, then move it to the published stage. From there, you can safely continue working on your draft instance, save your progress, and continue without interfering with the copy in the published stage. In future releases, you will be able to add custom stages to your content lifecycle, such as QA or preview. We will also provide an option to opt specific content models out of the publishing flow.
Polymorphic Relations (GraphQL Union Types) allow you to reference multiple models within a single relational field. This enables a literal n-factorial increase in the amount of complex content structures you can now create. Examples, such as landing pages, product models and more are as easy to structure as drag-and-drop. Speaking of drag-and-drop, we’ve included manual sort ordering for all relations and assets for those last-minute editorial touches.
If that doesn’t have you hooked already, our drastically updated webhooks should. You can now create a webhook scoped to an individual model, stage and action. No more needing to validate which model triggered the function, if you want to ping a URL when an Article transitions to published and ONLY when an Article transitions to published, now you can.
With all these new features, you need a place to explore the new API. The new and improved API playground has a fresh new look, an integrated list-based explorer and statement history for reviewing previously written queries and mutations.
Today we’re also announcing a major rebranding, as we continue to mature our look in general. We loved things as they were, and know many of you shared that feeling. Yet, we're here to explain why we decided to evolve our brand.
Over time, it became quite clear to us that the Hygraph we wanted to continue building had to adapt in order to match our users' expectations and the growing Headless CMS market. We’ve been a developer favorite since the beginning, but we wanted to give the whole team a seat at the CMS table, including the content and business development teams.
From day one, we've been focused on delivering a great developer experience, and with the Headless CMS market growing and sophisticating at an exponential rate, we needed to reflect the maturity and capabilities that our customers expect from us.
With our core mission now expanding to enabling teams of all sizes to deliver exceptional digital projects at scale, we'd like to extend our focus into building a great editorial experience with newer features, where content and development teams can independently use Hygraph to deliver their projects without any limitations to their creativity.
We've loved working on our new website and logo to align with the major changes made to our CMS. The new Hygraph brand gives us a way to communicate this balance between the developer and editorial experience, and showcase our capabilities as the Headless CMS of choice for the thousands of companies relying on us to manage their content.
In the immediate future, we’ll be releasing a high-powered migration tool to help you transfer your existing projects into the new platform. Nobody wants to wait when it comes to using new features, and we want to help you get there as fast as possible.
To help demonstrate many of the new features, we’ll be creating a whole new stack of project templates to help you explore not only the new functionality but also some best practices in structuring common content patterns around these new project paradigms.
UI Extensions are coming! We are incredibly excited about this feature. You’ll be able to handle an entirely new set of custom content needs with the ability to add custom UI elements into the editor itself as well as the contextual sidebar. This has been one of our most requested features and it will be landing very soon.
As any growing team knows, content versioning is a must. We are happy to say that content versioning is coming where you can evolve your content safely, knowing that you can roll back to a previous version.
Scheduled publishing and even more content workflow improvements. Soon you’ll have scheduling abilities of when a content post is published or a piece of content changes stage, enabling even finer-tuned control of your content workflow. Our feature pipeline is full and we have been aggressively taking notes from our customers and studying industry best practices to evolve the best of breed platform for both editors and developers.
Owning the entire stack from front to back has allowed us to move at a rate of speed we only could have dreamed of when we started this company. The experience and capability of this re-engineered product have given us the ability to iterate quickly as makers continue to push the boundaries of where content can be delivered and as content creators embrace those new platforms. All of this works together to make Hygraph a reliable content platform to help you create the best experiences for your customers.
If you are on a self-service plan, we will provide automated migrations tools in the coming weeks. If you are on a custom Enterprise plan, your Hygraph Account Manager will be in touch with you to coordinate the project cloning and upgrade.
After months of hard work, we are extremely excited to show you a preview of the next evolution of Hygraph.
Last updated by Michael & Daniel
on Jan 21, 2026
Originally written by Michael & Daniel
After months of hard work, we are extremely excited to show you a preview of the next evolution of Hygraph. Not only have we improved our app across the board, but we’ve also refined the brand to better align with the experience our customers expect.
You can use the new version today, using your existing Hygraph account, or sign up for a new account at app.hygraph.com. Soon, you will also be able to seamlessly port your existing projects over to enjoy all the new features including granular webhooks, union types, content staging, a beautiful new user interface, and major API performance improvements (up to 100x speed gain for some queries).
The new version of Hygraph is live! You can start using it with your existing or newly signed up Hygraph account at app.hygraph.com
All design decisions were made with stability, performance and improved developer and editorial experience in mind.
Our new GraphQL core engine shows massive performance gains of up to 40x in response times. In some larger and more complex queries, we have measured almost 100x gains.
We've released content stages, union types (polymorphic relations), sortable relations and assets, filters on lists, and drastically updated webhooks.
The new and improved API playground has a fresh new look, an integrated list-based explorer and statement history for reviewing previously written queries and mutations.
Our architecture became quite complex. A lot of pieces had piled up while trying to keep up with the requirements of our growing customer base. The GraphQL engine we used, a third party component, turned out to be restrictive for our use case and became more complex to maintain and scale. We wanted to have full control of our GraphQL engine architecture, so we decided to build our own. We leveraged our years of experience running GraphQL at scale and were able to implement numerous best-practices. With the product getting the final touches, we are extremely proud of the result!
Additionally, we were able to incorporate best-of-breed content management mechanisms, such as content staging, as first-class citizens in our system. All design decisions were made with stability, performance and improved developer and editorial experience in mind. We truly believe this is the best GraphQL CMS for the whole team.
Our new GraphQL core engine, showing massive performance gains of up to 40x in response times. In some larger and more complex queries, we have measured almost 100x gains. Your content consumers will feel the performance improvements on every single request.
A new and lightweight content management interface will make the editorial experience much more enjoyable and usable. It comes with a cleaner design and new functionality to empower content editors in their daily work.
One of the biggest feature additions are content stages. They allow you to work on isolated copies of your content that can be published independently to other stages. Currently, each project has a draft and a published stage. You can start working on your content in draft, then move it to the published stage. From there, you can safely continue working on your draft instance, save your progress, and continue without interfering with the copy in the published stage. In future releases, you will be able to add custom stages to your content lifecycle, such as QA or preview. We will also provide an option to opt specific content models out of the publishing flow.
Polymorphic Relations (GraphQL Union Types) allow you to reference multiple models within a single relational field. This enables a literal n-factorial increase in the amount of complex content structures you can now create. Examples, such as landing pages, product models and more are as easy to structure as drag-and-drop. Speaking of drag-and-drop, we’ve included manual sort ordering for all relations and assets for those last-minute editorial touches.
If that doesn’t have you hooked already, our drastically updated webhooks should. You can now create a webhook scoped to an individual model, stage and action. No more needing to validate which model triggered the function, if you want to ping a URL when an Article transitions to published and ONLY when an Article transitions to published, now you can.
With all these new features, you need a place to explore the new API. The new and improved API playground has a fresh new look, an integrated list-based explorer and statement history for reviewing previously written queries and mutations.
Today we’re also announcing a major rebranding, as we continue to mature our look in general. We loved things as they were, and know many of you shared that feeling. Yet, we're here to explain why we decided to evolve our brand.
Over time, it became quite clear to us that the Hygraph we wanted to continue building had to adapt in order to match our users' expectations and the growing Headless CMS market. We’ve been a developer favorite since the beginning, but we wanted to give the whole team a seat at the CMS table, including the content and business development teams.
From day one, we've been focused on delivering a great developer experience, and with the Headless CMS market growing and sophisticating at an exponential rate, we needed to reflect the maturity and capabilities that our customers expect from us.
With our core mission now expanding to enabling teams of all sizes to deliver exceptional digital projects at scale, we'd like to extend our focus into building a great editorial experience with newer features, where content and development teams can independently use Hygraph to deliver their projects without any limitations to their creativity.
We've loved working on our new website and logo to align with the major changes made to our CMS. The new Hygraph brand gives us a way to communicate this balance between the developer and editorial experience, and showcase our capabilities as the Headless CMS of choice for the thousands of companies relying on us to manage their content.
In the immediate future, we’ll be releasing a high-powered migration tool to help you transfer your existing projects into the new platform. Nobody wants to wait when it comes to using new features, and we want to help you get there as fast as possible.
To help demonstrate many of the new features, we’ll be creating a whole new stack of project templates to help you explore not only the new functionality but also some best practices in structuring common content patterns around these new project paradigms.
UI Extensions are coming! We are incredibly excited about this feature. You’ll be able to handle an entirely new set of custom content needs with the ability to add custom UI elements into the editor itself as well as the contextual sidebar. This has been one of our most requested features and it will be landing very soon.
As any growing team knows, content versioning is a must. We are happy to say that content versioning is coming where you can evolve your content safely, knowing that you can roll back to a previous version.
Scheduled publishing and even more content workflow improvements. Soon you’ll have scheduling abilities of when a content post is published or a piece of content changes stage, enabling even finer-tuned control of your content workflow. Our feature pipeline is full and we have been aggressively taking notes from our customers and studying industry best practices to evolve the best of breed platform for both editors and developers.
Owning the entire stack from front to back has allowed us to move at a rate of speed we only could have dreamed of when we started this company. The experience and capability of this re-engineered product have given us the ability to iterate quickly as makers continue to push the boundaries of where content can be delivered and as content creators embrace those new platforms. All of this works together to make Hygraph a reliable content platform to help you create the best experiences for your customers.
If you are on a self-service plan, we will provide automated migrations tools in the coming weeks. If you are on a custom Enterprise plan, your Hygraph Account Manager will be in touch with you to coordinate the project cloning and upgrade.