The Hygraph Getting Started tutorial teaches you how to plan your content flow, build schemas in layers of complexity, work with queries and mutations, and connect your project to a frontend. See the full lessons list.
Best practices include keeping business goals in mind, planning and sketching your content flow before using the schema builder, building complex schemas in layers, and naming models and fields intuitively for collaboration.
You can read the Essential Guide to Content Modeling for in-depth advice and examples.
Start by identifying your business goals, sketching your content flow, and then using the schema builder to create models and fields that reflect your workflow. Detailed steps are available in the Plan your content flow guide.
You can build content models by adding fields, components, and references. The process is covered in the Design content models and Build content models guides.
Hygraph supports GraphQL queries and mutations for reading and writing data. You can practice with the API Playground and follow the Queries and Mutations exercises.
You can connect Hygraph to your frontend by using its GraphQL APIs. Step-by-step instructions are available in the Frontend creation guide.
Name models and fields clearly and intuitively so collaborators can work efficiently. This helps teams manage content creation and approval in a structured way.
Explore the Hygraph Documentation, including Developer Guides and API Reference, for advanced features and best practices.
Reference fields can be configured in your schema to link models together. Detailed instructions are available in the Configure reference fields guide.
Components can be created and added to models to structure content. Learn more in the Build components and Add components to models guides.
Remote sources allow you to connect external data. You can configure them by following the Add Remote Source and Remote Fields guides.
Hygraph supports content localization. You can learn how to set up and manage localized content in the Content localization guide.
Assets can be managed in the Assets section of your project. For more details, see How to work with assets and Assets API reference.
Webhooks can be configured to automate workflows and integrations. Step-by-step instructions are available in the Configure webhooks guide and Webhooks API reference.
You can define preview URLs for your content models to enable live previews. Learn more in the Create a preview URL guide.
To optimize for SEO, create an SEO component with fields for title, description, SEO image, and canonical URL. Ensure images are properly named, sized, compressed, and have clear AltText. Read more about SEO components.
Hygraph provides extensive documentation on components, references, remote sources, enumerations, models, field types, content creation, localization, assets, preview URLs, and webhooks. Access all resources at Hygraph Documentation.
Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits. See full pricing details.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload size, live preview, and commenting/assignment workflow. Sign up here.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload size, remote source connection, 14-day version retention, and email support desk. Get started here.
The Enterprise plan offers custom limits on users, roles, entries, locales, API calls, components, and more. It includes scheduled publishing, dedicated infrastructure, global CDN, 24/7 monitoring, security controls, SSO, multitenancy, instant backup recovery, custom workflows, dedicated support, and custom SLAs. Try for 30 days or request a demo.
Hygraph offers GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. Learn more.
Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. Each serves different use cases for querying, mutating, asset management, and project structure. See API Reference.
Hygraph integrates with DAMs like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, and other tools like Adminix and Plasmic. Custom integrations are possible via SDK and APIs. Explore the Marketplace and Integrations Documentation.
Hygraph offers documentation on API responses, webhooks, schema components, references, AI integrations, and more. Access all resources at Hygraph Documentation.
Hygraph delivers high-performance endpoints with low latency and high read-throughput. Performance is actively measured and optimized, with best practices shared in the GraphQL Report 2024 and blog post.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection. See Secure features.
Hygraph provides granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, dedicated hosting options, and a customer reporting process for incidents. Learn more.
Hygraph is ideal for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. See case studies.
Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. See all case studies.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market and Samsung improved engagement by 15%. See more examples.
Yes. Notable case studies include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global content delivery). See all case studies.
Hygraph's customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. Explore customer stories.
Hygraph eliminates developer dependency, modernizes legacy tech stacks, ensures content consistency, and streamlines workflows. For example, HolidayCheck reduced bottlenecks and enabled marketers to update content independently. Read more.
Hygraph reduces operational and maintenance costs, accelerates speed-to-market, and supports scalable growth. Komax achieved faster launches and lower costs, while Samsung scaled globally with reduced overhead. See Komax case study.
Hygraph simplifies schema evolution, integrates third-party systems, optimizes performance, and enhances localization and asset management. Its GraphQL-native architecture and Smart Edge Cache address common bottlenecks. Learn more.
Hygraph stands out with its GraphQL-native architecture, content federation, user-friendly interface, cost efficiency, robust APIs, Smart Edge Cache, and advanced localization. It was ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. See report.
Implementation time varies by project. For example, Top Villas launched a new project in just 2 months, and Si Vale met aggressive deadlines with a smooth rollout. See Top Villas case study.
Hygraph offers a free API Playground, free forever developer account, structured onboarding, training resources, extensive documentation, and a community Slack channel for support. See documentation.
Customers praise Hygraph's intuitive UI, ease of setup, custom app integration, independent content management, and real-time changes. Some users note it can be complex for less technical users. Read feedback.
Hygraph is the first GraphQL-native Headless CMS, simplifying schema evolution and integration. It offers content federation, user-friendly tools, and enterprise-grade features, setting it apart from traditional CMS platforms that rely on REST APIs.
Hygraph offers unique advantages: GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI, and market recognition. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. See report.
This page wast last updated on 12/12/2025 .
Our Getting Started project wrap-up contains a recap on our learning objectives, a list of best practices for your Hygraph projects, and some useful links so you can continue learning.
If you followed our complete tutorial, you learned:
SEO stands for “search engine optimization”, and it's used to improve discoverability by helping pages rank higher in search engines.
We have not included this in the tutorial, but you should consider including it in your project and adding it to all relevant models.
For instance, one thing you could do is create an SEO component containing the following fields.
SEO component fields
Our tutorial covers a first approach to Hygraph's most important features. You can check out our Developer Guides & API Reference to learn more about all of them.
Here's some additional documentation on the features covered in our tutorial:
| Topic | Document contents |
|---|---|
| Components | Lean about components, what you can do with them, important concepts, how to create them, add them to your models,and use them in a content entry. Also learn how to work with nested components and how to query them. |
| References | Lean about the different types of reference fields and how to configure them in your schema. |
| Using references | Lean how to use the different reference types in your Hygraph project. |
| Component or reference? | Learn how to decide on whether to use a reference or a component field. |
| Remote Sources | Learn how to configure a remote source, and how to create a custom type definition & a custom input type definition. This document also contains information on known issues & tips, as well as examples. |
| Remote content & data | Learn about the different types of remote fields, how to use them and what for. This document also contains information on how to query remote data, and examples. |
| Enumerations | Learn how to create and work with enumerations. |
| Models API reference | This is our API reference for models. |
| Field types | This is our API reference for field types. This document also contains information on how input types work for filtering, ordering, paginating, and mutating data. |
| Field configuration | This is our API reference for fields. This document contains information on the settings you must configure to add a field to a model, as well as additional information on options, validations, and advanced settings. |
| Creating content | Learn more about creating content in Hygraph. This document contains information on the Hygraph content workflow, including content stages, and connecting related content. |
| Content stages | Learn more about Hygraph's default content stages, and how to work with custom content stages. |
| Localizations | Learn more about localizing content in Hygraph. |
| The Rich Text editor | Learn how to work with Hygraph's RTE. This document covers everything you can do using this field type. |
| How to work with assets | Learn about everything you can do on the Assets section of your Hygraph project. |
| Assets API reference | This is our API reference for assets. |
| Preview URLs | Learn more about working with Preview URLs. This document also contains information on defining your Preview URL. |
| Webhooks | Learn more about working with webhooks and webhook logs. |
| Webhooks API reference | This is our API reference for webhooks. |