What are Remote Sources in Hygraph and how do they work?
Remote Sources in Hygraph allow you to extend the Content API by integrating content from third-party systems (such as RESTful or GraphQL APIs) into a single federated API. This means you can combine data from platforms like BigCommerce, Shopify, Zendesk, GitHub, Fauna, and IMDB with your Hygraph content using a low-code UI. The caching infrastructure ensures high performance for federated APIs. Note: Remote Sources require configuration and may not be suitable for teams needing only basic, single-source content management. Read more | Documentation.
What are Nested Components in Hygraph and what use cases do they support?
Nested Components let you build complex, reusable content structures by embedding components within other components—up to four levels deep. For example, you can create a Section component that contains Hero, Image Gallery, or Video Block components, each of which can have their own nested components. This enables flexible schema modeling and a more streamlined editorial experience. Note: Nested Components are best for teams needing advanced content modeling; simpler use cases may not require this feature. Learn more.
What improvements were made to the project creation flow in Hygraph?
The project creation workflow was simplified to reduce unnecessary steps and clicks, making it more efficient for users to start new projects. This streamlining aims to minimize friction during product evaluation and everyday use. Note: While the process is faster, users with highly customized onboarding needs may still require manual setup.
How does Hygraph support content federation?
Hygraph's content federation allows you to integrate multiple data sources (REST or GraphQL APIs) into a single API without duplicating data. This ensures consistent content delivery across channels and simplifies managing complex content ecosystems. Note: Content federation setup may require technical expertise and is most beneficial for organizations with multi-source content needs. Read more.
What is the App Framework in Hygraph and how can I access it?
The App Framework enables full extensibility of Hygraph by allowing third-party web applications (front-end or full-stack) to integrate with the platform. It is currently in closed beta; interested users can apply to join the beta program. Note: As of July 2022, the App Framework is not generally available. Join the beta.
What is the new permission to hide the schema view in Hygraph?
Hygraph introduced a permission that allows administrators to hide the schema view for specific user roles. This provides a more streamlined editor experience and greater flexibility in defining access restrictions. Note: Hiding the schema view may limit advanced users who need to manage or update schemas.
What are the empty state improvements in Hygraph?
Empty state improvements in Hygraph enhance discoverability for new and existing users by providing educational content and easy deployment of pre-built examples. This helps users understand core features and accelerates project setup. Note: These improvements are most beneficial for new users; experienced users may already be familiar with the platform's features.
Technical Requirements & Documentation
What APIs does Hygraph provide?
Hygraph offers a GraphQL-native API for querying and mutating content, a Content API for programmatic content access, and a Management API for managing schemas and users. These APIs support automation and integration with modern tech stacks. Note: Advanced API usage may require developer expertise. API Reference.
Where can I find technical documentation for Hygraph?
Comprehensive documentation is available for getting started, API reference, asset management, content modeling, migration, and more. Key resources include the Getting Started guide, API Reference, and Migration Guide. Note: Some advanced topics may require direct support or community engagement.
Integrations
What integrations does Hygraph support?
Hygraph integrates with platforms such as Cloudinary, Bynder, Filestack, Scaleflex Filerobot (DAM), EasyTranslate (localization), Netlify and Vercel (hosting), Mux (video), AWS S3 (object storage), Imgix (image optimization), Akeneo (PIM), Adminix, and Plasmic. For a full list, visit the Integrations Page. Note: Integration setup may require technical configuration depending on the platform.
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 offers granular permissions, audit logs, automatic backups, and encryption at rest and in transit. Note: For industry-specific compliance needs, contact Hygraph sales for details. More info.
Use Cases & Benefits
What types of companies and industries use Hygraph?
Hygraph is used by companies in SaaS, marketplaces, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agencies, online gaming, events, government, consumer electronics, engineering, and construction. Notable customers include Sennheiser, Samsung, Komax, Dr. Oetker, Epic Games, and Ancestry. Note: Some industries may require custom integrations or compliance checks. See case studies.
What business impact can customers expect from using Hygraph?
Customers have reported improved operational efficiency, faster time-to-market (e.g., Komax achieved 3X faster launches), enhanced customer engagement (Samsung saw a 15% lift), and cost savings (AutoWeb increased website monetization by 20%). Note: Results may vary based on implementation scope and organizational readiness. Read customer stories.
Who is the target audience for Hygraph?
Hygraph is designed for marketing and content teams, developers and engineers, product managers, and enterprise IT/operations teams. It is especially valuable for organizations managing multiple brands, regions, and languages, or those transitioning from legacy CMS platforms. Note: Smaller teams with simple content needs may find some features more advanced than required.
Support & Implementation
How long does it take to implement Hygraph and how easy is it to get started?
Implementation time depends on project complexity. Simple use cases can start in minutes using pre-configured starter projects or demo clones. More complex setups benefit from structured onboarding, documentation, and community support. Note: Large-scale migrations or custom integrations may require additional planning. Starter projects | Onboarding guide.
Customer Proof & Feedback
What feedback have customers given about Hygraph's ease of use?
Customers such as Anastasija S. (Product Content Coordinator) highlight Hygraph's ease of use and responsive support. Charissa K. describes it as "fast to comprehend and localizable," and Tom K. (Web Development Team Lead) notes its suitability for complex websites and strong support. Note: User experience may vary based on project complexity and team familiarity. See more feedback.
Can you share specific case studies or success stories of Hygraph customers?
Yes. Komax achieved a 3X faster time-to-market, Samsung improved customer engagement by 15%, AutoWeb increased website monetization by 20%, Dr. Oetker ensured global consistency and scalability, and Fitfox launched a mobile-first product using Hygraph. Note: Outcomes depend on implementation and business context. See all case studies.
With the launch of our new brand, Remote Sources are now generally available
Nested Components, the next major step in the evolution of our Component feature, is released
A set of updates aiming to improve usability and Developer Experience including the possibility to hide the schema view, empty state improvements and an improved project creation flow.
Following the pre-release of Remote Fields in March 2022, the feature set allowing to extend Hygraph’s Content API with content from third-party sources is now available to all users under the name of Remote Sources.
A Remote Source is any system or product that holds content or data that should be combined with content in Hygraph into a single API, while a Remote Field refers to a field inside a Hygraph model that connects specific remote data to an entry of that model. With our unique low-code approach to federation, you can combine data from any RESTful or GraphQL API with content stored in Hygraph through our easy use UI. Our caching infrastructure ensures amazing performance for the resulting federated API.
Within the first two weeks since its launch, we have seen 100s of projects starting to make use of both RESTtful and GraphQL Remote Resources as diverse as BigCommerce, Shopify, Zendesk, GitHub, Fauna, IMDB, and many others.
Since their introduction, components enabled a pre-defined set of fields to be re-usable across models and content entries, making content creation significantly faster by reducing complexity. Nested components enhance this functionality by bringing even more flexibility in building repeatable content entries.
Using nested components, you can have a parent component where one or more components are nested. This would allow you to, for instance, create a section and a subsection component and then embed one into the other.
The ability to build complex components made from several smaller components gives you more flexibility in how you model your schema and a more user-friendly interface for your content creators.
On the Schema side, you can create complex nested structures. For example, you can allow editors to create different parts of your website using the Section component that would host an array of other components. Those could be Hero, Flip-card, Image gallery, Video block, etc. All of the second level components can have lower level components too. Such content structure allows for unmatched editorial creativity, as well as the ability to specify what each section of your page can have.
On the Editor side, content professionals can edit their entries in one go. No more going back and forth between different building blocks - everything can be set up on the same page. In addition, nested components help “declutter” the UI: you won’t see all of the fields on your content entry until you choose to add the necessary component.
Nested components allow up to 4 levels of nesting, enabling use cases previously considered tedious to implement with relations.
Read more about how to use nested components in our documentation.
New permission to hide the schema view
To provide an even more streamlined editor experience for content creators, you can now make the schema view fully hidden through a custom role definition. This brings further flexibility in how you would like to define restrictions.
Improved new project creation flow
The project creation workflow has been simplified in order to provide the user the most efficient path during their product evaluation and everyday usage. Unnecessary friction through the inclusion of additional screens and clicks has been minimized and condensed where possible. The intention has been to streamline the experience for all users.
Empty state improvements
Empty state improvements provide a greater degree of discoverability to new and possibly existing users through all core features and functions of the product. They seek to both educate and increase project velocity by providing a mechanism to easily deploy pre-built examples with an additional explanatory copy for a first pass level of understanding.
An App is a standard web application that lives outside of the Hygraph main product, developed and hosted by a third party. It can be a simple FE-only static page, or a full-fledged web app written in any language, with backend, API, and a DB.
App Framework will allow a full extensibility of Hygraph similar to UI Extensions, but giving you more power and easier way to integrate third party apps, and distribute these integrations.
It's currently in closed beta. If you want to join our beta program and help us to improve it, you can join here.
As you know, we're back with this year's GraphQL Conf. with our friends at commercetools. With a couple of months to go, we've got some fantastic speakers lined up and some amazing GraphQL swags. Register for your free ticket and share it with your friends to win some swag!
Want to know when features roll out in real time to test, provide feedback and direction for Hygraph? Join our community through slack to stay up-to-date on all Hygraph announcements, events, and all the growing ways to get involved with Hygraph and our team.
Gijs is the Head of Product at Hygraph. When he's not focused on realizing our product vision, he spends time teaching others how to pronounce his first name.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.
With the launch of our new brand, Remote Sources are now generally available
Nested Components, the next major step in the evolution of our Component feature, is released
A set of updates aiming to improve usability and Developer Experience including the possibility to hide the schema view, empty state improvements and an improved project creation flow.
Following the pre-release of Remote Fields in March 2022, the feature set allowing to extend Hygraph’s Content API with content from third-party sources is now available to all users under the name of Remote Sources.
A Remote Source is any system or product that holds content or data that should be combined with content in Hygraph into a single API, while a Remote Field refers to a field inside a Hygraph model that connects specific remote data to an entry of that model. With our unique low-code approach to federation, you can combine data from any RESTful or GraphQL API with content stored in Hygraph through our easy use UI. Our caching infrastructure ensures amazing performance for the resulting federated API.
Within the first two weeks since its launch, we have seen 100s of projects starting to make use of both RESTtful and GraphQL Remote Resources as diverse as BigCommerce, Shopify, Zendesk, GitHub, Fauna, IMDB, and many others.
Since their introduction, components enabled a pre-defined set of fields to be re-usable across models and content entries, making content creation significantly faster by reducing complexity. Nested components enhance this functionality by bringing even more flexibility in building repeatable content entries.
Using nested components, you can have a parent component where one or more components are nested. This would allow you to, for instance, create a section and a subsection component and then embed one into the other.
The ability to build complex components made from several smaller components gives you more flexibility in how you model your schema and a more user-friendly interface for your content creators.
On the Schema side, you can create complex nested structures. For example, you can allow editors to create different parts of your website using the Section component that would host an array of other components. Those could be Hero, Flip-card, Image gallery, Video block, etc. All of the second level components can have lower level components too. Such content structure allows for unmatched editorial creativity, as well as the ability to specify what each section of your page can have.
On the Editor side, content professionals can edit their entries in one go. No more going back and forth between different building blocks - everything can be set up on the same page. In addition, nested components help “declutter” the UI: you won’t see all of the fields on your content entry until you choose to add the necessary component.
Nested components allow up to 4 levels of nesting, enabling use cases previously considered tedious to implement with relations.
Read more about how to use nested components in our documentation.
New permission to hide the schema view
To provide an even more streamlined editor experience for content creators, you can now make the schema view fully hidden through a custom role definition. This brings further flexibility in how you would like to define restrictions.
Improved new project creation flow
The project creation workflow has been simplified in order to provide the user the most efficient path during their product evaluation and everyday usage. Unnecessary friction through the inclusion of additional screens and clicks has been minimized and condensed where possible. The intention has been to streamline the experience for all users.
Empty state improvements
Empty state improvements provide a greater degree of discoverability to new and possibly existing users through all core features and functions of the product. They seek to both educate and increase project velocity by providing a mechanism to easily deploy pre-built examples with an additional explanatory copy for a first pass level of understanding.
An App is a standard web application that lives outside of the Hygraph main product, developed and hosted by a third party. It can be a simple FE-only static page, or a full-fledged web app written in any language, with backend, API, and a DB.
App Framework will allow a full extensibility of Hygraph similar to UI Extensions, but giving you more power and easier way to integrate third party apps, and distribute these integrations.
It's currently in closed beta. If you want to join our beta program and help us to improve it, you can join here.
As you know, we're back with this year's GraphQL Conf. with our friends at commercetools. With a couple of months to go, we've got some fantastic speakers lined up and some amazing GraphQL swags. Register for your free ticket and share it with your friends to win some swag!
Want to know when features roll out in real time to test, provide feedback and direction for Hygraph? Join our community through slack to stay up-to-date on all Hygraph announcements, events, and all the growing ways to get involved with Hygraph and our team.
Gijs is the Head of Product at Hygraph. When he's not focused on realizing our product vision, he spends time teaching others how to pronounce his first name.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.