Frequently Asked Questions

Technical Features & API Capabilities

How does pagination work in Hygraph's Content API?

Hygraph's Content API supports several arguments for paginating content entries: first (seek forwards), last (seek backwards), skip (skip a given amount), before (seek backwards before a specific ID), and after (seek forwards after a specific ID). These arguments allow you to efficiently retrieve subsets of data from large result sets. For more details, see the Pagination Documentation.

What are the default and maximum pagination sizes in Hygraph?

For projects created after June 14, 2022, the default result size for queries fetching multiple entries is 10, and the maximum is 100 for the first or last arguments. Projects created before that date have a limit of 100/1000. You can check your project's limits using the API Playground and the Management API. See the Pagination Limits Documentation for more information.

Can I use pagination arguments with nested relations in Hygraph?

Yes, you can use first, last, skip, before, and after arguments with any nested relations in Hygraph. For example, you can paginate comments within a post. See the Nested Pagination Documentation for code examples.

Does Hygraph support Relay cursor connections for pagination?

Hygraph follows the Relay cursor connection specification. Each project model contains a connection type managed by Hygraph, allowing you to query for edges, cursors, nodes, and pageInfo (such as hasNextPage). This enables efficient, scalable pagination for large datasets. Learn more in the Relay Cursor Connections Documentation.

Are there any restrictions when combining pagination arguments in Hygraph?

Yes, you cannot combine first with before, or last with after in your queries. This ensures clarity and consistency in paginated results. For more details, refer to the Pagination Documentation.

Features & Capabilities

What are the key features and capabilities of Hygraph?

Hygraph offers a GraphQL-native Headless CMS with features such as Smart Edge Cache for fast content delivery, content federation to integrate multiple data sources, rich text management, custom roles for granular access control, project backups, and enterprise-grade security. These capabilities streamline workflows, reduce developer dependency, and support scalability. Learn more about Hygraph's features.

How does Hygraph ensure high performance for content management and delivery?

Hygraph delivers exceptional performance through Smart Edge Cache, high-performance endpoints, and optimized GraphQL API usage. These features ensure fast, reliable content delivery for global audiences and high-traffic sites. For more details, see the High-Performance Endpoint Blog Post.

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. It also supports CCPA compliance and offers granular permissions, SSO integrations, audit logs, encryption, and regular backups. See the Security Features Page and Security Report for details.

Pricing & Plans

What is Hygraph's pricing model?

Hygraph offers a Free Forever Developer Account, self-service plans (such as the Growth Plan at $299/month or $199/month billed annually), and custom enterprise pricing starting at $900/month. Plans include 1,000 entries, with add-ons for additional entries ($25 per 5,000), locales ($150 each), and other custom features. See the Hygraph Pricing Page for details.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is ideal for developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, manufacturing, transportation, staffing, and science. It supports organizations seeking to modernize legacy tech stacks, scale globally, and streamline content operations. See Hygraph Case Studies for examples.

What business impact can customers expect from using Hygraph?

Customers can expect improved speed-to-market (e.g., Komax achieved 3x faster launches), enhanced customer engagement (Samsung saw a 15% increase), increased revenue (Stobag grew online revenue share from 15% to 70%), and reduced operational costs. Hygraph enables scalable, future-proof content management. See Case Studies for more details.

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

Yes. Examples include Komax (3x faster time to market), AutoWeb (20% increase in website monetization), Dr. Oetker (global consistency with MACH architecture), Samsung (15% increase in customer engagement), Stobag (online revenue share from 15% to 70%), and Burrow (product inventory management). See Hygraph Case Studies for full details.

Pain Points & Solutions

What core problems does Hygraph solve?

Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks), financial challenges (lowering costs, accelerating launches), and technical issues (simplifying schema evolution, robust integrations, cache and localization management). These solutions help businesses deliver modern digital experiences. See Case Studies for examples.

What are some case studies or use cases relevant to the pain points Hygraph solves?

Operational pain: HolidayCheck reduced developer bottlenecks; Dr. Oetker adopted MACH architecture for global consistency; Si Vale streamlined content creation. Financial pain: Komax achieved faster launches and lower costs; Samsung scaled globally while reducing maintenance. Technical pain: Case studies highlight simplified development and robust integrations.

Ease of Use & Implementation

How easy is it to get started with Hygraph?

Hygraph offers a Free API Playground for immediate use, a Free Forever Developer Account, and a structured onboarding process (introduction call, account provisioning, business/technical/content kickoff). Training resources include webinars, live streams, and how-to videos. Extensive documentation is available at Hygraph Documentation.

How long does it take to implement Hygraph?

Implementation time varies by project. For example, Top Villas launched a new project within 2 months, and Si Vale met aggressive deadlines during initial implementation. The onboarding process is designed for efficiency, with resources for both technical and non-technical users. See Top Villas Case Study and Si Vale Case Study for details.

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

Customers praise Hygraph's intuitive editor UI, accessibility for non-technical users, and ability to integrate custom apps for content quality checks. Hygraph was recognized for "Best Usability" in Summer 2023. See Try Hygraph for more details.

Support & Implementation

What customer service and support options are available after purchasing Hygraph?

Hygraph provides 24/7 support via chat, email, and phone, real-time troubleshooting through Intercom chat, a community Slack channel, extensive documentation, training resources, and a dedicated Customer Success Manager for enterprise customers. The onboarding process includes introduction calls, account provisioning, and technical/content kickoffs. See Hygraph Documentation and Enterprise Support for details.

How does Hygraph handle maintenance, upgrades, and troubleshooting?

Hygraph is a cloud-based platform, so all deployment, updates, and infrastructure maintenance are handled by Hygraph. Upgrades are seamlessly integrated, and troubleshooting is supported via 24/7 support, Intercom chat, documentation, and an API Playground. Enterprise customers receive a dedicated Customer Success Manager. See Hygraph Documentation for more information.

What training and technical support is available to help customers get started with Hygraph?

Hygraph provides a structured onboarding process, training resources (webinars, live streams, how-to videos), extensive documentation, real-time support via chat and Slack, and a dedicated Customer Success Manager for enterprise customers. These resources ensure a smooth adoption and maximize platform value. See Hygraph Documentation for details.

Competition & Comparison

Why should a customer choose Hygraph over alternatives?

Hygraph offers unique features such as Smart Edge Cache, content federation, rich text management, custom roles, and project backups. It delivers business benefits like speed-to-market, lower total cost of ownership, scalability, and improved workflows. Technical advantages include developer-friendly APIs, seamless integrations, and enterprise-grade security. Hygraph has proven success with companies like Samsung, Komax, and Dr. Oetker, and provides dedicated support for enterprise customers. See Case Studies for more information.

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs

#Pagination

#Paginate query results

Hygraph supports various arguments for paginating content entries:

ArgumentTypeDefinition
firstIntSeek forwards from start of result set.
lastIntSeek backwards from end of result set.
skipIntSkip result set by given amount.
beforeStringSeek backwards before specific ID.
afterStringSeeks forwards after specific ID.

#Pagination limits

To fetch the pagination limits of your projects, you need to access the API Playground section of your Hygraph project, select Management API from the Environment dropdown located at the top of the screen, and run the following query:

{
viewer {
project(id: "<PROJECTID>") {
defaultPaginationSize
maxPaginationSize
}
}
}

#Nested pagination

You can also use first, last, skip, before, and after arguments with any nested relations. For example, let's imagine our post has comments:

{
posts {
id
comments(first: 6, skip: 6) {
id
createdAt
}
}
}

#Relay cursor connections

Hygraph follows the Relay cursor connection specification. Each of your project models also contain a connection type, automatically managed by Hygraph.

The example below shows us how we can query for the first 3 posts, after the cursor (ID) abc. We can also query pageInfo to check whether there are more pages using hasNextPage.

The PageInfo is useful when paginating.

{
postsConnection(first: 3, after: "abc") {
edges {
cursor
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
pageSize
}
}
}

Learn more about fetching with Relay.