Frequently Asked Questions

Asset Management & API Usage

What is the Assets model in Hygraph and how is it used?

The 'Assets' model is a core feature in Hygraph, automatically added to every new project. It allows you to store images and other file types, which can be managed and referenced in your content entries. For more details, see our documentation on working with assets.

How can I update asset metadata in Hygraph?

You can extend the Assets model with custom fields (such as altText and caption) and update them using GraphQL mutations. For example, the updateAsset mutation allows you to change metadata fields. After running the mutation, the updated fields will be visible in the asset's edit mode. Learn more about Mutations.

How do I update an existing asset file in Hygraph?

Hygraph allows you to update an existing asset entry by reuploading a new file or using a remote URL. You can use the reUpload: true parameter in the updateAsset mutation to replace the file. For file uploads, follow the asset upload async process using data from requestPostData to send the local file to S3.

Can I update assets via remote URL in Hygraph?

Yes, you can update assets via remote URL by using the reUpload: true parameter and specifying the uploadUrl in the updateAsset mutation. This allows you to replace the asset file with one hosted at a remote location.

Where can I find the API Reference for Hygraph Assets?

You can find detailed information in our API Reference document on Assets.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph is a GraphQL-native Headless CMS offering operational efficiency, financial benefits, and technical advantages. Key features include Smart Edge Cache for performance, content federation for multi-source integration, custom roles, rich text management, and project backups. Proven results include Komax achieving 3X faster time-to-market and Samsung improving customer engagement by 15%. See more customer stories.

What problems does Hygraph solve for businesses?

Hygraph addresses operational inefficiencies (eliminating developer dependency, modernizing legacy tech stacks), financial challenges (reducing costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, resolving integration difficulties, optimizing performance, and improving localization and asset management). See related KPIs.

How does Hygraph differentiate itself in solving pain points?

Hygraph stands out as the first GraphQL-native Headless CMS, offering a user-friendly interface, content federation, Smart Edge Cache, and robust integration capabilities. Its focus on composability, scalability, and enterprise-grade features sets it apart from competitors like Sanity, Prismic, and Contentful. Learn more about enterprise features.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for security and data protection. For more details, visit the security features page and security and compliance report.

What security features does Hygraph offer?

Hygraph provides granular permissions, SSO integrations, audit logs, encryption (at rest and in transit), regular backups, and enterprise-grade compliance features such as dedicated hosting and custom SLAs. Security issues can be reported, and certified infrastructure details are available in the security report.

Performance & Reliability

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

Hygraph uses Smart Edge Cache for enhanced performance and faster content delivery, especially for high-traffic and global audiences. Its high-performance endpoints and GraphQL API optimizations ensure reliability and speed. For more details, see the blog post on endpoint improvements.

Ease of Use & Onboarding

How easy is it to get started with Hygraph?

Hygraph offers a free API Playground for immediate exploration, a free forever developer account, and a structured onboarding process including introduction calls, account provisioning, and technical/content kickoffs. Training resources (webinars, live streams, how-to videos) and extensive documentation are available at Hygraph Documentation.

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

Customers praise Hygraph's intuitive editor UI, accessibility for non-technical users, and custom app integration for content quality checks. Hygraph was recognized for "Best Usability" in Summer 2023. Review titles highlight flexibility, user-friendliness, and effectiveness for diverse teams. Try Hygraph.

Support & Implementation

What support and training resources are available for Hygraph customers?

Hygraph provides 24/7 support via chat, email, and phone, real-time troubleshooting through Intercom chat, a community Slack channel (join here), extensive documentation (Hygraph Documentation), webinars, live streams, and how-to videos. Enterprise customers receive a dedicated Customer Success Manager and structured onboarding.

How long does it take to implement Hygraph?

Implementation time varies by project scope. For example, Top Villas launched a new project within 2 months from initial contact, and Si Vale met aggressive deadlines during their initial implementation. The onboarding process is designed for efficiency, with immediate access via API Playground and developer accounts.

How does Hygraph handle maintenance, upgrades, and troubleshooting?

Hygraph is cloud-based, so deployment, updates, security, and infrastructure maintenance are managed by Hygraph. Upgrades are seamless, with new features integrated automatically. Troubleshooting is supported by 24/7 support, Intercom chat, documentation, and an API Playground for self-service.

Use Cases & Customer Success

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, and manufacturing. It suits organizations modernizing legacy tech stacks, global enterprises needing localization, asset management, and content federation. See customer stories.

Can you share some customer success stories with Hygraph?

Komax achieved a 3X faster time-to-market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement by 15%, and Stobag increased online revenue share from 15% to 70%. Explore more customer stories.

KPIs & Metrics

What KPIs and metrics are associated with the pain points Hygraph solves?

Key metrics include time saved on content updates, system uptime, content consistency across regions, user satisfaction scores, reduction in operational costs, speed to market, maintenance costs, scalability metrics, and performance during peak usage. For more details, visit the blog on CMS KPIs.

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

#Updating assets

#Overview

Since assets are a system model, and automatically added to every project, you can extend them with your own custom fields.

These fields can be updated using GraphQL mutations.

#Update metadata

In the following example, we have added altText and caption fields to our Assets model. Here, we are using an updateAsset mutation to change the text in them:

After successfully running this mutation, if you access your asset in edit mode, you will see the new altText and caption.

Learn more about Mutations.

#Update existing asset

The Hygraph Asset Management System offers a way to update an existing asset entry and reuploading a new file for it.

To do this, there is a route to do a file upload, or a remote URL upload.

#Update via remote URL

Use reUpload: true as follows:

mutation test {
updateAsset(
where: {id: "<YOUR_ASSET_ID>"}
data: {reUpload: true, uploadUrl: "<NEW_ASSET_URL>"}
) {
id
upload {
status
expiresAt
error {
code
message
}
}
}
}

#Update via file upload

To update an asset via file upload you need to follow the asset upload async process, with the data you get from requestPostData to send the local file to S3.

Use reUpload: true as follows:

mutation test {
updateAsset(where: {id: "<YOUR_ASSET_ID>"}, data: {reUpload: true}) {
id
upload {
status
expiresAt
error {
code
message
}
requestPostData {
url
date
key
signature
algorithm
policy
credential
securityToken
}
}
}
}