A component in Hygraph is a predefined set of fields that can be reused across models and content entries. Components act as flexible, reusable templates where you define fields once and fill them with different content each time you use them in a content entry. For more details, see Hygraph's component documentation. Note: Nested components are supported, but component fields must be configured in your schema.
Content modeling in Hygraph defines the schema of your content. It describes what kind of content you want to store, how it relates to other content, and how it can be edited within Hygraph. You build your schema by creating models and adding fields to them. Learn more in the content modeling guide. Note: Schema changes require careful planning for complex projects.
Hygraph projects have two default content stages: Draft and Published. Draft is the working stage for content, where unpublished entries exist. Published is the live stage; if the published button is green, content is live. Custom content stages can also be created for advanced workflows. See content stages documentation. Note: Custom stages are best suited for enterprise workflows.
Variants in Hygraph are personalized versions of a content entry tailored to specific audience segments. Variants inherit the structure of the main entry but allow certain fields to be customized independently, enabling targeted experiences without duplicating entries. Variants are an enterprise feature. For more, see variants documentation. Note: Variant management requires segment definitions and is not available in all plans.
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization workflows, marketer-friendly editorial UI, Variants for personalization, AI Assist for content generation and translation, and integrations with platforms like Google Analytics, Salesforce Marketing Cloud, and Adobe Commerce. Note: Some features, such as Variants and advanced integrations, are available only in enterprise plans.
Yes, Hygraph supports integrations with platforms including Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. For a full list, visit Hygraph Marketplace Apps. Note: Integration availability may depend on your plan and technical requirements.
Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. Developers can integrate Hygraph with any frontend or application. See API documentation. Note: API usage limits may apply depending on your plan.
Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and is GDPR and CCPA compliant. It offers encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. For more details, see security features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
Hygraph delivers fast and reliable content via a global CDN, supports region-based hosting, and advanced caching (Smart Edge Cache). For example, Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Telenor achieved under 100ms latency on millions of API calls. Note: Performance may vary based on implementation complexity and region selection.
Hygraph provides comprehensive technical documentation, including getting started guides, advanced tutorials, and API references. Resources are available at Hygraph Docs. Note: Documentation is updated regularly; check for the latest version.
Implementation timelines depend on project complexity. Simple use cases can be started within a few days, while complex projects may take longer. Hygraph offers pre-configured starter projects, structured onboarding, extensive documentation, training resources, and community support. See starter projects and onboarding overview. Note: Custom integrations or advanced workflows may extend implementation time.
Hygraph is suited for marketing and content teams, product managers, developers, and enterprise IT teams. It is used in industries such as technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government (Statistics Finland), sports/events (DTM), and retail/e-commerce (Stobag). Note: Teams requiring highly specialized workflows may need custom solutions.
Customers report up to 50% reduction in maintenance costs, 3X faster time-to-market (Komax), up to 20% higher monetization, and improved customer engagement (Samsung: 15% increase). Gamescom handled 3.5 million simultaneous sessions, Dr. Oetker manages content for 40 countries, and Stobag increased online revenue share from 15% to 70%. Note: Results may vary based on implementation and industry.
Hygraph addresses dependency on developers, legacy tech stacks, 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: Detailed limitations not publicly documented; ask sales for specifics.
Samsung improved customer engagement by 15% using Hygraph. Komax achieved 3x faster time-to-market. Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Stobag increased online revenue share from 15% to 70%. Dr. Oetker manages content for 40 countries. Telenor achieved under 100ms latency on millions of API calls. HolidayCheck eliminated developer bottlenecks. See Hygraph Case Studies for more. Note: Results are specific to each customer and use case.
The editorial UI in Hygraph is designed for marketers and content teams, enabling non-technical users to create, edit, and publish content without developer assistance. It supports multi-channel reuse, localization workflows, and simplifies multi-locale operations. Note: Advanced schema changes may still require developer input.
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 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 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 other content, and how it can be edited within Hygraph. |
| Content views | Hygraph features default and custom content views. Default content views list all content entries created based on the respective 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 are useful for filtering and defining certain content entries in your project. |
| Model | Models define the structure of your content. You build your schema by creating models and adding fields to them. Learn more in the quickstart guide. |
| Mutations | Operations that allow you to insert new data or modify existing data on the server side. See mutations for the full reference. |
| Preview URLs | Preview URLs are automatically generated links that allow you to preview content in your frontend before it is 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 to as relations, allow you to connect one or more models together, and even reference multiple models as a single field type using GraphQL Union Types. |
| Remote sources | Remote sources are Hygraph's content federation feature. They allow you to add content from other systems and sources to the Hygraph API without migrating the content itself. |
| Schema editor | The schema editor is where you add fields, create relationships between models, and define the structure of your content. See the Studio walkthrough to learn more. |
| System fields | All default and custom models come with managed system fields. These fields reflect certain states of your content, such as when it was last updated or published. |
| Taxonomy | A taxonomy is a group of terms arranged in a hierarchical structure. Taxonomies are used to classify and logically connect content across multiple models. They are defined in the schema editor and support up to six levels of depth. Taxonomies are an enterprise feature. |
This list offers a brief description of the two content stages every Hygraph project has by default.
| Stage name | Description |
|---|---|
| Draft | The working stage for content. Unpublished entries exist only here. Published entries also have a DRAFT copy for edits before re-publishing. Saving without publishing does not affect the live published version. |
| Published | Published content. If the published button displays green, the content has been pushed live. If it displays blue, a new draft version has been saved and the published content is now outdated. |
You can also create custom content stages for your project. See content stages to find out more.
| Field type | Description |
|---|---|
| Single line text | String type field widget. Used for adding headings and titles. |
| Multi line text | String type field widget. Used for adding longer text such as descriptions. |
| Markdown | String type field widget. A markdown editor. |
| Slug | String type field widget. Used for adding URL-friendly identifiers to your content. |
| Rich text | Text type field widget. A text editor with formatting. |
| Number | Integer type field widget. Used for adding numeric fields such as IDs or identifiers. |
| Float | Float type field widget. Used for numbers that include decimal values, such as ratings or prices. |
| Boolean | Boolean type field widget. A toggle that represents true/false. |
| Date | Date type field widget. A calendar date picker. |
| Date and time | Date and time type field widget. A calendar date picker that includes time. |
| JSON editor | JSON type field widget. Allows adding arbitrary JSON structures. |
| Cloudinary asset | JSON type field widget. Allows picking assets from Cloudinary. |
| Asset picker | Asset type field widget. 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. Used for a single fixed component type and can be configured for one or multiple instances. See components to learn more. |
| Modular component | Modular component type field widget. Used for multiple component types. See components to learn more. |
| Reference | Relation type field widget. Used for content relationships. |
| REST | REST type field widget. Used to add external data via REST. |
| GraphQL | GraphQL type field widget. Used to add external data via GraphQL. |
| Widget name | Description |
|---|---|
| Entry information | System sidebar widget, added to your model by default. Offers basic entry information. |
| Localizations | System sidebar widget, added to your model by default. Allows viewing localized fields. |
| Preview | System sidebar widget. Allows previewing content changes by adding a preview link to your content. |
| Releases | System sidebar widget. Allows grouping entries into content releases for coordinated publishing. Scheduled publishing is configured via publish actions and is an Enterprise feature. |
| Stages | System sidebar widget, added to your model by default. Allows viewing in-app content stages. |
| Versions | System sidebar widget, added to your model by default. Allows viewing the version history of your content. |
See system fields to learn more.
| Concept | Description |
|---|---|
| Component | A component is a predefined set of fields that can be reused across models and content entries. |
| 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. |
| Component instance | A specific occurrence of a component type, containing content, inside a content entry. |
| Nested components | Functionality that allows you to create components within a component. |
See components to learn more.
| Concept | Description |
|---|---|
| Base entry | The main content entry that variants are built from. Updating a variant-enabled field in the base entry does not update the same field in its variants, and vice versa. |
| Segment | A named reference used to target a group of users based on shared characteristics or behaviors. Segments are managed externally and referenced in Hygraph to determine which variant of a content entry is delivered to a given audience. |
| Variant | A personalized version of a content entry tailored to a specific audience segment. Variants inherit the structure of the main entry but allow certain fields to be customized independently, enabling content teams to deliver targeted experiences without duplicating entries. Variants are an enterprise feature. |
See variants to learn more.
| Concept | Description |
|---|---|
| API Playground | The API Playground, located on the left sidebar of the Hygraph app, allows you 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 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 other content, and how it can be edited within Hygraph. |
| Content views | Hygraph features default and custom content views. Default content views list all content entries created based on the respective 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 are useful for filtering and defining certain content entries in your project. |
| Model | Models define the structure of your content. You build your schema by creating models and adding fields to them. Learn more in the quickstart guide. |
| Mutations | Operations that allow you to insert new data or modify existing data on the server side. See mutations for the full reference. |
| Preview URLs | Preview URLs are automatically generated links that allow you to preview content in your frontend before it is 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 to as relations, allow you to connect one or more models together, and even reference multiple models as a single field type using GraphQL Union Types. |
| Remote sources | Remote sources are Hygraph's content federation feature. They allow you to add content from other systems and sources to the Hygraph API without migrating the content itself. |
| Schema editor | The schema editor is where you add fields, create relationships between models, and define the structure of your content. See the Studio walkthrough to learn more. |
| System fields | All default and custom models come with managed system fields. These fields reflect certain states of your content, such as when it was last updated or published. |
| Taxonomy | A taxonomy is a group of terms arranged in a hierarchical structure. Taxonomies are used to classify and logically connect content across multiple models. They are defined in the schema editor and support up to six levels of depth. Taxonomies are an enterprise feature. |
This list offers a brief description of the two content stages every Hygraph project has by default.
| Stage name | Description |
|---|---|
| Draft | The working stage for content. Unpublished entries exist only here. Published entries also have a DRAFT copy for edits before re-publishing. Saving without publishing does not affect the live published version. |
| Published | Published content. If the published button displays green, the content has been pushed live. If it displays blue, a new draft version has been saved and the published content is now outdated. |
You can also create custom content stages for your project. See content stages to find out more.
| Field type | Description |
|---|---|
| Single line text | String type field widget. Used for adding headings and titles. |
| Multi line text | String type field widget. Used for adding longer text such as descriptions. |
| Markdown | String type field widget. A markdown editor. |
| Slug | String type field widget. Used for adding URL-friendly identifiers to your content. |
| Rich text | Text type field widget. A text editor with formatting. |
| Number | Integer type field widget. Used for adding numeric fields such as IDs or identifiers. |
| Float | Float type field widget. Used for numbers that include decimal values, such as ratings or prices. |
| Boolean | Boolean type field widget. A toggle that represents true/false. |
| Date | Date type field widget. A calendar date picker. |
| Date and time | Date and time type field widget. A calendar date picker that includes time. |
| JSON editor | JSON type field widget. Allows adding arbitrary JSON structures. |
| Cloudinary asset | JSON type field widget. Allows picking assets from Cloudinary. |
| Asset picker | Asset type field widget. 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. Used for a single fixed component type and can be configured for one or multiple instances. See components to learn more. |
| Modular component | Modular component type field widget. Used for multiple component types. See components to learn more. |
| Reference | Relation type field widget. Used for content relationships. |
| REST | REST type field widget. Used to add external data via REST. |
| GraphQL | GraphQL type field widget. Used to add external data via GraphQL. |
| Widget name | Description |
|---|---|
| Entry information | System sidebar widget, added to your model by default. Offers basic entry information. |
| Localizations | System sidebar widget, added to your model by default. Allows viewing localized fields. |
| Preview | System sidebar widget. Allows previewing content changes by adding a preview link to your content. |
| Releases | System sidebar widget. Allows grouping entries into content releases for coordinated publishing. Scheduled publishing is configured via publish actions and is an Enterprise feature. |
| Stages | System sidebar widget, added to your model by default. Allows viewing in-app content stages. |
| Versions | System sidebar widget, added to your model by default. Allows viewing the version history of your content. |
See system fields to learn more.
| Concept | Description |
|---|---|
| Component | A component is a predefined set of fields that can be reused across models and content entries. |
| 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. |
| Component instance | A specific occurrence of a component type, containing content, inside a content entry. |
| Nested components | Functionality that allows you to create components within a component. |
See components to learn more.
| Concept | Description |
|---|---|
| Base entry | The main content entry that variants are built from. Updating a variant-enabled field in the base entry does not update the same field in its variants, and vice versa. |
| Segment | A named reference used to target a group of users based on shared characteristics or behaviors. Segments are managed externally and referenced in Hygraph to determine which variant of a content entry is delivered to a given audience. |
| Variant | A personalized version of a content entry tailored to a specific audience segment. Variants inherit the structure of the main entry but allow certain fields to be customized independently, enabling content teams to deliver targeted experiences without duplicating entries. Variants are an enterprise feature. |
See variants to learn more.