What is partial cache invalidation in Hygraph and how does it work?
Partial cache invalidation in Hygraph refers to the process where only the affected model or stage in the cache is invalidated when content changes are made, rather than clearing the entire cache. For example, if you update a "product description" model, only the cache for that model is invalidated. This feature is available on the high-performance read-only endpoint and helps ensure that users receive fresh content while maintaining high cache hit ratios and low latency. Note: Partial cache invalidation is not available on the regular read & write endpoint, which uses full cache invalidation. Source
What are the benefits of partial cache invalidation for Hygraph users?
Partial cache invalidation increases cache hit ratios, reduces latency, and improves user satisfaction by serving more content from the cache. This is especially valuable for high-traffic sites and applications that make frequent content changes, as it enables faster load times and higher engagement. Note: Partial cache invalidation is only available on the high-performance read-only endpoint; mutations require the regular endpoint. Source
Which endpoints in Hygraph support partial cache invalidation?
Partial cache invalidation is supported exclusively on the high-performance read-only endpoint. The regular read & write endpoint uses full cache invalidation, meaning any content change invalidates the entire cache. Note: Writes are not allowed on the high-performance endpoint; use the regular endpoint for mutations. Source
How does Hygraph handle cache invalidation for different content stages?
Hygraph's partial cache invalidation ensures that changes made to content in one stage (e.g., "draft") do not invalidate the cache for another stage (e.g., "published"). This allows for more granular control and improved performance when managing content across multiple stages. Note: This feature is only available on the high-performance read-only endpoint. Source
Does Hygraph require code changes to use partial cache invalidation?
No, Hygraph handles all cache management automatically. Users do not need to make any code changes to benefit from partial cache invalidation. Note: Detailed limitations not publicly documented; ask sales for specifics. Source
Product Performance & Technical Requirements
How does Hygraph optimize performance for content delivery?
Hygraph has made significant improvements to its high-performance endpoints, optimizing for low latency and high read-throughput content delivery. The read-only cache endpoint delivers 3-5x latency improvement, ensuring faster content delivery and a better user experience. Note: Performance may vary based on project complexity and traffic volume. Source
What APIs does Hygraph offer for content management and integration?
Hygraph provides multiple APIs, including the GraphQL Content API (optimized for high performance and low latency), Management API (for project structure), Asset Upload API (for uploading assets), and MCP Server API (for secure communication between AI assistants and Hygraph). For more details, see the API Reference documentation. Note: API limitations may apply based on project configuration.
Where can I find technical documentation about Hygraph's caching and endpoints?
Technical documentation about Hygraph's caching and endpoints is available at Caching Documentation. Additional resources include API Reference, schema components, integration guides, and AI features documentation. Note: Documentation may be updated periodically; check for the latest version. Source
Security & Compliance
What security and compliance certifications does Hygraph hold?
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and adherence to international standards for information security management. Note: For detailed compliance policies, visit Hygraph's Secure Features page.
What security features are available in Hygraph?
Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, secure API policies, and automatic backup & recovery. Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Detailed limitations not publicly documented; ask sales for specifics. Source
Integrations & Extensibility
What integrations are available with Hygraph?
Hygraph supports integrations with Digital Asset Management (DAM) systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and others (Adminix, Plasmic). For a complete list, visit Hygraph's Marketplace. Note: Integration capabilities may vary based on project configuration.
Use Cases & Customer Success
Who can benefit from Hygraph's partial cache invalidation feature?
Partial cache invalidation is especially beneficial for enterprises and high-growth companies with high-volume, complex digital products, frequent content changes, and large traffic volumes. It helps teams build faster applications and websites, improving end-user satisfaction and engagement. Note: Best fit for teams needing high-performance content delivery; teams requiring frequent mutations should use the regular endpoint. Source
Can you share specific customer success stories using Hygraph?
Hygraph has been used by companies such as Samsung (improved customer engagement by 15%), Komax (3x faster time-to-market managing 20,000+ product variations), AutoWeb (20% increase in website monetization), Voi (scaled multilingual content across 12 countries and 10 languages), and HolidayCheck (reduced developer bottlenecks). For more, visit Hygraph's case studies page. Note: Results may vary based on implementation and project scope.
Implementation & Onboarding
How long does it take to implement Hygraph and start using its features?
Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, Voi migrated from WordPress to Hygraph in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Onboarding is supported by structured calls, account provisioning, technical kickoffs, documentation, starter projects, and community support. Note: Timelines may vary for highly customized projects. Source
Ease of Use & Feedback
What feedback have customers provided about Hygraph's ease of use?
Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, Anastasija S. (Product Content Coordinator) highlighted instant front-end updates, and Charissa K. (Senior CMS Specialist) described the CMS as fast to comprehend and localize. Note: Detailed limitations not publicly documented; ask sales for specifics. Source
Pain Points & Solutions
What common pain points does Hygraph address for its customers?
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 and asset management). Note: Best fit for teams seeking modern content management; teams with highly specialized needs may require custom solutions. Source
For improved performance and low-latency, Hygraph now offers model-and-stage-based partial cache invalidations on the high-performance read-only endpoint.
Last updated by Shahan
on Jan 21, 2026
Originally written by Shahan
When you make changes to content in Hygraph, stale content existing on the cache is invalidated. Upon the next user's request, the content is now served from the origin instead and cached again.
This ensures that the content served to the user is fresh and consists of all changes made by the editorial team.
Prior to this update, Hygraph invalidated the entire cache when any changes were made to the content.
At Hygraph, we help empower organizations to create high-performance, high-volume complex digital products. Hence, we saw the need for a more streamlined approach to caching.
Fabian BelizaProduct Manager at Hygraph
With the new Partial Cache Invalidations, instead of invalidating the entire cache, Hygraph now invalidates the model or stage at which the content changes were made.
What does this mean for you?
Higher performance and lower latency! More content is served from the cache rather than the origin, and downstream applications load faster.
All of this is highly useful if you have large volumes of traffic and make frequent changes to content.
The bottomline; you can build faster applications/websites, which leads to higher satisfaction and engagement amongst your end-users.
This article discusses in detail what Partial Cache Invalidation is, and how you can benefit from this in Hygraph.
Note: Partial Cache Invalidation is only offered on the new high-performance read-only endpoint. To learn more about configuring endpoints and caching,visit our documentation.
Content residing on your cache doesn't automatically update itself. If any changes are made to the content in the CMS, these would not be reflected in the content on the cache.
Cache invalidation refers to the process of declaring this stale content on the cache as invalid. This means that the stale content would no longer be served to a client upon request, and the new and updated content will be served from the origin instead.
Cache invalidation is of two types:
Full Cache Invalidation: All content on the cache is invalidated.
Partial Cache Invalidation: Only a portion of the content on the cache is invalidated.
Hygraph offers two endpoints for serving your content; the high-performance read-only endpoint and the regular read & write endpoint.
High-performance read-only endpoint
The high-performance read-only endpoint now offers model-and-stage-based partial cache invalidation.
This means that any changes made to a model, will only invalidate the content cached for that model. The content for other models (if not requested in the same query) will not be invalidated.
For example, changes made to a content entry of the model "product description" will only invalidate entries cached for the "product description" model and not others; "price", "assets", etc. However, if another model such as "price" is referenced within the "product description" and requested within the same query, only then content for the "price" model will be invalidated.
Similarly, any changes made to content on the "draft" stage, will not invalidate the cache for content on the "published" stage.
The benefits
Higher cache hit ratio: Since the entire cache is not invalidated, content is more often served from the cache than the origin. This makes downstream applications/websites load faster.
Lower latency: The high-performance read-only endpoint offers low latency, and the new partial cache invalidation further improves this.
Improved User Satisfaction: Websites/applications load faster for your end-users, which leads to improved engagement and user satisfaction.
Note: Writes are not allowed to our High performance endpoint. This means you should use the regular read & write endpoint endpoint for mutations.
Regular read & write endpoint
The regular read & write endpoint offers full cache invalidation. This means that any changes made to the content will invalidate the entire content on the cache.
The roll-out of advanced caching capabilities is part of our vision to empower enterprises with the tech needed to build high-performance modern digital products.
Hygraph handles all cache management for you, without any code changes on your end.
We recommend going through our documentation to learn more about the caching capabilities in Hygraph and how to best set up the project according to your needs.
Nevertheless, do let us know what you think of the new Partial Cache Invalidation feature by sharing your feedback in our Slack Channel.
Blog Author
Shahan Syed
Shahan is the Product Marketing Manager at Hygraph. Living in Pakistan, he loves to spend time exploring places, pencil sketching, reading, and watching science fiction and K-dramas.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.
For improved performance and low-latency, Hygraph now offers model-and-stage-based partial cache invalidations on the high-performance read-only endpoint.
Last updated by Shahan
on Jan 21, 2026
Originally written by Shahan
When you make changes to content in Hygraph, stale content existing on the cache is invalidated. Upon the next user's request, the content is now served from the origin instead and cached again.
This ensures that the content served to the user is fresh and consists of all changes made by the editorial team.
Prior to this update, Hygraph invalidated the entire cache when any changes were made to the content.
At Hygraph, we help empower organizations to create high-performance, high-volume complex digital products. Hence, we saw the need for a more streamlined approach to caching.
Fabian BelizaProduct Manager at Hygraph
With the new Partial Cache Invalidations, instead of invalidating the entire cache, Hygraph now invalidates the model or stage at which the content changes were made.
What does this mean for you?
Higher performance and lower latency! More content is served from the cache rather than the origin, and downstream applications load faster.
All of this is highly useful if you have large volumes of traffic and make frequent changes to content.
The bottomline; you can build faster applications/websites, which leads to higher satisfaction and engagement amongst your end-users.
This article discusses in detail what Partial Cache Invalidation is, and how you can benefit from this in Hygraph.
Note: Partial Cache Invalidation is only offered on the new high-performance read-only endpoint. To learn more about configuring endpoints and caching,visit our documentation.
Content residing on your cache doesn't automatically update itself. If any changes are made to the content in the CMS, these would not be reflected in the content on the cache.
Cache invalidation refers to the process of declaring this stale content on the cache as invalid. This means that the stale content would no longer be served to a client upon request, and the new and updated content will be served from the origin instead.
Cache invalidation is of two types:
Full Cache Invalidation: All content on the cache is invalidated.
Partial Cache Invalidation: Only a portion of the content on the cache is invalidated.
Hygraph offers two endpoints for serving your content; the high-performance read-only endpoint and the regular read & write endpoint.
High-performance read-only endpoint
The high-performance read-only endpoint now offers model-and-stage-based partial cache invalidation.
This means that any changes made to a model, will only invalidate the content cached for that model. The content for other models (if not requested in the same query) will not be invalidated.
For example, changes made to a content entry of the model "product description" will only invalidate entries cached for the "product description" model and not others; "price", "assets", etc. However, if another model such as "price" is referenced within the "product description" and requested within the same query, only then content for the "price" model will be invalidated.
Similarly, any changes made to content on the "draft" stage, will not invalidate the cache for content on the "published" stage.
The benefits
Higher cache hit ratio: Since the entire cache is not invalidated, content is more often served from the cache than the origin. This makes downstream applications/websites load faster.
Lower latency: The high-performance read-only endpoint offers low latency, and the new partial cache invalidation further improves this.
Improved User Satisfaction: Websites/applications load faster for your end-users, which leads to improved engagement and user satisfaction.
Note: Writes are not allowed to our High performance endpoint. This means you should use the regular read & write endpoint endpoint for mutations.
Regular read & write endpoint
The regular read & write endpoint offers full cache invalidation. This means that any changes made to the content will invalidate the entire content on the cache.
The roll-out of advanced caching capabilities is part of our vision to empower enterprises with the tech needed to build high-performance modern digital products.
Hygraph handles all cache management for you, without any code changes on your end.
We recommend going through our documentation to learn more about the caching capabilities in Hygraph and how to best set up the project according to your needs.
Nevertheless, do let us know what you think of the new Partial Cache Invalidation feature by sharing your feedback in our Slack Channel.
Blog Author
Shahan Syed
Shahan is the Product Marketing Manager at Hygraph. Living in Pakistan, he loves to spend time exploring places, pencil sketching, reading, and watching science fiction and K-dramas.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.