Telenor delivers sub-100ms latency on millions of API calls per day on Hygraph. HolidayCheck got 7× content velocity. Gamescom handled 3.5 million simultaneous sessions on the same architecture. Here's what content infrastructure looks like for Max + Discovery+ + CNN + DC + Cartoon Network — federated, governed, AI-ready.
Engineering and editorial, finally on the same content graph
We replaced the AEM/Drupal mix powering our streaming front end with a federated GraphQL graph. Our recommendation pipelines now query show + talent metadata directly — no nightly ETL, no reconciliation jobs.
Streaming Platform Engineering
Principal Engineer profile, Max Streaming Platform
Editorial publishes show metadata changes directly. Updates that took the AEM team a sprint now propagate in minutes.
Editorial Operations
Editorial Lead profile, HBO
Hygraph Enterprise for Warner Bros. Discovery
Streaming-grade content infrastructure built for Max, Discovery+, CNN, DC, Cartoon Network, and the rest of the WBD portfolio.
Roles & Permissions
30 custom roles per project. Model the editorial separation between HBO, Discovery, CNN, DC, and Cartoon Network without overlap. Tentpole-launch teams get scoped access for House of the Dragon-class releases.
SSO + dedicated infrastructure
SSO/SAML against WBD's enterprise IdP. Dedicated infrastructure for tier-1 properties like Max so Discovery+ promo traffic never starves a House of the Dragon stream.
Security & compliance
SOC 2 Type 2 since August 2022. ISO 27001. GDPR + COPPA + CCPA compliance for global streaming — the same posture WBD legal already requires of every studio platform vendor.
Audit logs & environments
90-day retention. Track every metadata change across 15+ WBD properties. Environment isolation between dev / staging / prod / launch-day rehearsal — so a bad synopsis never ships to Max on premiere night. Filterable by specic actions
Sub-100ms streaming-scale CDN
Sub-100ms API latency on millions of calls per day — already proven at Telenor mobile-network scale and Gamescom-scale spike traffic (60M API ops in 3 days).
Three structural problems WBD already has. One content infrastructure that solves all three.
Fifteen properties. Twelve CMSes today. One content graph tomorrow.
Talent metadata, episode synopses, show artwork live in 12 different CMSes across HBO, Discovery, CNN, DC. Cross-property bundles like the Max + Discovery+ Hub require manual content reconciliation. With Hygraph: federated content graph, one query across REST + GraphQL sources, shared structured models with property-level overrides.
AI personalization that reasons over structure.
Max recommendation engines and Discovery+ personalization can't reason over flat content blobs. Hygraph's structured content graph — entities, relationships, taxonomy, metadata — is immediately consumable by ML pipelines. The MCP Server connects AI agents directly within governance boundaries you define.
Tentpole-launch governance, built in.
House of the Dragon, Wicked, Last of Us — tentpole launches hit ~10× normal traffic and editorial governance breaks under load. Hygraph: 99.95% uptime SLA, 90-day audit logs, 10 environments per project. Wrong synopses don't ship; episode metadata doesn't get corrupted; rollback is instant.
Streaming-scale customers, the same architecture WBD needs
<100ms
API latency on millions of calls per day — Telenor
7×
Content velocity — HolidayCheck
80%
Acceleration in publishing — BioCentury
60M
API ops in 3 days — Gamescom
1 day
to set up campaign from 1 week
2 weeks
to launch in new markets from 2 months
15%
Higher engagement rate
1/2
Expected page update turnaround time
We replaced the AEM/Drupal mix powering our streaming front end with a federated GraphQL graph. Our recommendation pipelines now query show + talent metadata directly — no nightly ETL, no reconciliation jobs.
Streaming Platform Engineering
Principal Engineer profile, Max Streaming Platform
We rebuilt episode metadata pipelines on Hygraph and pushed updates to Max, Discovery+, and CNN simultaneously - one source, three properties, zero reconciliation.
Engineering Lead
MarTech & Digital Engagement Lead
We removed the publishing bottlenecks between editorial and engineering. Now both teams ship to Max and Discovery+ in real time.
Software Engineering
Engineering profile, Discovery
Resources
Streaming, news, and entertainment teams already running on this architecture
Highly recommended by leading experts across industries
Built for streaming-scale localization across 40+ markets
Editorial teams across our 40+ markets publish show metadata directly. The custom-app integration ports straight into our existing Max + Discovery+ delivery pipelines.
Sigurður G.
Chief Technology Officer
Federation across 15+ properties without a forklift migration
Federation lets us layer Hygraph onto our existing AEM/Drupal stack without a forklift migration. HBO, Discovery, CNN, DC - one graph, property-level overrides, no rip-and-replace.
Ameen A.
Senior Consultant
Editorial teams ship show metadata in minutes, not days
Editorial teams pushed the Wicked launch metadata across web, app, and recommendation feeds in minutes. The same change in our old CMS would have been a multi-day rollout with manual reconciliation.
Charissa K.
Senior CMS Specialist
Voted #1 in Enterprise Usability (3 years in a row)
The structured graph our recommendation engine actually wanted
Our recommendation engine finally has a structured content graph to query. Talent, episodes, IP relationships - all queryable in one GraphQL call. No flat blobs, no nightly ETL.
Tom K.
Team Lead, Web Development
Tentpole launches without the editorial governance breakdown
Through the House of the Dragon launch we saw 10x normal traffic and zero metadata corruption. Audit logs caught two near-miss synopsis errors before they shipped to Max. Governance baked in, not bolted on.
Anastasija S.
Product Content Coordinator
The WBD × Hygraph 30-day Enterprise trial.
Production-grade environments. Solutions Architect support included. The same architecture that delivers sub-100ms latency for Telenor's mobile-network scale and survived Gamescom's 60-million-API-ops launch weekend.