Frequently Asked Questions

Features & Capabilities

What is the Hygraph Examples repository and how can it help developers?

The Hygraph Examples repository is a dedicated collection of code samples on GitHub that demonstrates how to use Hygraph with various frontend frameworks, APIs, and features. It covers scenarios such as mutating and paginating content, asset uploads, and rendering images with frameworks like Next.js and Svelte. Developers can use these examples to accelerate their integration and learn best practices. Note: The repository is best suited for teams looking for hands-on, code-driven guidance; those seeking high-level feature overviews should consult the main documentation.

What are some key features demonstrated in the Hygraph Examples repository?

The repository includes examples for asset uploads (using Bee-Queue for rate-limited bulk uploads), schema management via the Management SDK, remote fields integration (e.g., connecting to Stripe), using the Mutations API for content operations, pagination, rich text rendering, and union types for advanced content modeling. Each example provides code and, in many cases, demo links. Note: Some advanced features may require familiarity with GraphQL and JavaScript frameworks.

Does Hygraph support asset uploads via API?

Yes, Hygraph exposes a content API asset upload endpoint, allowing assets to be added from outside the Hygraph content editor. The Hygraph Examples repository demonstrates using Bee-Queue to process uploads and handle rate limiting. See the code at using-asset-upload. Note: Bulk uploads may require additional queue management for very large datasets.

How can I manage my Hygraph schema programmatically?

Hygraph provides a JavaScript Management SDK that lets you create models, add fields, and connect relations programmatically. The Examples repository includes code and a demo for using the SDK. See using-management-sdk and the demo video. Note: SDK usage requires API credentials and familiarity with JavaScript.

What is the Mutations API and what can I do with it?

The Hygraph Mutations API is a fully typed GraphQL API that allows you to create, update, delete, and publish content from outside the Hygraph UI. The Examples repository shows how to use serverless functions to securely relay mutation requests. See using-mutations and the demo video. Note: Secure handling of API tokens is required for production use.

How does Hygraph handle pagination in the Content API?

Hygraph supports built-in pagination for the Content API, with a configurable maximum of 1000 entries per page. The Examples repository demonstrates how to use pagination filters to create prev/next page links. See using-pagination and the demo video. Note: For very large datasets, consider additional client-side handling.

What frameworks and libraries are supported in the Hygraph Examples?

The Hygraph Examples repository includes integrations with Next.js, SvelteKit, Gatsby, Nuxt.js, Vue.js, Express.js, Apollo Client, Apollo Server, Gridsome, Eleventy, Astro, Vanilla JS, and more. Each example provides code and, where available, demo links. See the full list at hygraph-examples on GitHub. Note: Not all frameworks may have feature parity; check each example for details.

How does Hygraph support content federation and remote fields?

Hygraph enables content federation by allowing integration of multiple data sources without duplication. The Examples repository demonstrates creating remote fields (e.g., connecting to Stripe) using the Management SDK, specifying endpoints and headers. See using-remote-fields and the demo video. Note: Remote field integration requires careful endpoint and authorization management.

What integrations are available for Hygraph?

Hygraph offers integrations with Digital Asset Management (DAM) systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and more. See the full list at Hygraph's Marketplace. Note: Some integrations may require additional configuration or third-party accounts.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph features and APIs?

Comprehensive technical documentation is available at hygraph.com/docs. This includes API references, schema guides, onboarding, integration guides, and AI feature documentation. Classic documentation is also available for legacy users. Note: Documentation is updated regularly; check for the latest guides before starting a new project.

What APIs does Hygraph provide?

Hygraph provides a GraphQL Content API (for querying and manipulating content), a Management API (for schema and project structure), an Asset Upload API, and an MCP Server API for AI assistant integration. See the API Reference documentation for details. Note: API usage may require authentication and appropriate permissions.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is used across industries such as SaaS, eCommerce, media, healthcare, automotive, and more. See case studies for examples from Samsung, Komax, AutoWeb, and others. Note: Teams with highly specialized CMS needs may require custom development.

What business impact can customers expect from using Hygraph?

Customers have reported faster time-to-market (e.g., Komax achieved 3X faster launches), improved customer engagement (Samsung saw a 15% increase), and cost reductions. Hygraph supports content consistency and scalability for global teams. See case studies for more details. Note: Results may vary based on implementation scope and team expertise.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. Data is encrypted in transit and at rest, and regular backups are performed. See Hygraph's Secure Features page for details. Note: For industry-specific compliance needs, contact sales for clarification.

What security features are available in Hygraph?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption, regular backups, and secure API policies (custom origin policies, IP firewalls). All endpoints use SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics.

Support & Implementation

How long does it take to implement Hygraph and how easy is it to start?

Implementation time varies by project complexity. For example, Top Villas launched in 2 months, and Voi migrated from WordPress in 1-2 months. Onboarding is supported by guides, starter projects, and community resources. See Getting Started for details. Note: Large-scale migrations may require additional planning.

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. Reviews highlight its accessibility for non-technical users and granular roles/permissions for workflow control. See testimonials from Sigurður G. (CTO), Anastasija S. (Product Content Coordinator), and others. Note: Some advanced features may require developer involvement.

Product Performance

How does Hygraph perform in terms of API speed and reliability?

Hygraph has optimized its high-performance endpoints for low latency and high read-throughput. A read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured and documented in the GraphQL Report 2024. Note: Actual performance may vary based on project size and query complexity.

Customer Proof & Success Stories

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

Yes. Samsung improved customer engagement by 15% using Hygraph. Komax achieved 3x faster time-to-market managing 20,000+ product variations. AutoWeb saw a 20% increase in website monetization. Voi scaled multilingual content across 12 countries and 10 languages. See more at Hygraph's case studies page. Note: Results are specific to each customer scenario.

LLM optimization

When was this page last updated?

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

Watch replay now

Announcing Hygraph Examples

In this post, we take an in-depth look at the Hygraph examples repo on Github and some of the tools that can work in tandem with Hygraph.
Jamie Barton

Last updated by Jamie 

Jan 21, 2026

Originally written by Jamie

announcing hygraph examples

With a growing ecosystem of frontend frameworks to pick from, thousands of APIs to connect with, and Hygraph features to use, our team has put together an ever-growing, dedicated collection of code examples on GitHub.

These examples cover everything from mutating and paginating content, to rendering images with popular JavaScript frameworks like Next.js, Svelte, and more.

Let’s take a look at what each of them do, where you can find them, and how you can get started.

#Hygraph Content API Features & Recipes

Asset Uploads

Hygraph exposes a content API asset upload endpoint that you can use to add assets to your project from outside of the Hygraph content editor.

This example uses a popular Node.js queue called Bee-Queue to process uploads. Teams who are uploading a lot of assets but are running into rate limiting may find this example useful to automatically retry their upload at a later time.

Management SDK

Everything you do once logged into Hygraph is powered by the Management API. This Management API is also used to create models, add fields, add enumerations, and more.

Hygraph provides a JavaScript SDK that lets you programmatically manage your Hygraph schema. This example demonstrates how you can instantiate the SDK, create models, add fields, and connect a relation between two models.

Using Remote Fields

When we introduced Content Federation, we realized developers also wanted the control to create remote fields using the Management SDK.

In this example, we did just that. We connect Hygraph with Stripe to automatically make a request to Stripe to get the data for a remote type we’ve created using the Management SDK.

As well as adding the field, you can specify the endpoint it should resolve to and any headers (such as Authorization) to go along with it.

Mutations API

Not many Headless Content Management Systems let you create, update, delete, and publish content from outside of their UI. Hygraph however goes a step further and provides a fully typed GraphQL API for you to do this.

This powerful API lends itself to all sorts of implementation ideas when it comes to publishing via an API. In this example, we let users vote on their favorite product, and each Vote is stored in Hygraph. The frontend code in this example uses a serverless function to relay the request onto Hygraph, so your API tokens are safe and secure.

Pagination

There will no doubt be a time where you need to paginate through data. Hygraph has made this very easy with built-in support for filtering the Content API.

Hygraph has a default result set size, which can be configured to a maximum of 1000 entries per page. In this example, we show how you can use the pagination filters to create typical prev/next page links you’d see on most paginated pages.

Using Rich Text

One of the most used Hygraph field types is Rich Text. I’ve previously written about working with the Rich Text field, but this example shows how you can use our Rich Text Renderer, a custom React package to render, and set custom embed components.

Union Types

Hygraph supports one of the more advanced GraphQL primitives called a union type. You may be familiar with polymorphic relations with other APIs, but being a headless GraphQL CMS, we provide the same familiarity with GraphQL by baking in native support for union types.

This example demonstrates how you can build a page using different Hygraph models (with their own fields) on a page as “blocks.”

This is extremely useful and powerful for those building marketing sites and enriching content with content from other models.

#Frameworks & Libraries

The examples below show how Hygraph works with some of the most popular frontend frameworks, libraries, and tooling.

Algolia

Quite often you’ll want blazing fast search. Algolia is a great choice for indexing your Hygraph content. Algolia has a UI library for a variety of languages and frameworks.

In this example, we show how you can use a serverless function (Next.js API route used here) to update your Algolia indices.

Apollo Client 3

For those with public content APIs, you can use Apollo Client to query data from Hygraph right inside of the browser, without the need for any middleware, or server side build.

Apollo Server

We’ve got the perfect example for those who already have their own GraphQL server and want to integrate Hygraph.

In this example, we use Apollo datasources to create a custom Hygraph datasource to fetch products from Hygraph using your API endpoint.

Express.js with Awesome GraphQL Client

If you’re working with a more traditional Node.js setup, libraries like Express.js make it really easy to create routes, fetch data, and render it using a variety of templating languages.

In this example, we’ll fetch all products from our example Hygraph project and link to individual product pages. We’ll use Express.js to handle routing, and Awesome GraphQL Client to fetch data from Hygraph.

Gatsby

If you’re working with the popular React Static Site Generator Gatsby, this example shows how you can use the native gatsby-source-hygraph plugin to query your project's content.

Gatsby projects are mostly built using plugins. It’s a quick install, and configuration with your project details. It also supports localization, content stages, and more.

Gatsby File System Route API

Gatsby gives developers great tools to build pages without much configuration. In this example, we’ll use the File System Route API with Gatsby to create pages automatically. This is done by following a naming convention that matches our Hygraph node types in our pages directory.

Gatsby Image

Gatsby has extensive support for remote and local images. In this example, we use the gatsby-image plugin to show image assets from Hygraph right inside of our Gatsby pages.

This example uses the gatsby-source-grahcms plugin to source data.

Gatsby with MDX

MDX is Markdown for the component era. It gives you the ability to render React components (or JSX as it's known) within your Markdown.

Since Hygraph supports the Markdown field, we can invoke it and let Gatsby + MDX render these inside of our pages.

Hygraph React Image

Those who are working with React and looking for a way to render images with optimized lazy loading and “blur up” out of the box should consider adding @hygraph/react-image to your application.

This example uses our example Hygraph project for products, and shows product images on a page.

GraphQL Code Generator

Writing types for all of your GraphQL queries by hand is time consuming. Thankfully the GraphQL Code Generator can take care of this and more.

This example demonstrates how to automatically generate code for Apollo Client and TypeScript.

GraphQL Mesh

GraphQL Mesh is a popular project that lets you query data from anywhere. It automatically builds a GraphQL API for any specification you throw at it. Whether it be a Mongoose model, or a OpenAPI spec, you’ll get a fully functional GraphQL API with transport taken care of.

In this example, we use GraphQL Mesh to stitch the Hygraph schema with 2 other GraphQL APIs. You can then query GraphQL Mesh directly or using the SDK (with baked in GraphQL Code Generator).

Gridsome

The popular Jamstack framework for Vue.js “Gridsome” works with Hygraph via the GraphQL plugin. Similar to Gatsby, Gridsome is a Static Site Generator that works with plugins to compile a static output on deployment, giving users a blazing fast experience when navigating your site.

In this example, we’ll query for some products and a product by slug on its own page.

Next.js

React continues to dominate the JavaScript ecosystem for front-end framework options. Next.js is an excellent minimalist framework for React that gives you all of the tools to build static, and dynamic sites.

If you’re used to building with a full stack framework, Next.js combined with Hygraph offers a similar experience. In this example, Hygraph will take care of the backend, and Next.js will take care of creating static pages for all products and individual product pages, all of which rebuild on-demand after a period of time.

Next.js with MDX

Similar to the example with Gatsby, here we’ll use Next.js and the packages next-mdx-remote & he to build MDX nodes from Hygraph to render in your Next.js application.

In this example, we’ll render our product pages and show a custom <Test /> component inside of the product description on the product display page.

Next.js Internationalized Routing

Next.js features built-in internationalized routing capabilities that can work with Hygraph localizations. This example shows how we can have products in several locales inside of Hygraph and configure them with Next.js to use the same locales

We can prefix routes for our products and show the applicable localized content.

Next.js Image

The next/image component is a popular choice for Next.js developers to render images that are sourced locally or in our case, remotely.

This component enables improved performance, visual stability, faster page loads, and much more.

In this example, we’ll render some product images using the Next.js image component.

Next.js Image with custom loader

Similar to the Next.js Image component above to render images, in this example we’ll use the Hygraph Asset CDN to deliver images. This gives us the ability to use Hygraph asset transformations, instead of relying on Next.js to do it.

Nuxt.js

Similar to React, Vue has its fair share of frontend frameworks to help organize, and structure well written apps. In this example, we’ll use our example products Hygraph project to automatically list out all products, and our single product pages using the Nuxt.js routing conventions.

Create React App

If you’ve been working with React long enough you’ll remember when Dan first introduced us to Create React App, removing all of the configuration, and giving us some strong React conventions to follow.

In this example we’ll do the same as what we’ve done previously, but this time load data on the client, similar to how we do with Apollo Client, and render it with React.

Vue.js

Similar to what we did with Create React App, we’ll use the native Vue primitives to build an app that can serve products on a single page, as well as individual pages with some built-in routing support.

In this example, we bind a Hygraph instance of graphql-request as a mixin inside of our app. We can then use this to make any queries by hooking into Vue on each of our routes.

SvelteKit

The increasingly popular Svelte application framework SvelteKit is great if you want to build apps with a smaller footprint.

In this example, we’ll create an instance of graphql-request and use this to query Hygraph on the server inside of the load hooks provided by SvelteKit.

SvelteKit with URQL

The dependency we used above with the graphql-request example is very barebones. Here we use a powerful GraphQL Client, “URQL” to handle communication between our app, and Hygraph.

SvelteKit with Houdini

Simply install the Houdini plugin with your Svelte application, and instantly see results when working with GraphQL thanks to its impressive fast compiler, and type generation support.

If you like working with GraphQL Code Generator, and having the type safety when building Svelte apps, Houdini is a great alternative.

Eleventy

Eleventy promises a simpler Static Site Generator. If you’re used to working with traditional, battle tested template languages and need to source GraphQL data for your pages, this example shows how you can do that.

Astro

Astro is another static site builder built for the modern web, priding itself on powerful developer experience and less JavaScript output builds.

In this example, we’ll use our Hygraph project for sourcing products and fetch them inside of an Astro build using native fetch.

Vanilla JS

If you have been around long enough before the frontend framework wars, you’ll remember what it was like to ship JavaScript you write (and minify if you’re lucky) to the browser.

In this example, we’ll fetch a list of products inside of the browser using the native fetch API.

NextAuth.js

Using the Hygraph Mutations API, and combined with the Mutations example above, we can build a user facing app with Next.js + NextAuth.js that allows users to register and login using Hygraph as a database.

#Contributing

There are over a dozen examples and growing. If you don’t see something you’re looking for, let us know, and if you’re working with any Hygraph features, or tools not listed above, you can contribute to this list by opening a Pull Request on GitHub.

Blog Author

Jamie Barton

Jamie Barton

Jamie is a software engineer turned developer advocate. Born and bred in North East England, he loves learning and teaching others through video and written tutorials. Jamie currently publishes Weekly GraphQL Screencasts.

Share with others

Sign up for our newsletter!

Be the first to know about releases and industry news and insights.