Frequently Asked Questions

Getting Started & Implementation

How do I start building an eCommerce project with Hygraph?

To start building an eCommerce project with Hygraph, you can follow the full tutorial available at Hygraph Tutorial Overview. You have two options: build from scratch (where you construct the schema, content, API configuration, and frontend connection step by step) or explore a complete project (where all models, components, and content are pre-built, allowing you to focus on API queries and frontend integration). Note: For lessons involving remote sources or advanced features, a Growth plan or higher, or a 30-day trial, is required. Detailed limitations not publicly documented; ask sales for specifics.

What are the technical requirements for completing the Hygraph eCommerce tutorial?

Technical requirements include a Hygraph account, basic GraphQL knowledge, understanding of content modeling, a code editor (such as VS Code), the current version of Node.js, and a Netlify or Vercel account for frontend deployment. For advanced lessons (5.1–5.3 and remote sources), you need a Growth plan or higher, or a 30-day trial. Note: API tokens, environment variable configuration, connected frontend, and webhooks are not included in the cloned project and must be set up during the tutorial. Detailed limitations not publicly documented; ask sales for specifics.

How long does it take to implement Hygraph for a typical project?

Implementation timelines depend on project complexity. Simple use cases can be started within a few days, while more complex implementations may take longer. Hygraph offers structured onboarding, pre-configured starter projects, and extensive documentation to accelerate setup. For more details, see Getting Started guide. Note: Implementation speed may vary based on team experience and project scope. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What features does Hygraph offer for eCommerce projects?

Hygraph provides a range of features for eCommerce projects, including customizable content models (Product, Product category, Blog post, Seller information, Landing page, Navigation), reusable components (Product variant, Related Products, CTAs, Navigation links), enumerations for product attributes, remote sources for integrating external APIs, and localization for multi-language content. The platform supports both REST and GraphQL APIs, enabling flexible integration with modern frontends like Next.js. Note: API tokens, environment variable configuration, and webhooks must be set up separately. Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph support API integration for content delivery?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. This allows developers to integrate Hygraph with any frontend or application. For more details, see API documentation. Note: API tokens and permissions must be configured for secure access. Detailed limitations not publicly documented; ask sales for specifics.

What integrations are available with Hygraph?

Hygraph offers integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. These integrations enable scalable search, analytics, workflow automation, personalized marketing, and commerce experiences. For a full list, visit Marketplace Apps page. Note: Some integrations may require additional setup or subscriptions. Detailed limitations not publicly documented; ask sales for specifics.

What are Hygraph's performance capabilities?

Hygraph delivers high performance through a global CDN, region-based hosting, advanced caching (Smart Edge Cache), and a GraphQL-native architecture. It supports high-traffic scenarios, as demonstrated by Gamescom (3.5 million simultaneous sessions, 60 million API operations in three days) and Telenor (under 100ms latency on millions of API calls). Note: Performance may vary based on region and traffic volume. Detailed limitations not publicly documented; ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and complies with GDPR and CCPA regulations. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. Customers can select data centers in preferred regions for compliance. For more details, visit security features page. Note: Some compliance requirements may require additional configuration. Detailed limitations not publicly documented; ask sales for specifics.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is suited for marketing and content teams, product managers, developers, and enterprise IT teams. It addresses needs in industries such as technology, consumer goods, telecommunications, media, retail, e-commerce, travel, scientific publishing, government, sports, and events. Case studies include Samsung (15% improved engagement), Komax (3x faster time-to-market), Gamescom (millions of sessions), and Dr. Oetker (content for 40 countries). Note: Teams requiring highly specialized workflows may need custom integrations. Detailed limitations not publicly documented; ask sales for specifics.

What business impact can customers expect from using Hygraph?

Customers report up to 50% reduction in maintenance costs, 3x faster time-to-market (Komax), improved monetization (up to 20% higher website monetization), and enhanced customer engagement (Samsung, 15% improvement). Hygraph enables scalable operations, global content consistency, and personalized experiences. Note: Actual impact may vary based on implementation and industry. Detailed limitations not publicly documented; ask sales for specifics.

Pain Points & Solutions

What problems does Hygraph solve for its customers?

Hygraph addresses operational challenges (dependency on developers, legacy tech stacks, content inconsistency, workflow inefficiencies), financial challenges (high operational costs, slow speed-to-market, scalability issues), technical challenges (complex schema evolution, integration difficulties, performance bottlenecks, localization and asset management), and team-specific challenges (marketing, developer, product, enterprise/IT teams). Note: Some highly specialized requirements may require custom solutions. Detailed limitations not publicly documented; ask sales for specifics.

Product Information & Documentation

Where can I find technical documentation and guides for Hygraph?

Comprehensive technical documentation and developer guides are available at Hygraph Docs. Resources include getting started guides, advanced tutorials, onboarding overviews, and community support via Slack (slack.hygraph.com). Note: Some advanced features may require a paid plan. Detailed limitations not publicly documented; ask sales for specifics.

Customer Proof & Case Studies

Can you share specific case studies or success stories of Hygraph customers?

Yes. Samsung improved customer engagement by 15% using Hygraph. Komax achieved a 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 from a single platform. Telenor achieved under 100ms latency on millions of API calls. For more, visit Hygraph Case Studies. Note: Results may vary based on implementation. Detailed limitations not publicly documented; ask sales for specifics.

Industries & Customer Base

What industries are represented in Hygraph's customer case studies?

Industries include technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government and public sector (Statistics Finland), sports and events (DTM), and retail/e-commerce (Stobag). Note: Some industries may require custom workflows or integrations. Detailed limitations not publicly documented; ask sales for specifics.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#Full Tutorial - Build Your First eCommerce Project

This tutorial takes you through a complete Hygraph project: an e-commerce store selling wearables and home goods. By the end, you will have a working schema, real content, a queryable API, and a connected Next.js storefront.

Getting started project previewGetting started project preview

Every decision in this tutorial is one you will face on a real project. The schema choices you make in lessons 1 through 5 determine what you can query in lesson 7 and what your frontend renders in lesson 8.

#Choose your path

Your starting point is a cloned Hygraph project. You can choose your own path through the tutorial.

Option 1: Build from scratch

This clone includes navigation structure and image assets. You will build the schema, content, API configuration, and frontend connection yourself, step by step.

Choose this path if you want to understand how every part of a Hygraph project is constructed and why.

Requirements

Select Option 1

Option 2: Explore a complete project

This clone includes the complete Hygraph project: all models, components, enumerations, content entries, and localized content already built. You will skip straight to querying and frontend connection.

Choose this path if you want to practice API queries, mutations, and frontend integration without building the schema yourself.

Requirements

Select Option 2

#Clone the project

The cloning process is the same for both options.

Clone project screenClone project screen

The project already has a name, but you can give it a new name. You can also optionally add a description, select a region, and click Clone now. Cloning takes a couple of minutes. When it finishes, you land on your project homepage.

#What's already in your project

Your cloned project is fully built. Here is what it contains.

Schema

TypeWhat's included
ModelsProduct, Product category, Blog post, Seller information, Landing page, Navigation
ComponentsRelated Products, Product variant, Clothing, Shoes, Accessories, Decor, Button, Call to Action, Product Grid, Link
EnumerationsClothes size, Shoes size, Wearable items color, Decor items color
Remote sourceHyDemoAPI, a Hygraph-maintained REST API used to fetch product reviews
Remote fieldsReviews field on the Product model; Reviews top-level field on the Query model

Content

TypeWhat's included
Products9 published entries with images, variants, related products, and category assignments
Product categories7 published entries
Landing pagesHomepage and Summer Campaign, both with localized Spanish content
NavigationMain navigation with category and campaign links
Seller information1 published entry
AssetsAll product images with alt text and captions

Your path through the tutorial

  1. Query your content in the API Playground.
  2. Run mutations.
  3. Set up the Next.js frontend starter.
  4. Connect Hygraph to your local frontend.
  5. Configure a preview URL for draft content.
  6. Set up a webhook to trigger frontend deploys on publish.

#Lesson overview

#Lesson 1 — Content models

#LessonWhat you will be able to do
1.1Design your content modelsSketch your model structure and understand how fields, models, and schema relate to each other
1.2Build your content modelsCreate your base models and fields in the Hygraph schema editor

#Lesson 2 — References

#LessonWhat you will be able to do
2.1Configure reference fieldsConnect models to each other using one-to-one, one-to-many, and many-to-many references

#Lesson 3 — Enumerations

#LessonWhat you will be able to do
3.1Configure enumerationsCreate predefined value sets that appear as dropdowns in the content editor

#Lesson 4 — Components

#LessonWhat you will be able to do
4.1Build componentsCreate reusable field sets for product variants, CTAs, related products, and navigation links
4.2Add components to your modelsAttach your components to models as basic and modular component fields

#Lesson 5 — Remote Sources

#LessonWhat you will be able to do
5.1Add a Remote SourceConnect an external REST API to your Hygraph schema
5.2Remote FieldsFetch remote data within the context of a specific model entry
5.3Top-level Remote FieldsFetch remote data outside the context of any model and serve it alongside Hygraph content in a single API call

#Lesson 6 — The Content Editor

#LessonWhat you will be able to do
6.1Create contentCreate and publish products, categories, landing pages, and navigation entries
6.2Localize contentAdd a locale and write localized content for selected fields
6.3Understand content stagesLearn how DRAFT and PUBLISHED content stages affect what the Content API returns and what the frontend displays

#Lesson 7 — The API Playground

#LessonWhat you will be able to do
7.1Exercises: QueriesWrite queries for models, references, components, and remote fields
7.2Exercises: MutationsCreate, update, publish, and delete content entries programmatically

#Lesson 8 — Frontend Connection

#LessonWhat you will be able to do
8.1Set up the frontend starterClone and configure the Next.js e-commerce starter locally
8.2Connect your storefrontConfigure API access permissions, create a PAT, and connect Hygraph to your local frontend
8.3Preview URLAdd a preview button to the content editor sidebar to preview draft content before publishing

#Lesson 9 — Webhooks

#LessonWhat you will be able to do
9.1Configure webhooksSet up a webhook that triggers a frontend rebuild whenever content is published

#What's next

Build from scratch OR Explore a complete project