Frequently Asked Questions

Ordering & Content API Usage

How can I order results when fetching multiple entries in Hygraph's Content API?

You can use the orderBy argument in Hygraph's Content API to define the order of returned records. You can order results by any system field or non-relational custom field defined in your model, in either ascending (_ASC) or descending (_DESC) order. For example, orderBy: createdAt_ASC will order results by the createdAt field in ascending order. Note: Only one inputType can be used with orderBy at a time. Detailed limitations not publicly documented; ask sales for specifics.

What types of fields can I use with the orderBy argument?

You can use orderBy with all system fields and any non-relational custom field defined in your model. This allows you to sort results based on fields such as createdAt, updatedAt, or custom fields you have added. Note: Relational fields are not supported for direct ordering. Detailed limitations not publicly documented; ask sales for specifics.

Can I use multiple orderBy input types in a single query?

No, you can only use one inputType with orderBy to order results in a single query. If you need more complex ordering, you may need to adjust your query structure or handle sorting in your application logic. Note: This limitation may affect advanced sorting scenarios. Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph support nested ordering in queries?

Yes, you can use orderBy with two-way references for nested ordering. For example, you can order related entries within a parent entry. However, one-way references and union-type relations are not supported for nested ordering. Note: If your model relies on one-way references or unions, nested ordering will not be available. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native Headless CMS, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and integrations with platforms like AWS S3, Cloudinary, Netlify, Vercel, and BigCommerce. It also provides user-friendly tools for non-technical users and supports high-performance endpoints for low-latency content delivery. Note: Some advanced features may require specific plans or technical setup. Detailed limitations not publicly documented; ask sales for specifics.

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and more. For a full list, visit the Hygraph Marketplace. Note: Integration availability may depend on your plan or technical requirements. Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph provide APIs for content management?

Yes, Hygraph provides several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure AI assistant communication. For details, see the API Reference documentation. Note: API usage may require authentication and specific permissions. Detailed limitations not publicly documented; ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to security and privacy. Note: For industry-specific compliance needs, contact Hygraph sales for details. Source: Hygraph Secure Features.

What security features are available in Hygraph?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin policies, IP firewalls). All endpoints have SSL certificates. Note: Some features may require enterprise plans. Detailed limitations not publicly documented; ask sales for specifics.

Performance & Implementation

How does Hygraph ensure high performance for content delivery?

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint provides 3-5x latency improvement. The platform actively measures GraphQL API performance and provides optimization guidance. For details, see the performance improvements blog and GraphQL Report 2024. Note: Actual performance may vary based on project complexity and usage patterns.

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 Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph provides structured onboarding, starter projects, and extensive documentation to accelerate adoption. Note: Complex migrations or integrations may require additional time. Source: Top Villas Case Study, Voi Case Study.

Use Cases & Customer Success

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 in industries such as SaaS, eCommerce, media, healthcare, automotive, fintech, education, and more. Note: Teams with highly specialized legacy systems may require additional integration work. Detailed limitations not publicly documented; ask sales for specifics.

What business impact have customers seen with Hygraph?

Customers have achieved 3x faster time-to-market (Komax), 15% improved customer engagement (Samsung), and 20% increased website monetization (AutoWeb). Voi scaled multilingual content across 12 countries and 10 languages. For more, see Hygraph case studies. Note: Results may vary based on implementation and use case.

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

Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. For example, Sigurður G. (CTO) noted the UI is intuitive for non-technical users, and Charissa K. (Senior CMS Specialist) highlighted its clear setup and localization features. Note: Some advanced features may require technical expertise. Source: Hygraph Reviews.

Pain Points & Problems Solved

What problems does Hygraph solve for its users?

Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some pain points may require custom solutions or integrations. Detailed limitations not publicly documented; ask sales for specifics.

Technical Documentation & Support

Where can I find technical documentation for Hygraph?

Technical documentation is available at hygraph.com/docs, including API references, schema guides, onboarding, integration tutorials, and AI feature documentation. Classic Docs are also available for legacy users. Note: Some advanced topics may require direct support. 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 .

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#Ordering

When fetching multiple entries you can use the orderBy argument to define the order of the returned records.

You can order results by all System Fields, and any non-relational custom field you define in your model, either ascending, or descending.

#Order by types

Input TypeDescription
[fieldName]_ASCOrder results by fieldName ascending.
[fieldName]_DESCOrder results by fieldName descending.

#Nested ordering

You can use the orderBy with two-way references.

One-way references and union-type relations are not supported.

For example, let's imagine our post has a authors relation. The same orderBy rules apply.

{
  posts {
    id
    createdAt
    relatedPosts(orderBy: createdAt_DESC) {
      id
      createdAt
    }
  }
}