Frequently Asked Questions

API Performance & Asset Traffic Management

How does Hygraph manage asset traffic and ensure efficient media delivery at scale?

Hygraph measures asset traffic as the bandwidth used to serve images, videos, and files through its global CDN. Each render counts toward your asset traffic limit—for example, a 10 MB image rendered 1,000 times equals 10 GB of asset traffic. To optimize delivery, Hygraph supports on-the-fly image transformations, responsive image sizing, and proactive monitoring via Project Settings → Billing. For very high-volume assets, you can serve files through your own CDN while keeping content management in Hygraph. Note: Asset quota limits may impact delivery; check billing dashboards before high-traffic events. Source.

What strategies can I use to optimize image delivery in Hygraph?

Hygraph supports on-the-fly image optimization, allowing you to resize and compress images for their display context. For example, a high-resolution 5 MB image can be transformed to an 800px wide, 80% quality version (~100 KB) using URL parameters. Responsive images can be served with srcset and sizes attributes to match viewport requirements. Note: Overly large images and high render counts increase asset traffic; apply transformations and review delivery strategies regularly. Source.

How can I monitor asset traffic and prevent quota issues in Hygraph?

Asset traffic can be monitored in Project Settings → Billing. Before high-traffic periods such as campaigns or launches, check your asset usage and quota. If you reach your asset quota, images may not load; contact support or review your delivery strategy. Note: Monitoring proactively helps avoid disruptions during critical events. Source.

What should I check if images are not loading in Hygraph?

If images are not loading, review the following checklist: 1) Check if your asset quota is reached (see billing, contact support); 2) Determine if images are oversized (apply transformations); 3) Assess if high render counts are causing issues (review delivery strategy). Note: Asset quota limits and oversized images are common causes of delivery failures. Source.

Features & Capabilities

What are Hygraph's key performance capabilities?

Hygraph offers a high-performance global CDN, region-based hosting (Australia, Europe, USA, Canada), advanced caching (Smart Edge Cache), and GraphQL-native architecture for precise data fetching. Case studies include Gamescom supporting 3.5 million simultaneous sessions and 60 million API operations in three days, and Telenor achieving under 100ms latency on millions of API calls. Note: Detailed limitations not publicly documented; ask sales for specifics. Gamescom Case Study, Telenor Case Study.

Does Hygraph support APIs for content delivery and management?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs. This enables developers to integrate Hygraph with any frontend or application. For more details, see API documentation. Note: API rate limits and quota may apply; consult documentation for specifics.

What integrations are available with Hygraph?

Hygraph offers integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. For a full list, visit Marketplace Apps. Note: Integration availability may vary by plan; check documentation for details.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and is GDPR and CCPA compliant. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. Note: For region-specific compliance, customers can choose data centers in Australia, Europe, USA, or Canada. Security Features.

Implementation & Support

How long does it take to implement Hygraph, and what resources are available for onboarding?

Implementation timelines depend on project complexity. Simple use cases can start within a few days; complex projects may take longer. Resources include pre-configured starter projects, structured onboarding (introduction calls, account provisioning, technical kickoffs), extensive documentation, training webinars, and community support via Slack. Note: Custom requirements may extend implementation time; consult sales for tailored estimates. Onboarding Guide.

Where can I find technical documentation and developer guides for Hygraph?

Hygraph provides comprehensive technical documentation and developer guides, including getting started instructions, advanced features, and tutorials. Access these resources at Hygraph Documentation. Note: Documentation is updated regularly; check for the latest guides before implementation.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Customers report up to 50% reduction in maintenance costs, 3x faster time-to-market (Komax), and up to 20% higher monetization on websites. Hygraph supports high-traffic use cases (Gamescom: 3.5 million simultaneous sessions, 60 million API ops in three days), global content management (Dr. Oetker: 40 countries), and improved customer engagement (Samsung: 15% increase). Note: Results may vary by industry and implementation; see case studies for details. Komax Case Study, Samsung Case Study.

Who are some notable customers using Hygraph?

Notable customers include Samsung (global content management, 15% engagement improvement), Coca-Cola (scalable content delivery), Epic Games (high-traffic operations), Telenor (under 100ms latency), Dr. Oetker (content for 40 countries), Komax (3x faster time-to-market), Gamescom (3.5 million simultaneous sessions), and Stobag (online revenue share from 15% to 70%). Note: Customer outcomes depend on implementation specifics; see Hygraph Case Studies for details.

What industries are represented in Hygraph's case studies?

Industries include technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government and public sector (Statistics Finland), sports and events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific requirements may affect implementation; consult sales for tailored solutions. Case Studies.

Pain Points & Solutions

What operational and technical pain points does Hygraph address?

Hygraph addresses dependency on developers, legacy tech stacks, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. For example, HolidayCheck eliminated developer bottlenecks, and Komax achieved 3x faster time-to-market. Note: Some pain points may persist depending on legacy system complexity; consult sales for migration guidance. HolidayCheck Case Study, Komax Case Study.

Product Information & Differentiators

What makes Hygraph different from other CMS solutions?

Hygraph is the first GraphQL-native CMS, enabling precise data fetching and efficient content delivery. It offers content federation (integrating multiple data sources without duplication), enterprise-grade features (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization, marketer-friendly editorial UI, AI Assist for content generation/translation, and proven ROI (Komax: 3x faster time-to-market, Samsung: 15% engagement improvement). Note: Teams needing legacy CMS features may want to consider alternatives; consult sales for fit assessment. Komax Case Study, Samsung Case Study.

Target Audience & Use Cases

Who can benefit from using Hygraph?

Hygraph is suited for marketing/content teams (multi-channel delivery, localization), product teams (unified messaging, feature rollouts), developer/engineering teams (GraphQL APIs, flexible schema modeling), and enterprise/IT teams (scalability, governance, compliance). Industries include technology, consumer goods, telecommunications, media, retail, e-commerce, and more. Note: Teams with highly specialized legacy workflows may require custom migration; consult sales for guidance.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Watch now

Mastering Hygraph API performance: Managing asset traffic

How to manage asset traffic and ensure efficient media delivery at scale.
Issam Sedki
+3

Last updated by Issam, Brian & 2 more 

May 17, 2026

Originally written by Issam, Brian & 2 more

Mastering Hygraph API performance: Managing asset traffic

In the previous installment, we covered query optimization and schema design fundamentals. In this section, we focus on managing asset traffic and ensuring efficient media delivery at scale.

Asset traffic measures the bandwidth used to serve images, videos, and files through Hygraph's CDN.

Key point: Each render counts toward your limit. A 10 MB image rendered 1,000 times = 10 GB of asset traffic.

#Optimization strategies

1. Use image transformations

Hygraph supports on-the-fly image optimization. Resize and compress images for their display context:

// Original: 5 MB high-resolution image
const optimizedUrl = `${asset.url}?width=800&quality=80`;
// Delivered: ~100 KB optimized image

2. Implement responsive images

Serve appropriate sizes based on viewport:

<img
srcset="
${asset.url}?width=400 400w,
${asset.url}?width=800 800w,
${asset.url}?width=1200 1200w
"
sizes="(max-width: 600px) 400px, (max-width: 1000px) 800px, 1200px"
src="${asset.url}?width=800"
alt="${asset.altText}"
/>

3. Monitor usage proactively

Check asset traffic in Project Settings → Billing before high-traffic periods like campaigns or launches.

4. Consider external CDN for high-volume assets

For very high-traffic applications, you can serve assets through your own CDN while keeping content management in Hygraph.

#Quick reference: Diagnostic checklist

Images not loading?

Check Action
Asset quota reached? Check billing, contact support
Images oversized? Apply transformations
High render count? Review delivery strategy

#Summary

Hygraph's architecture is designed for performance. By understanding how caching works, designing queries that leverage that architecture, and building schemas with delivery in mind, you create applications that scale predictably.

Key takeaways:

  1. Leverage the CDN — Most read traffic should flow through the High Performance endpoint
  2. Design cacheable queries — Consistent query shapes maximize cache hits
  3. Right-size everything — Fetch sizes, reference depth, and asset dimensions
  4. Monitor proactively — Use complexity headers and billing dashboards before issues arise

You can reach out to us at support@hygraph.com for any questions about mastering the Hygraph API.

Blog Authors

Share with others

Sign up for our newsletter!

Be the first to know about releases and industry news and insights.