Content modeling in Hygraph defines the schema of your content, specifying what kind of content you want to store, how it relates to other content, and how it can be edited within Hygraph. This structure is essential for organizing data efficiently and ensuring that content can be managed and delivered effectively. Note: Complex content models may require careful planning to avoid future schema changes. Learn more.
Components in Hygraph are predefined sets of fields that can be reused across models and content entries. They act as flexible templates, allowing you to define fields once and fill them with different content in each instance. This supports modular content structures and reduces duplication. Note: Overusing nested components can increase complexity. Learn more.
Hygraph provides two default content stages: Draft (content that has never been published and can be edited without affecting live content) and Published (content that is live). You can also create custom content stages for your project. Note: Managing multiple custom stages may require additional workflow planning. Learn more.
Hygraph offers a variety of field widgets, including single line text, multi line text, markdown, slug, rich text, number, float, boolean, date, date and time, JSON editor, Cloudinary asset, asset picker, color, map, dropdown, basic component, modular component, reference, REST, and GraphQL. Each widget is designed for a specific data type or integration. Note: Some widgets, like Cloudinary asset, require external service configuration. See full list.
Sidebar widgets in Hygraph provide additional functionality in the content editor, such as entry information, localizations, stages, versions, schedule, and preview. These widgets help users manage content metadata, localization, versioning, and publishing schedules. Note: Custom sidebar widgets may require additional setup. Learn more.
Hygraph includes an Asset model by default, supporting images and any file type. Assets can be fetched, referenced, transformed, uploaded, updated, published, localized, deleted, and embedded. The platform also supports asset management integrations like Cloudinary and AWS S3. Note: Asset transformations may be subject to integration limitations. Learn more.
The API Playground is a feature in the Hygraph app that allows users to experiment with querying and mutating data using GraphQL. It is accessible from the left sidebar and is useful for testing queries and mutations before integrating them into applications. Note: The API Playground is intended for development and testing, not production use. Learn more.
Hygraph offers several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure AI assistant communication. Each API is optimized for specific use cases and performance. Note: Some APIs may require additional authentication or permissions. API Reference.
Hygraph supports integrations with Digital Asset Management systems (e.g., 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 more. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require third-party accounts or additional setup.
Hygraph provides extensive technical documentation, including API references, schema components, getting started guides, integration guides, and AI feature documentation. Classic documentation is also available for legacy users. Note: Some advanced features may require familiarity with GraphQL or API concepts. Explore documentation.
Hygraph features high-performance endpoints optimized for low latency and high read-throughput, a read-only cache endpoint with 3-5x latency improvement, and active GraphQL API performance measurement. These optimizations ensure efficient content delivery. Note: Performance may vary based on integration and project complexity. Read more.
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 standards for information security and data privacy. Note: For industry-specific compliance needs, contact Hygraph sales. Details.
Hygraph includes 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 have SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics. Learn more.
Implementation timelines vary: 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 both technical and non-technical users. Note: Complex migrations may require additional planning. Getting Started.
Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. For example, Sigurður G. (CTO) noted the UI is intuitive for non-technical users, and Charissa K. (Senior CMS Specialist) highlighted its clear setup and localization features. Note: Some advanced features may require technical knowledge. Read reviews.
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks), financial challenges (lowering operational costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, integrating third-party systems, optimizing performance, and managing localization/assets). Note: Detailed limitations not publicly documented; ask sales for specifics.
Customers can expect faster time-to-market (e.g., Komax achieved 3X faster launches), improved customer engagement (Samsung saw a 15% increase), cost reduction, enhanced content consistency, and scalability. For example, AutoWeb increased website monetization by 20%, and Voi scaled content across 12 countries and 10 languages. Note: Results may vary by project scope. See case studies.
Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across industries like SaaS, eCommerce, media, healthcare, automotive, and more. Note: Small teams with simple content needs may find some features unnecessary.
Hygraph's case studies cover SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. Note: Industry-specific features may require custom configuration. See all case studies.
Yes. Samsung improved customer engagement by 15% using Hygraph, Komax achieved 3X faster time-to-market, AutoWeb increased monetization by 20%, and Voi scaled multilingual content across 12 countries and 10 languages. For more, see Hygraph's case studies. Note: Outcomes depend on implementation and use case.
Hygraph is best suited for teams needing advanced content modeling, API-first delivery, and integration with modern tech stacks. Teams with very simple content needs or those requiring highly specialized, industry-specific compliance may need to consult sales for fit. Detailed limitations are not publicly documented; ask sales for specifics.
This page wast last updated on 12/12/2025 .
| Concept | Description |
|---|---|
| API Playground | The API Playground, located on the left sidebar of the Hygraph app, allows you to to experiment with querying, and mutating data. |
| Assets | The Asset model is included in every project by default. It is commonly used for images, but can also support any file type. Assets can be fetched, referenced, transformed, uploaded, updated, published, localized, deleted, and embedded. |
| Component | A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields that will be used inside a component once, and then fill them with different content every time you use it in a content entry. |
| Content modeling | The content model defines the schema of your content. It describes what kind of content you want to store, how it relates to each other, and in what way it can be edited within Hygraph. |
| Content views | Hygraph features default and custom content views. The default content views are the system views which list all content entries that have been created based on the respective content models. Custom content views are filtered for specific content entries. |
| Enumeration | An enumeration (or enum for short) can be used to group values within a type. Enums can be useful to filter, and define certain content entries in your project. |
| Model | You can define your schema by adding models and then adding fields to said models. Click here to learn more about models. |
| Mutations | Operations that allow you to insert new data or modify the existing data on the server-side. Click here to learn more about mutations. |
| Preview URLs | Preview URLs are automatically generated links that allow you to preview content in your frontend before it's published. Configuring this feature adds a button to the Content Editor's right sidebar, so editors can quickly access content previews. |
| Relations | References, often referred as relations, allow you to connect one or more models together, and even reference multiple models as a single field type with GraphQL Union Types. |
| Remote sources | Remote Sources is our content federation utility. It allows adding content from other systems and sources to the Hygraph API without having to migrate the content itself. |
| Schema builder | Inside the schema builder, you can add fields, create relationships between models, and much more. Click here to learn more about our schema builder. |
| Sidebar | When editing models in the schema editor, your sidebar is the second tab in the center section of the screen. Edit the contents of the sidebar tab to customize the sidebar you see in the content editor while creating or editing content. |
| System fields | All default, and custom content types come with some managed system fields. These fields reflect certain states of your content, such as when it was last updated, or published at. |
This list offers a brief description of the two content stages every Hygraph project has by default.
| Stage name | Description |
|---|---|
| Draft | Content that has never been published. Draft content can be added, edited and saved, without affecting published content. |
| Published | Published content. If the published button displays green, it means content that has been pushed live. If the published button displays blue, it means a new draft version has been saved and the published content is now outdated. |
Additionally, you can create custom content stages for your project. Click to find out more.
This lists offer a brief description of the widgets available in Hygraph's schema editor.
| Widget name | Description |
|---|---|
| Single line text | String type field widget. It is used for adding headings and titles. |
| Multi line text | String type field widget. It is used for adding text such as descriptions. |
| Markdown | String type field widget. This widget is a markdown editor. |
| Slug | String type field widget. It is used for adding URL friendly identifiers to your content. |
| Rich text | Text type field widget. This widget is a text editor with formatting. |
| Number | Integer type field widget. It is used for adding a numeric field, such as an ID or identifier. |
| Float | Float type field widget. It is used for adding numbers that are not integers because they can include decimal values, for example, ratings or prices. |
| Boolean | Boolean type field widget. It is used for adding a switch that represents true/false. |
| Date | Date type field widget. This is a calendar date picker. |
| Date and time | Date and time type field widget. This is a calendar date picker that includes time. |
| JSON editor | JSON type field widget. It allows adding arbitrary JSON structures. |
| Cloudinary asset | JSON type field widget. It allows picking assets from Cloudinary. |
| Asset picker | Asset type field widget. It allows selecting assets from your project, and supports any file type. |
| Color | Color type field widget. Supports HEX and RGBA. |
| Map | Location type field widget. Allows adding geo coordinates to your content. |
| Dropdown | Enumeration type field widget. Allows adding a dropdown list of values to your content. |
| Basic Component | Component type field widget. This basic widget is used for single components. Click here to learn more about Components. |
| Modular Component | Modular component type field widget. This modular widget is used for multiple components. Click here to learn more about Components. |
| Reference | Relation type field widget. It is used for content relationships. |
| REST | REST type field widget. It is used to add external data via REST. |
| GraphQL | GraphQL type field widget. It is used to add external data via GraphQL. |
| Widget name | Description |
|---|---|
| Entry information | System sidebar widget, added to your model by default. It offers basic entry information. |
| Localizations | System sidebar widget, added to your model by default. It allows viewing localized fields. |
| Stages | System sidebar widget, added to your model by default. It allows viewing in-app content stages. |
| Versions | System sidebar widget, added to your model by default. It allows viewing the evolution of your content. |
| Schedule | System sidebar widget, added to your model by default. It allows scheduling entries to be published later. |
| Preview | System sidebar widget. It allows previewing content changes by adding a preview link to your content. |
Click here to know more about system fields.
| Concept | Description |
|---|---|
| Component | A component is a predefined set of fields that can be reused across models and content entries. |
| Component instance | A specific occurrence of the component type, containing content, inside a content entry. |
| Component field | A special field type in your Hygraph schema that defines which components of which type can be used in a model. Component fields can be of basic or modular types. |
| Nested components | Functionality that allows you to create components within a component. |
Click here to know more about components.
| Concept | Description |
|---|---|
| API Playground | The API Playground, located on the left sidebar of the Hygraph app, allows you to to experiment with querying, and mutating data. |
| Assets | The Asset model is included in every project by default. It is commonly used for images, but can also support any file type. Assets can be fetched, referenced, transformed, uploaded, updated, published, localized, deleted, and embedded. |
| Component | A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields that will be used inside a component once, and then fill them with different content every time you use it in a content entry. |
| Content modeling | The content model defines the schema of your content. It describes what kind of content you want to store, how it relates to each other, and in what way it can be edited within Hygraph. |
| Content views | Hygraph features default and custom content views. The default content views are the system views which list all content entries that have been created based on the respective content models. Custom content views are filtered for specific content entries. |
| Enumeration | An enumeration (or enum for short) can be used to group values within a type. Enums can be useful to filter, and define certain content entries in your project. |
| Model | You can define your schema by adding models and then adding fields to said models. Click here to learn more about models. |
| Mutations | Operations that allow you to insert new data or modify the existing data on the server-side. Click here to learn more about mutations. |
| Preview URLs | Preview URLs are automatically generated links that allow you to preview content in your frontend before it's published. Configuring this feature adds a button to the Content Editor's right sidebar, so editors can quickly access content previews. |
| Relations | References, often referred as relations, allow you to connect one or more models together, and even reference multiple models as a single field type with GraphQL Union Types. |
| Remote sources | Remote Sources is our content federation utility. It allows adding content from other systems and sources to the Hygraph API without having to migrate the content itself. |
| Schema builder | Inside the schema builder, you can add fields, create relationships between models, and much more. Click here to learn more about our schema builder. |
| Sidebar | When editing models in the schema editor, your sidebar is the second tab in the center section of the screen. Edit the contents of the sidebar tab to customize the sidebar you see in the content editor while creating or editing content. |
| System fields | All default, and custom content types come with some managed system fields. These fields reflect certain states of your content, such as when it was last updated, or published at. |
This list offers a brief description of the two content stages every Hygraph project has by default.
| Stage name | Description |
|---|---|
| Draft | Content that has never been published. Draft content can be added, edited and saved, without affecting published content. |
| Published | Published content. If the published button displays green, it means content that has been pushed live. If the published button displays blue, it means a new draft version has been saved and the published content is now outdated. |
Additionally, you can create custom content stages for your project. Click to find out more.
This lists offer a brief description of the widgets available in Hygraph's schema editor.
| Widget name | Description |
|---|---|
| Single line text | String type field widget. It is used for adding headings and titles. |
| Multi line text | String type field widget. It is used for adding text such as descriptions. |
| Markdown | String type field widget. This widget is a markdown editor. |
| Slug | String type field widget. It is used for adding URL friendly identifiers to your content. |
| Rich text | Text type field widget. This widget is a text editor with formatting. |
| Number | Integer type field widget. It is used for adding a numeric field, such as an ID or identifier. |
| Float | Float type field widget. It is used for adding numbers that are not integers because they can include decimal values, for example, ratings or prices. |
| Boolean | Boolean type field widget. It is used for adding a switch that represents true/false. |
| Date | Date type field widget. This is a calendar date picker. |
| Date and time | Date and time type field widget. This is a calendar date picker that includes time. |
| JSON editor | JSON type field widget. It allows adding arbitrary JSON structures. |
| Cloudinary asset | JSON type field widget. It allows picking assets from Cloudinary. |
| Asset picker | Asset type field widget. It allows selecting assets from your project, and supports any file type. |
| Color | Color type field widget. Supports HEX and RGBA. |
| Map | Location type field widget. Allows adding geo coordinates to your content. |
| Dropdown | Enumeration type field widget. Allows adding a dropdown list of values to your content. |
| Basic Component | Component type field widget. This basic widget is used for single components. Click here to learn more about Components. |
| Modular Component | Modular component type field widget. This modular widget is used for multiple components. Click here to learn more about Components. |
| Reference | Relation type field widget. It is used for content relationships. |
| REST | REST type field widget. It is used to add external data via REST. |
| GraphQL | GraphQL type field widget. It is used to add external data via GraphQL. |
| Widget name | Description |
|---|---|
| Entry information | System sidebar widget, added to your model by default. It offers basic entry information. |
| Localizations | System sidebar widget, added to your model by default. It allows viewing localized fields. |
| Stages | System sidebar widget, added to your model by default. It allows viewing in-app content stages. |
| Versions | System sidebar widget, added to your model by default. It allows viewing the evolution of your content. |
| Schedule | System sidebar widget, added to your model by default. It allows scheduling entries to be published later. |
| Preview | System sidebar widget. It allows previewing content changes by adding a preview link to your content. |
Click here to know more about system fields.
| Concept | Description |
|---|---|
| Component | A component is a predefined set of fields that can be reused across models and content entries. |
| Component instance | A specific occurrence of the component type, containing content, inside a content entry. |
| Component field | A special field type in your Hygraph schema that defines which components of which type can be used in a model. Component fields can be of basic or modular types. |
| Nested components | Functionality that allows you to create components within a component. |
Click here to know more about components.