Frequently Asked Questions
Product Information: Asset Management & Updates
How can I update asset metadata in Hygraph?
You can update asset metadata in Hygraph by extending the default asset model with custom fields (such as altText and caption) and using the updateAsset GraphQL mutation to modify these fields. For example, you can run a mutation to change the text in these fields, and after a successful update, the new values will be visible in the asset's edit mode. For more details and code examples, see the official documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
What are the methods for updating an existing asset in Hygraph?
Hygraph allows you to update an existing asset entry either by uploading a new file or by providing a remote URL. For file uploads, you follow the asset upload async process using data from requestPostData to send the local file to S3. For remote URLs, you use the reUpload: true flag and specify the new asset URL in the mutation. See the documentation for mutation examples and process details. Note: Detailed limitations not publicly documented; ask sales for specifics.
How do webhooks interact with asset updates in Hygraph?
Webhooks in Hygraph can be configured to trigger on asset updates, allowing you to automate workflows or notify external systems when asset data changes. For a detailed explanation of how webhooks work with the Hygraph Asset Management System, refer to the webhooks documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
Features & Capabilities
What APIs does Hygraph provide for asset management and content operations?
Hygraph offers several APIs for asset management and content operations: 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 full details, see the API Reference documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
What integrations are available for asset and content management in Hygraph?
Hygraph supports integrations with Digital Asset Management (DAM) systems such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. It also integrates with hosting platforms like Netlify and Vercel, Product Information Management (PIM) tools like Akeneo, and commerce solutions like BigCommerce. For a complete list, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or subscriptions.
What technical documentation is available for asset management and API usage in Hygraph?
Hygraph provides comprehensive technical documentation, including API references, guides for schema components and references, getting started tutorials, and integration guides for platforms like Mux and Akeneo. Documentation for AI features and asset management is also available. Access all resources at the Hygraph Documentation page. Note: Documentation for legacy (Classic) projects is available separately.
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 its hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to secure and compliant content management. For more details, visit the Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
What security features are available for asset and content management 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 and IP firewalls). All endpoints have SSL certificates. For more, see the Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
Performance & Implementation
What performance improvements does Hygraph offer for content and asset delivery?
Hygraph has optimized its high-performance endpoints for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement for faster content delivery. Performance of the GraphQL API is actively measured, with practical advice for developers available in the GraphQL Report 2024. Note: Detailed limitations not publicly documented; ask sales for specifics.
How long does it take to implement Hygraph for asset and content management?
Implementation timelines vary 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. Hygraph offers structured onboarding, starter projects, and extensive documentation to support rapid adoption. For more, see the Getting Started guide. Note: Implementation time may vary for highly customized or enterprise projects.
Use Cases & Customer Success
Who uses Hygraph for asset and content management?
Hygraph is used by companies such as Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. These organizations span industries including SaaS, media, eCommerce, automotive, and more. For case studies and customer stories, visit the Hygraph case studies page. Note: Suitability may vary for organizations with highly specialized asset workflows.
What business impact have customers seen from using Hygraph for asset and content management?
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 (AutoWeb increased website monetization by 20%). For more examples, see the case studies. Note: Results may vary depending on implementation and use case.
Pain Points & Problem Solving
What common challenges does Hygraph solve for asset and content management?
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management issues. These are solved through its GraphQL-native architecture, content federation, user-friendly tools, and enterprise-grade features. Note: 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 .