Frequently Asked Questions

Content Search & Filtering

How does content search work in Hygraph?

Hygraph's content search allows users to quickly find content pieces by entering keywords. The search function matches keywords in string fields such as Author, Title, or Content Keywords. The search is not case sensitive, so searching for "TEST" or "test" will return the same results. Note: Full text search is not supported, and searching within Rich Text or JSON fields is currently unavailable. For more details, see the Searching for Content documentation.

Which field types can be searched or filtered in Hygraph?

You can search and filter by String (Single-Line, Multi-Line, Slug, Markdown), Float, Integer, Enumeration, and Boolean fields. Multi-value versions of string fields are also supported. However, you cannot search or filter by multi-value fields (other than string), colors, or coordinates. Rich Text and JSON fields are not searchable. Note: For large content projects, specifying a field type can improve search performance. Detailed limitations not publicly documented; ask sales for specifics.

Can I perform full text search in Hygraph?

No, Hygraph does not currently support full text search. Searching within Rich Text or JSON fields is also not supported. If you require full text search, you may need to consider integrating with an external search service. Note: This may be a limitation for teams needing advanced search capabilities.

How are search results ordered in Hygraph?

By default, search results are ordered by the "created at" timestamp, starting with the oldest item. You can change the order by sorting on the "created at" field. Note: Custom sorting beyond "created at" may require additional configuration or queries.

Can I save my search or filter settings in Hygraph?

Yes, editors can save their search and filter settings as a content view for future use. This helps streamline workflows for recurring queries. Note: The ability to share saved views with other users is not documented; check with support for collaboration features.

Where can I find more resources on filtering content in Hygraph?

You can learn more about filtering content by entry, relations, and content stage in the Using Filters documentation. For technical details, refer to the API Reference documentation. Note: Some advanced filtering scenarios may require custom queries or API usage.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and integrations with platforms like DAM systems, hosting providers, and commerce solutions. It also provides user-friendly tools for non-technical users and supports scalability for high-growth businesses. Note: Some advanced features may require technical setup or higher-tier plans. Learn more.

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management (DAM) systems such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot; hosting and deployment platforms like Netlify and Vercel; Product Information Management (PIM) with Akeneo; commerce solutions like BigCommerce; and translation/localization tools such as EasyTranslate. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or third-party accounts.

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 communication with AI assistants. For details, see the API Reference documentation. Note: API usage may require authentication and appropriate permissions.

How does Hygraph ensure high performance for content delivery?

Hygraph optimizes for low latency and high read-throughput with high-performance endpoints and a read-only cache endpoint that delivers 3-5x latency improvement. The platform actively measures GraphQL API performance and provides practical optimization advice. For more, see the High-Performance Endpoint blog post and GraphQL Report 2024. Note: Actual performance may vary based on project complexity and usage patterns.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data privacy. For more details, visit the Secure Features page. Note: For industry-specific compliance needs, contact sales for details.

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. For more, see the Secure Features page. Note: Some features may be limited to enterprise plans.

Implementation & Onboarding

How long does it take to implement Hygraph?

Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Si Vale met aggressive deadlines in their initial phase. Note: Large-scale or highly customized projects may require more time. See case studies for details.

What resources are available to help new users get started with Hygraph?

Hygraph offers a structured onboarding process, comprehensive documentation, starter projects, webinars, live streams, and community support via Slack. New users can sign up for a free account and access guides in the Getting Started section. Note: Some advanced training may require direct engagement with the Hygraph team.

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals. It is suitable for enterprises and high-growth companies in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. For a full list of industries, see the case studies page. Note: Teams with highly specialized CMS needs should review technical documentation for fit.

What business impact have customers seen with Hygraph?

Customers have reported faster time-to-market (Komax achieved 3x faster launches), improved customer engagement (Samsung saw a 15% increase), and cost reduction (AutoWeb increased website monetization by 20%). Voi scaled multilingual content across 12 countries and 10 languages. For more, see customer 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 for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Charissa K. (Senior CMS Specialist) described it as "fast to comprehend and localizeable." Note: Some advanced features may require technical expertise. Read more reviews.

Technical Documentation & Support

Where can I find technical documentation for Hygraph?

Technical documentation is available for APIs, schema components, references, integrations, and AI features. Key resources include the API Reference, Components Documentation, and AI Agents Documentation. For onboarding, see the Getting Started guides. Note: Documentation for Hygraph Classic is also available for legacy users.

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

#Searching for content

The most basic feature for navigating the content is using the search.

The Search function enables you to quickly find any pieces that match the keyword entered. Users are able to search for any keyword (string fields) used in the content piece, such as Author, Title or Content Keywords.

Search for contentSearch for content

By submitting a search term, a fresh request is generated including a where argument.

Specifying a field type to narrow down the search can be done by typing the first letters or selecting it accordingly in the filter bar. The search itself is not case sensitive, meaning TEST or test will return the same results.

The default order of the items is by "created at", starting with the oldest item. Sorting by "created at" will allow you to change the order.

{
posts(where: { _search: "Test" }) {
id
}
}

In addition, it is possible to specify the following field types as part of the search request:

  • String (Single-Line, Multi-Line, Slug, Markdown)
    • also multi-value versions of these
  • Float
  • Integer

An editor can verify the schema of the content model to understand which field types are used. However, the usable field types will be shown in the search bar as part of the filters and depend on the schema modeling. The advantage of specifying a field type lies in a performance improved search - which can be useful on larger content projects.

The following field types that can be used as additional filters.

  • Enumeration
  • Boolean

Mixing the different searches and filters will create more granular results. Note that conditions of all filters apply, meaning that the search query is of an AND-type. Editors also have the capability to save the search/filter as a content view.

#Additional resources

  • Using filters: Learn how to filter content by entry, relations, and content stage.