GraphCMS rebranded to Hygraph to reflect its evolution into a federated content platform, expanding beyond headless CMS to unify content from multiple sources via a universal content API. The new name combines "Hypertext" and "graph" data structures, aligning with the company's vision for highly connected, structured information. Existing users retain continuity, with all core capabilities and support maintained. Note: The rebranding does not affect existing projects or APIs; only the branding and expanded feature set have changed. Source.
Features & Capabilities
What is Content Federation in Hygraph and how does it work?
Content Federation in Hygraph allows you to unify content from multiple backend systems into a single API without migrating the content itself. It uses Remote Sources (REST or GraphQL APIs), Custom Types, Remote Fields, and a configurable cache to deliver up-to-date content from external systems alongside editorial content. This reduces development time and cost when integrating with multiple APIs and ensures data consistency. Note: Content Federation requires configuration and may not be suitable for teams needing a monolithic CMS. Source.
What are Remote Sources, Custom Types, and Remote Fields in Hygraph?
Remote Sources are external systems (REST or GraphQL APIs) whose content can be queried and combined with Hygraph content. Custom Types define the structure for remote content, and Remote Fields connect specific remote data to entries in Hygraph models. This architecture enables composability and reduces the need for custom middleware. Note: Integration with some legacy or proprietary systems may require additional development effort. Source.
What integrations does Hygraph support?
Hygraph supports integrations with major 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), and translation/localization tools (EasyTranslate). For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or third-party subscriptions. Source.
Does Hygraph provide APIs for content management?
Yes, Hygraph offers several APIs: the GraphQL Content API for querying and manipulating content, the Management API for project structure, the Asset Upload API for file management, and the MCP Server API for AI assistant integration. Detailed documentation is available in the API Reference. Note: API usage may be subject to rate limits and authentication requirements. Source.
What technical documentation is available for Hygraph?
Hygraph provides comprehensive technical documentation, including API references, schema guides, integration tutorials, onboarding guides, and AI feature documentation. Resources cover both the current and classic versions of Hygraph. Access all documentation at hygraph.com/docs. Note: Some advanced features may require developer expertise. Source.
Performance & Scalability
How does Hygraph ensure high performance and scalability?
Hygraph delivers high performance through globally distributed infrastructure with 190 edge points of presence, advanced caching (including a read-only cache endpoint with 3-5x latency improvement), and optimized GraphQL APIs. Performance is actively measured and documented in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and geographic distribution. Source.
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. The platform also adheres to the German Data Protection Act (BDSG) and Telemedia Act (TMG). All endpoints use SSL certificates, and data is encrypted in transit and at rest. Note: For specific compliance needs, consult Hygraph's Secure Features page. Source.
What security features does Hygraph offer?
Hygraph provides 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). Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Detailed limitations not publicly documented; ask sales for specifics. Source.
Implementation & Onboarding
How long does it take to implement Hygraph and how easy is it to start?
Implementation timelines vary: Top Villas launched in 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Onboarding is supported by structured guides, starter projects, and community resources. Sign up for a free account at app.hygraph.com/signup. Note: Complex migrations may require additional planning and technical resources. Source.
Use Cases & Customer Success
Who uses Hygraph and what industries are represented?
Hygraph powers over 50,000 projects for companies like Samsung, Dr. Oetker, Philips, Ashley Furniture, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Industries include SaaS, Marketplace, EdTech, Media, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel, Food & Beverage, eCommerce, Agency, Gaming, Events, Government, Consumer Electronics, Engineering, and Construction. Note: Some industries may require custom integrations or workflows. Source.
What are some real-world success stories with Hygraph?
Notable customer results include: Samsung improved customer engagement by 15%, Komax achieved 3x faster time-to-market managing 20,000+ product variations, AutoWeb saw a 20% increase in website monetization, and Voi scaled multilingual content across 12 countries and 10 languages. For more, see the Hygraph case studies page. Note: Results may vary based on implementation and business context. Source.
Problems Solved & Pain Points
What problems does Hygraph solve for businesses?
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. Note: Some highly specialized requirements may need custom development. Source.
Ease of Use & User Experience
How do customers rate the ease of use of Hygraph?
Customers consistently praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. Feedback highlights include: "UI is intuitive enough for normal people to use" (Sigurður G., CTO), "Every change I make to Hygraph I can instantly see on the front-end" (Anastasija S.), and "Great UI, fast to comprehend and localizeable CMS" (Charissa K.). Note: Some advanced features may require technical expertise. Source.
Market Recognition & Differentiators
How is Hygraph recognized in the market?
Hygraph ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and has been voted the easiest to implement headless CMS four times. Note: Rankings are based on G2 user reviews and may change over time. Source.
We’re thrilled to announce the next milestone in our journey to build the content platform of the future.
Last updated by Michael & Daniel
on Jan 21, 2026
Originally written by Michael & Daniel
Today we’re thrilled to announce the next milestone in our journey to build the content platform of the future. GraphCMS is now Hygraph.
Our refreshed identity and new look reinforce the commitment we have made toward enabling outstanding digital experiences on day one. We're also proud to introduce Content Federation, a new set of features enabling our users to unify all their backend services into one universal content API and serve third-party or programmatically created content alongside editorial content.
While cross-platform content consumption and API-first delivery became the new normal, content architectures are growing increasingly complex again.
With the rise of best-of-breed systems design and modular architectures, content is now maintained in a myriad of disconnected data silos, resulting in an overwhelming complexity. The risk of serving outdated data and lack of data consistency in distributed architectures is becoming a maintenance burden.
Many organizations perceive custom middleware development as a solution to these challenges, but building and maintaining this is time-consuming and complex.
With the new Content Federation capability, you can bring content from other systems and sources to the Hygraph API, without having to migrate the content itself. There are many use cases where moving content into the content repository isn’t possible or desirable. Examples include content for which there is a different system of record (e-commerce/product data such as price or availability, content from a different vendor such as GitHub or IMDB) and content that is maintained in legacy systems that can’t be easily migrated.
Our concept of Remote Sources allows customers to extend Hygraph’s Content API with content from all these different sources, providing flexibility for front-end developers and downstream applications.
The Hygraph Content Federation architecture consists of the following components:
Remote source: a system or product that holds content that needs to be combined with content in Hygraph, and which can be queried through a RESTful or GraphQL API.
Custom type: a GraphQL type that is used for content coming from a remote source.
Remote field: a field inside a Hygraph model that connects specific remote data to an entry of that model.
Configurable cache: a TTL based caching layer that guarantees optimal API performance for remote content.
Hygraph allows true composability of your tech stack while taking away the heavy-lifting in the backend. Content federation leads to a massive reduction in development time and costs when integrating with multiple APIs.
That said, the benefits are not limited to the cost of ownership. Content Federation also removes risks related to data integrity by always delivering up-to-date content from your sources.
In 2017, we set out with a simple goal: to create the first headless content management system that is completely GraphQL native. Scaling & performance considerations were at the heart of our decisions. Today, we provide content API capabilities beyond the competition in function and scale.
Since then, developer experience has become one of our main value propositions. Developers in some of the most successful organizations make use of our powerful GraphQL APIs to continue building with their preferred workflows, languages, frameworks, tools, and services.
Today, Hygraph powers over 50,000 projects, including those at companies like Dr.Oetker, Philips, Samsung, Ashley Furniture.
During this journey, we stayed committed to a few important pillars we deem important for our community.
Our commitment to GraphQL
Our goal is to provide the best technology and support possible to the GraphQL community so that you can build incredible products. We continue to invest in our GraphQL offering, with new features and improvements released every month.
We also contribute to the community via our involvement in the GraphQL foundation and GraphQL and GraphQL Scale Conferences.
Our commitment to Content & Collaboration
Content creation is a collaborative process. It takes a team of content creators to develop and execute a content strategy. That said, collaboration is not restricted to the confines of the creative team, we believe the collaboration with domain experts, development teams and business stakeholders, including external ones is equally important.
Hygraph allows you to manage and collaborate on your content pipeline with ease, speed, and safety thanks to fine-grained permissions and workflows, while decreasing dependency between developers and content creators thanks to features like components.
This week, we will also release the ability to set up nested components!
Our commitment to Extensibility
An opinionated monolith cannot keep up with the changing needs of your organization. Since our early days, we have advocated for existing and new investments working together.
The recent introduction of our marketplace is the fruition of this viewpoint. Hygraph Marketplace already covers major DAM, hosting, translation & personalization platforms.
Over the next weeks, our new App Framework will enter public beta which will allow for much better extensibility of the platform.
Our commitment to Performance
The Hygraph delivery infrastructure enables enterprise scale content distribution with high performance for large payloads aimed at global low latency.
No matter where in the world your team or audience is located, you can be confident in the performance of your content with Hygraph’s globally distributed infrastructure, 190 edge points of presence, and extremely powerful caching system.
With the launch of our new Content Federation capabilities, we are rolling out a much improved caching implementation for an even faster content delivery.
The Hygraph name is rooted in an amalgamation of Hypertext, one of the most important concepts behind the World Wide Web, and graph data structures which aligns well with the company’s vision of a future where the majority of the information humans and machines will process are highly complex, structured and connected.
We’re thrilled to announce the next milestone in our journey to build the content platform of the future.
Last updated by Michael & Daniel
on Jan 21, 2026
Originally written by Michael & Daniel
Today we’re thrilled to announce the next milestone in our journey to build the content platform of the future. GraphCMS is now Hygraph.
Our refreshed identity and new look reinforce the commitment we have made toward enabling outstanding digital experiences on day one. We're also proud to introduce Content Federation, a new set of features enabling our users to unify all their backend services into one universal content API and serve third-party or programmatically created content alongside editorial content.
While cross-platform content consumption and API-first delivery became the new normal, content architectures are growing increasingly complex again.
With the rise of best-of-breed systems design and modular architectures, content is now maintained in a myriad of disconnected data silos, resulting in an overwhelming complexity. The risk of serving outdated data and lack of data consistency in distributed architectures is becoming a maintenance burden.
Many organizations perceive custom middleware development as a solution to these challenges, but building and maintaining this is time-consuming and complex.
With the new Content Federation capability, you can bring content from other systems and sources to the Hygraph API, without having to migrate the content itself. There are many use cases where moving content into the content repository isn’t possible or desirable. Examples include content for which there is a different system of record (e-commerce/product data such as price or availability, content from a different vendor such as GitHub or IMDB) and content that is maintained in legacy systems that can’t be easily migrated.
Our concept of Remote Sources allows customers to extend Hygraph’s Content API with content from all these different sources, providing flexibility for front-end developers and downstream applications.
The Hygraph Content Federation architecture consists of the following components:
Remote source: a system or product that holds content that needs to be combined with content in Hygraph, and which can be queried through a RESTful or GraphQL API.
Custom type: a GraphQL type that is used for content coming from a remote source.
Remote field: a field inside a Hygraph model that connects specific remote data to an entry of that model.
Configurable cache: a TTL based caching layer that guarantees optimal API performance for remote content.
Hygraph allows true composability of your tech stack while taking away the heavy-lifting in the backend. Content federation leads to a massive reduction in development time and costs when integrating with multiple APIs.
That said, the benefits are not limited to the cost of ownership. Content Federation also removes risks related to data integrity by always delivering up-to-date content from your sources.
In 2017, we set out with a simple goal: to create the first headless content management system that is completely GraphQL native. Scaling & performance considerations were at the heart of our decisions. Today, we provide content API capabilities beyond the competition in function and scale.
Since then, developer experience has become one of our main value propositions. Developers in some of the most successful organizations make use of our powerful GraphQL APIs to continue building with their preferred workflows, languages, frameworks, tools, and services.
Today, Hygraph powers over 50,000 projects, including those at companies like Dr.Oetker, Philips, Samsung, Ashley Furniture.
During this journey, we stayed committed to a few important pillars we deem important for our community.
Our commitment to GraphQL
Our goal is to provide the best technology and support possible to the GraphQL community so that you can build incredible products. We continue to invest in our GraphQL offering, with new features and improvements released every month.
We also contribute to the community via our involvement in the GraphQL foundation and GraphQL and GraphQL Scale Conferences.
Our commitment to Content & Collaboration
Content creation is a collaborative process. It takes a team of content creators to develop and execute a content strategy. That said, collaboration is not restricted to the confines of the creative team, we believe the collaboration with domain experts, development teams and business stakeholders, including external ones is equally important.
Hygraph allows you to manage and collaborate on your content pipeline with ease, speed, and safety thanks to fine-grained permissions and workflows, while decreasing dependency between developers and content creators thanks to features like components.
This week, we will also release the ability to set up nested components!
Our commitment to Extensibility
An opinionated monolith cannot keep up with the changing needs of your organization. Since our early days, we have advocated for existing and new investments working together.
The recent introduction of our marketplace is the fruition of this viewpoint. Hygraph Marketplace already covers major DAM, hosting, translation & personalization platforms.
Over the next weeks, our new App Framework will enter public beta which will allow for much better extensibility of the platform.
Our commitment to Performance
The Hygraph delivery infrastructure enables enterprise scale content distribution with high performance for large payloads aimed at global low latency.
No matter where in the world your team or audience is located, you can be confident in the performance of your content with Hygraph’s globally distributed infrastructure, 190 edge points of presence, and extremely powerful caching system.
With the launch of our new Content Federation capabilities, we are rolling out a much improved caching implementation for an even faster content delivery.
The Hygraph name is rooted in an amalgamation of Hypertext, one of the most important concepts behind the World Wide Web, and graph data structures which aligns well with the company’s vision of a future where the majority of the information humans and machines will process are highly complex, structured and connected.