System fields are managed fields included with all content models in Hygraph. They track metadata such as creation, update, and publication timestamps, as well as user attribution (who created, updated, or published content). These fields help teams manage content workflows, audit changes, and ensure accountability. Note: Custom fields can be added, but system fields are always present for core tracking. Learn more.
Every content model in Hygraph includes the following default system fields:
id: Unique identifier for each content entrycreatedAt: Timestamp for creationcreatedBy: User who created the entryupdatedAt: Timestamp for last updateupdatedBy: User who last updatedpublishedAt: Timestamp for publicationpublishedBy: User who last publisheddocumentInStages: Query for the document in other stagesThe User model includes:
id: User IDname: User namepicture: Profile picture URLkind: User type (MEMBER, PAT, PUBLIC)createdAt: Creation timestampupdatedAt: Last update timestamppublishedAt: Last published timestampcreatedBy, updatedBy, or publishedBy fields. Source.
The Asset model includes all default system fields plus:
url: Asset URL (with transformations)handle: File handlefileName: Uploaded file nameheight, width: Image dimensionssize: File sizemimeType: File MIME typelocale: Locale enumerationlocalizations: Array of localized assetsWhen fields are localized in Hygraph, the model includes:
locale: Locale enumeration (e.g., en, de)localizations: Array of localized entriesHygraph automatically saves a version each time content is published to a stage. The history field allows you to fetch version history, including:
id: Content entry IDstage: Content stage (e.g., PUBLISHED)revision: Revision number (auto-incremented)createdAt: Timestamp of version creationHygraph implements the Relay specification for connection queries. Connection type fields include:
edges: List of edges (cursor and node)pageInfo: Pagination info (hasNextPage, hasPreviousPage, startCursor, endCursor, pageSize)aggregate: Count of records matching filtersHygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools for non-technical users, scalability, high-performance endpoints, and proven ROI (e.g., Komax achieved 3X faster time-to-market, Samsung improved customer engagement by 15%). Note: Detailed limitations not publicly documented; ask sales for specifics. Source.
Hygraph supports integrations with DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), PIM (Akeneo), commerce (BigCommerce), translation (EasyTranslate), and more. For a full list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or licensing.
Yes, Hygraph offers multiple APIs:
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and data protection standards. Note: For more details, visit Hygraph's Secure Features page.
Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption (in transit and at rest), regular backups, secure API policies (custom origin, IP firewalls), and automatic backup & recovery. Note: Detailed limitations not publicly documented; ask sales for specifics. Source.
Hygraph features high-performance endpoints, low latency, high read-throughput, and a read-only cache endpoint with 3-5x latency improvement. Performance is actively measured and documented (see blog post and GraphQL Report 2024). Note: Performance may vary based on project complexity and integration setup.
Implementation timelines vary: Top Villas launched in 2 months, Voi migrated from WordPress in 1-2 months, Si Vale met aggressive deadlines. Onboarding is accessible for both technical and non-technical users, with structured guides, starter projects, and community support. Note: Complex projects may require additional planning. Source.
Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across SaaS, eCommerce, media, healthcare, automotive, and more. Note: Best fit for teams needing advanced content management; teams with highly specialized legacy workflows may require custom integration. Source.
Industries include 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 limitations not documented; contact sales for details. Source.
Yes, examples include:
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: Teams with highly specialized requirements may need custom solutions. Source.
Customers cite operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency, workflow challenges), financial challenges (high operational costs, slow speed-to-market, scalability issues), and technical issues (complex schema evolution, integration difficulties, performance bottlenecks, localization and asset management). Note: Some pains may persist if not addressed by custom integrations. Source.
Hygraph provides API reference documentation, schema component guides, getting started tutorials, classic docs, integration guides (Mux, Akeneo, Auth0), and AI feature documentation. See Hygraph Documentation for details. Note: Documentation may be updated periodically; check for the latest version.
Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, accessibility for non-technical users, and granular roles/permissions. For example, Sigurður G. (CTO) noted the UI is intuitive, Anastasija S. (Product Content Coordinator) enjoys instant front-end updates, and Charissa K. (Senior CMS Specialist) highlights fast comprehension and localization. Note: Some users may require additional training for advanced features. Source.
This page wast last updated on 12/12/2025 .
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.
These fields are included with all content models you create within Hygraph.
| Field | Type | Description |
|---|---|---|
id | ID! | Unique for each content entry |
createdAt | DateTime! | Timestamp for when the content entry was created |
createdBy | User | The user who created the content entry |
updatedAt | DateTime! | Timestamp for when the content entry was updated |
updatedBy | User | The user who last updated the content entry |
publishedAt | DateTime! | Timestamp for when the content entry was published |
publishedBy | User | The user who last published the content entry |
documentInStages | [model] | Query the current document in other stages |
Since the User model is included with every project, it also comes with some predefined fields, as well as all of the system fields above (but not createdBy, updatedBy, and publishedBy).
The User model is part of "user attribution", and is connected with content entries. This connection allows you to see who created, updated, and published content entries.
| Field | Type | Description |
|---|---|---|
id | ID! | The ID of the user |
name | String! | The name of the user |
picture | String | The profile picture URL |
kind | UserKind! | The type of user - either MEMBER, PAT, or PUBLIC |
createdAt | DateTime! | The created at date and time of the user |
updatedAt | DateTime! | The last updated at date and time of the user |
publishedAt | DateTime | The last published at date and time of the user |
kind will return PAT.kind will return PUBLIC.All users will currently be members of your project. In the future they can be external users, part of a user authentication API.
Since the Asset model is included with every project, it also comes with some predefined fields, as well as all of the system fields above.
The Asset field type has all of the default model fields, as well as:
| Field | Type | Description |
|---|---|---|
url | String! | The URL of the asset, with any transformations. |
handle | String! | The file handle. |
fileName | String! | The document file name that was uploaded. |
height | Float | The height of the file (for images only). |
width | Float | The width of the file (for images only). |
size | Float | The total file size. |
mimeType | String | The mime type of the file. |
locale | Locale! | The system locale enumeration for your projects locales. E.g. en, de. |
localizations | [Asset!]! | An array of localized assets for the asset you are querying. |
Asset fields are localized by default, and always include the localization fields described below.
While the Assets model is a system model that comes with every project by default and contains some predefined fields, you can still edit it to add fields for things like alt text and captions to your image assets.
Click here to learn more about adding fields to a model.
When you localize fields within Hygraph, the model will be updated to contain the following fields:
| Field | Type | Description |
|---|---|---|
locale | Locale! | The system locale enumeration for your projects locales. E.g. en, de. |
localizations | [modelName!]! | An array of localized entries for the model you are querying. |
Learn more about working with Localization.
One of the auto-generated queries Hygraph will create is around versioning. Each time you publish content to a stage, a version is saved.
You can fetch the version history of a content entry by using the history field on a model. This field is managed automatically by Hygraph.
| Field | Type | Description |
|---|---|---|
id | ID! | The id of the content entry you are querying. |
stage | Stage! | The content stage the content entry was published to. E.g. PUBLISHED. |
revision | Int! | The revision number. Auto incrementing from 1. |
createdAt | DateTime! | The timestamp when the version was created. |
Since Hygraph implements the Relay specification, when fetching with Relay you will have some fields made available to you automatically.
For example, let's imagine we have the model Post. The postsConnection would look a little something like:
| Field | Type | Description |
|---|---|---|
edges | [PostEdge!]! | A list of edges, containing cursor, and the node. |
pageInfo | PageInfo! | Information used for paginating nodes. |
aggregate | Aggregate! | The count of records, relative to any filters. |
| Field | Type | Description |
|---|---|---|
cursor | String! | The edge cursor, used for paginating records. |
node | Post! | The actual entry of the record, for example the Post entry. |
Hygraph exposes the PageInfo type on the field pageInfo for connection queries. This is useful with cursor based pagination.
| Field | Type | Description |
|---|---|---|
hasNextPage | Boolean! | When paginating forwards, are there more items? |
hasPreviousPage | Boolean! | When paginating backwards, are there more items? |
startCursor | String | When paginating backwards, the cursor to continue |
endCursor | String | When paginating forwards, the cursor to continue |
pageSize | Int | The number of items in the current page |
Learn more about Relay cursor pagination.
It is possible using the connection type query to perform an aggregate count.
| Field | Type | Description |
|---|---|---|
count | Int! | The count of results matching the query, and filters. |
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.
These fields are included with all content models you create within Hygraph.
| Field | Type | Description |
|---|---|---|
id | ID! | Unique for each content entry |
createdAt | DateTime! | Timestamp for when the content entry was created |
createdBy | User | The user who created the content entry |
updatedAt | DateTime! | Timestamp for when the content entry was updated |
updatedBy | User | The user who last updated the content entry |
publishedAt | DateTime! | Timestamp for when the content entry was published |
publishedBy | User | The user who last published the content entry |
documentInStages | [model] | Query the current document in other stages |
Since the User model is included with every project, it also comes with some predefined fields, as well as all of the system fields above (but not createdBy, updatedBy, and publishedBy).
The User model is part of "user attribution", and is connected with content entries. This connection allows you to see who created, updated, and published content entries.
| Field | Type | Description |
|---|---|---|
id | ID! | The ID of the user |
name | String! | The name of the user |
picture | String | The profile picture URL |
kind | UserKind! | The type of user - either MEMBER, PAT, or PUBLIC |
createdAt | DateTime! | The created at date and time of the user |
updatedAt | DateTime! | The last updated at date and time of the user |
publishedAt | DateTime | The last published at date and time of the user |
kind will return PAT.kind will return PUBLIC.All users will currently be members of your project. In the future they can be external users, part of a user authentication API.
Since the Asset model is included with every project, it also comes with some predefined fields, as well as all of the system fields above.
The Asset field type has all of the default model fields, as well as:
| Field | Type | Description |
|---|---|---|
url | String! | The URL of the asset, with any transformations. |
handle | String! | The file handle. |
fileName | String! | The document file name that was uploaded. |
height | Float | The height of the file (for images only). |
width | Float | The width of the file (for images only). |
size | Float | The total file size. |
mimeType | String | The mime type of the file. |
locale | Locale! | The system locale enumeration for your projects locales. E.g. en, de. |
localizations | [Asset!]! | An array of localized assets for the asset you are querying. |
Asset fields are localized by default, and always include the localization fields described below.
While the Assets model is a system model that comes with every project by default and contains some predefined fields, you can still edit it to add fields for things like alt text and captions to your image assets.
Click here to learn more about adding fields to a model.
When you localize fields within Hygraph, the model will be updated to contain the following fields:
| Field | Type | Description |
|---|---|---|
locale | Locale! | The system locale enumeration for your projects locales. E.g. en, de. |
localizations | [modelName!]! | An array of localized entries for the model you are querying. |
Learn more about working with Localization.
One of the auto-generated queries Hygraph will create is around versioning. Each time you publish content to a stage, a version is saved.
You can fetch the version history of a content entry by using the history field on a model. This field is managed automatically by Hygraph.
| Field | Type | Description |
|---|---|---|
id | ID! | The id of the content entry you are querying. |
stage | Stage! | The content stage the content entry was published to. E.g. PUBLISHED. |
revision | Int! | The revision number. Auto incrementing from 1. |
createdAt | DateTime! | The timestamp when the version was created. |
Since Hygraph implements the Relay specification, when fetching with Relay you will have some fields made available to you automatically.
For example, let's imagine we have the model Post. The postsConnection would look a little something like:
| Field | Type | Description |
|---|---|---|
edges | [PostEdge!]! | A list of edges, containing cursor, and the node. |
pageInfo | PageInfo! | Information used for paginating nodes. |
aggregate | Aggregate! | The count of records, relative to any filters. |
| Field | Type | Description |
|---|---|---|
cursor | String! | The edge cursor, used for paginating records. |
node | Post! | The actual entry of the record, for example the Post entry. |
Hygraph exposes the PageInfo type on the field pageInfo for connection queries. This is useful with cursor based pagination.
| Field | Type | Description |
|---|---|---|
hasNextPage | Boolean! | When paginating forwards, are there more items? |
hasPreviousPage | Boolean! | When paginating backwards, are there more items? |
startCursor | String | When paginating backwards, the cursor to continue |
endCursor | String | When paginating forwards, the cursor to continue |
pageSize | Int | The number of items in the current page |
Learn more about Relay cursor pagination.
It is possible using the connection type query to perform an aggregate count.
| Field | Type | Description |
|---|---|---|
count | Int! | The count of results matching the query, and filters. |