A content model is a foundational unit of a content schema within Hygraph. Content models are made up of fields that give the model its structure and define its purpose. They also describe how the model is contextualized using relations. For more details, see the Hygraph documentation on models. Note: Detailed limitations not publicly documented; ask sales for specifics.
A content entry is the result of adding content to a model in Hygraph. Once content is added and saved to a content model, it becomes a content entry. Entries can be created after all content is added or while content is still in progress. Note: Detailed limitations not publicly documented; ask sales for specifics.
Custom content views in Hygraph allow editors to customize the presentation and selection of content by showing or hiding columns and filtering which content is displayed. This feature helps build optimized editorial workflows and makes it easier to locate relevant content. Note: Custom content views are limited to the configuration options available in the Content Studio; advanced customizations may require API or SDK usage.
To create a custom content view in Hygraph: 1) Navigate to the content for one of your models. 2) Filter content or show/hide columns as needed. 3) At the top of the content window, click "Create Content View." 4) Provide a name and description, then press Create. Note: The ability to create custom views is subject to user permissions and project configuration.
To edit a custom content view, navigate to the view in the contextual sidebar of the content tab. Next to the title, click the three dots and select "Edit Content View." Make your changes and save. To delete, use the same menu and select the delete option. Note: Editing and deleting views may be restricted by user permissions.
Yes, you can create custom views for assets in Hygraph. Navigate to the assets view, filter or show/hide columns as needed, then click "Create Content View" at the top. Provide a name and description, then create the view. This helps categorize assets by format (e.g., PNG, SVG, JPG). Note: Asset view customization is limited to the options available in the Content Studio.
Key features of Hygraph include: GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization, granular permissions, high-performance endpoints, and a user-friendly interface for non-technical users. Note: Advanced use cases may require developer involvement for API or SDK integration. Source.
Hygraph supports integrations with 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), translation/localization (EasyTranslate), and others. For a full list, visit the Hygraph Marketplace. Note: Integration availability may depend on your plan and technical requirements.
Yes, Hygraph provides multiple APIs: GraphQL Content API (for querying and manipulating content), Management API (for project structure), Asset Upload API (for uploading assets), and MCP Server API (for secure AI assistant communication). See the API Reference documentation for details. Note: API usage may require technical expertise.
Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international security and privacy standards. Note: For industry-specific compliance needs, contact Hygraph sales. Source.
Hygraph offers 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). All endpoints use SSL certificates. Note: Some features may be limited to enterprise plans. Source.
Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph offers structured onboarding, starter projects, and extensive documentation to support quick adoption. Note: Large-scale migrations may require additional planning. Source.
Customers praise Hygraph's intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Note: Some advanced configurations may require technical expertise. Source.
Customers have achieved faster time-to-market (e.g., Komax: 3x faster), improved engagement (Samsung: 15% increase), and cost reduction (AutoWeb: 20% increase in monetization). Hygraph supports content consistency and scalability for global teams. Note: Results depend on implementation and organizational readiness. Source.
Hygraph is used by companies in SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Note: Industry-specific requirements may affect suitability. Source.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some pain points may require custom development or integration work. Source.
Technical documentation is available at hygraph.com/docs, including API references, schema guides, onboarding, integration guides, and AI features. Classic documentation is available for legacy users. Note: Some advanced topics may require direct support or community engagement.
This page wast last updated on 12/12/2025 .
Last updated by Ronak & Jamie
on Jan 21, 2026Originally written by Ronak & Jamie
Once you’ve defined your content models in Hygraph, working with the intuitive Content Studio makes it a breeze to manage your content. However, there are times when the content views may be better configured to let each user see what matters most to them, and make it easier to handle a growing volume of content entries.
Here’s a quick video on how to work with Content Views in Hygraph.
Custom Content Views and View Groups allow you to customize the presentation of your content entries, and the selection of content visible to an editor.
You can show or hide different columns and filter which content should be included in the group. This allows for an optimized editorial workflow, helping editors to quickly find the content that needs their attention.
To better illustrate this, let’s use the Hygraph project for Build Your DXP.
tool for this one.V in their Name.Tools with V.Now, Tools with V may not be the most descriptive to several authors. So let’s edit that to refine the naming.
Tools with V to Tool names that have the letter V.The same principles apply when creating Custom Views for assets.
PNG, SVG, and JPG, to make it easier to categorize by format.Frequently Asked Questions
A content model is a foundational unit of a content schema within Hygraph. Content models are fields which give the model its structure and help define its purpose. A content model also describes how the model is contextualized using relations. For more on content models and all of the fields that can make up a content model, check out our documentation on models.
A content entry is one is the outcome of adding content to a model. After content has been added to a content model and it is saved, then you have a content entry. Content entries can be created after all of the content has been added to the model or when it is still in progress.
Custom content views enable the editor to customize the presentation and selection of content visible by showing or hiding columns and filtering out which content should be displayed. They can be a powerful feature to build optimized workflows and make it quick and easy to locate content.
Blog Authors
Hear from the people who use the Hygraph website daily and inherit the codebase.
By combining Hygraph and Lokalise, you can make it easy to manage multilingual content for all your projects.
Learn about the best CMS options for your Nuxt.js projects.
Last updated by Ronak & Jamie
on Jan 21, 2026Originally written by Ronak & Jamie
Once you’ve defined your content models in Hygraph, working with the intuitive Content Studio makes it a breeze to manage your content. However, there are times when the content views may be better configured to let each user see what matters most to them, and make it easier to handle a growing volume of content entries.
Here’s a quick video on how to work with Content Views in Hygraph.
Custom Content Views and View Groups allow you to customize the presentation of your content entries, and the selection of content visible to an editor.
You can show or hide different columns and filter which content should be included in the group. This allows for an optimized editorial workflow, helping editors to quickly find the content that needs their attention.
To better illustrate this, let’s use the Hygraph project for Build Your DXP.
tool for this one.V in their Name.Tools with V.Now, Tools with V may not be the most descriptive to several authors. So let’s edit that to refine the naming.
Tools with V to Tool names that have the letter V.The same principles apply when creating Custom Views for assets.
PNG, SVG, and JPG, to make it easier to categorize by format.Frequently Asked Questions
A content model is a foundational unit of a content schema within Hygraph. Content models are fields which give the model its structure and help define its purpose. A content model also describes how the model is contextualized using relations. For more on content models and all of the fields that can make up a content model, check out our documentation on models.
A content entry is one is the outcome of adding content to a model. After content has been added to a content model and it is saved, then you have a content entry. Content entries can be created after all of the content has been added to the model or when it is still in progress.
Custom content views enable the editor to customize the presentation and selection of content visible by showing or hiding columns and filtering out which content should be displayed. They can be a powerful feature to build optimized workflows and make it quick and easy to locate content.
Blog Authors
Hear from the people who use the Hygraph website daily and inherit the codebase.
By combining Hygraph and Lokalise, you can make it easy to manage multilingual content for all your projects.
Learn about the best CMS options for your Nuxt.js projects.