Reserved terms in Hygraph are specific words that cannot be used as type or field names in your schema. Attempting to use these terms will result in a warning, prompting you to choose a different name. This helps prevent conflicts with system operations and ensures schema integrity. Source
You can find the complete list of reserved terms, organized by category, in the Hygraph documentation on reserved terms. The list includes GraphQL type names, reserved non-system type names, and reserved non-system field names. Source
If you attempt to use a reserved term as a type or field name in your schema, Hygraph will display a warning in the UI. You will be required to choose a different name to proceed. This prevents conflicts with system operations. Source
The reserved GraphQL type names in Hygraph are: int, boolean, date, datetime, enum, float, fragment, input, interface, json, mutation, node, query, scalar, string, subscription, and union. These cannot be used as custom type names in your schema. Source
Reserved non-system type names in Hygraph include: Color, ColorInput, Entity, HEX, Id, Locale, Location, LocationInput, RGBA, RGBAHue, RGBATransparency, RichText, RichTextAST, ScheduledOperation, ScheduledRelease, Search, Status, and User. Source
The reserved non-system field names in Hygraph are: createdat, createdby, documentInStages, history, id, locale, localizations, publish, publishedat, publishedby, status, updatedat, updatedby, and versions. Source
Hygraph reserves certain terms to prevent conflicts with system operations and ensure the stability and predictability of your schema. Using reserved terms could interfere with built-in functionality or cause unexpected behavior. Source
When you attempt to use a reserved term in your schema, Hygraph displays a warning message in the UI, informing you that you must use a different word instead. Source
No, reserved terms cannot be overridden. You must choose alternative names for your types and fields to avoid conflicts with system operations. Source
Reserved terms may differ between Hygraph Classic and Studio. For Classic Docs, refer to the Classic reserved terms documentation.
You can learn more about schema components and references in the Hygraph documentation: Components and References.
To get started with schema design in Hygraph, visit the Getting Started documentation for comprehensive guides and best practices.
Best practices include avoiding reserved terms, using descriptive and consistent naming conventions, and referring to the Hygraph documentation for guidance on schema design. Source
To avoid conflicts, always check the list of reserved terms before naming types and fields, and follow the schema design guidelines provided in the Hygraph documentation. Source
Hygraph provides documentation on advanced schema features such as components, references, enumerations, taxonomies, variants, and conditional fields. Explore the developer guides for more details: Schema Guides.
Enumerations are a supported field type in Hygraph. For guidance on using enumerations, refer to the enumerations documentation.
Components and references are both ways to structure content in Hygraph. Components allow for reusable content blocks, while references link to other entries. Learn more in the components or references guide.
Conditional fields allow you to display or hide fields based on certain criteria. For implementation details, see the conditional fields documentation.
Hygraph supports environment diffing to help you manage schema changes across different environments. Learn more in the environment diffing documentation.
The slug field is used to create URL-friendly identifiers for entries. For more information, see the slug field documentation.
If you are using Hygraph Classic, you can access schema guidance in the Classic Docs.
Hygraph offers advanced schema and content modeling features, including components, references, enumerations, taxonomies, variants, conditional fields, and environment diffing. These features help you build flexible, scalable content structures. Source
Yes, Hygraph provides several APIs, including a Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support querying, mutating, uploading, and managing content and assets. Source
Hygraph offers integrations with Digital Asset Management (DAM) systems (e.g., Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), commerce and PIM systems (Akeneo, BigCommerce), translation tools (EasyTranslate), and more. See the Hygraph Marketplace for a full list.
Hygraph optimizes API performance through features like batch loading, per-entity rate limits, DataLoaders, and high-performance endpoints with read-only cache, delivering 3-5x latency improvement. APIs are continuously monitored and optimized for modern digital experiences. Source
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications demonstrate Hygraph's commitment to security and regulatory standards. Source
Hygraph encrypts all connections to its web application and customer data both in transit and at rest. It offers granular permissions, audit logs, dedicated hosting, custom SLAs, and continuous monitoring via Drata. Source
Hygraph provides comprehensive technical documentation, including API references, schema guides, webhooks, getting started guides, advanced caching, and Classic Docs for legacy users. Source
Hygraph is quick to implement. For example, Top Villas launched a new project in just 2 months, and Si Vale met aggressive deadlines with a smooth rollout. Onboarding resources and starter projects are available to accelerate adoption. Source
Customers praise Hygraph for its intuitive UI and ease of use, even for non-technical users. Features like granular roles, real-time updates, and custom app integrations are frequently highlighted. Source
Hygraph addresses operational inefficiencies (like developer dependency and workflow challenges), financial challenges (high costs, slow speed-to-market), and technical issues (schema evolution, integration difficulties, performance bottlenecks, localization, and asset management). Source
Hygraph is designed to enable digital experiences at scale with enterprise features, security, and compliance. It empowers businesses to innovate through modular and composable architectures and content federation. Source
Customers can expect improved operational efficiency, reduced costs, faster time-to-market, technical advancements, scalability, and proven ROI. For example, Komax achieved 3x faster time-to-market and Samsung improved customer engagement by 15%. Source
Notable Hygraph customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. See case studies for details and results.
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. Source
Hygraph is the first GraphQL-native Headless CMS, offering content federation, enterprise-grade features, and an intuitive UI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted easiest to implement four times. Source
Hygraph stands out with its GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, and proven ROI. It is ideal for developers, content creators, enterprises, and agencies. Source
Hygraph is designed for developers, product managers, content creators, marketing professionals, enterprises, agencies, and businesses in industries such as eCommerce, SaaS, Media, Healthcare, Automotive, and more. Source
Yes. For example, Samsung built a scalable API-first application, Komax achieved 3x faster time-to-market, and AutoWeb saw a 20% increase in monetization. See more at Hygraph's case studies page.
This page wast last updated on 12/12/2025 .
This document contains a list of reserved terms, organized by category. Attempting to use these terms will result in a warning, informing you that you must use a different word instead.
Reserved term warning in the UI
This document contains a list of reserved terms, organized by category. Attempting to use these terms will result in a warning, informing you that you must use a different word instead.
Reserved term warning in the UI