One unified platform. Six solution pillars. The same global network that already serves dolby.com & dolby.io — now powering every workload Dolby runs.
Access · WARP · Gateway · CASB · DLP · Email Security · Managed OAuth · Brand Protection
Magic Transit · Magic WAN · Magic Firewall · CNI · Spectrum · Load Balancing
WAF · L7 DDoS · Bot Management · API Shield · Argo · Cache Reserve · Page Shield
Workers AI · AI Gateway · AI Search (AutoRAG) · Agents SDK · Browser Run · Vectorize
Workers · R2 · Durable Objects · Agents SDK · Workflows v2 · OptiView manifests · SGAI pipeline
30-day quick wins → 60-day foundation → 90-day AI agents → 12-month full platform
From Dolby Atmos in 200M+ cars and living rooms to Dolby OptiView powering live sports for the NFL, NASCAR, Paddy Power and Bet365 — Dolby's reach is already global. The Cloudflare Developer Platform is how that reach gets faster, more personalized, and AI-native — without leaving the Cloudflare network Dolby already depends on.
Dolby's product portfolio spans cinema, in-car, streaming, music, and a fast-growing B2B developer platform. Every one of these has a compute, delivery, real-time, or personalization layer that Cloudflare is uniquely positioned to accelerate.
Immersive, object-based audio in movies, music streaming, gaming, and now 200M+ cars (BMW 7 Series, Mahindra XUV 7XO, Tata Sierra, Hyundai Elexio, and more).
HDR picture standard featured in Fast Company's Most Innovative 2026 list. Adopted across Peacock, Douyin, ETV Win, EVO Entertainment, and consumer TVs.
The streaming platform born from acquiring Millicast (real-time WebRTC) and THEO (player). Ultra-low latency, SDK-driven video for live sports, betting, and fan engagement.
Premium theatrical format combining Dolby Vision + Atmos. Expanding aggressively across India (Pune, Bengaluru, Tamil Nadu) and partnering with TOHO in Japan.
Next-gen audio codec coming to Peacock for live sports and expanding to QQ Music. Powers efficient Atmos delivery at streaming scale.
World's first soundbar audio system powered by Atmos FlexConnect (with LG). Brings spatial audio to mainstream TVs without complex setup.
Dolby is already a Cloudflare customer at the CDN/zone layer. The fastest credibility win is replacing Zscaler with Cloudflare Zero Trust on a 90-day, side-by-side migration plan that ends with the Zscaler contract non-renewed. Every phase below builds incrementally on what's already deployed — no rip-and-replace, no user-facing outage.
Cloudflare runs alongside Zscaler from day one. Engineers keep the Zscaler client during Phases 1–2 — only the apps that have moved get steered to Cloudflare. By Day 90, Zscaler is decommissioned and the renewal is non-renewed.
Consolidating Zscaler (SSE), Palo Alto Networks (network firewalls), AWS S3 + CloudFront egress, and Proofpoint (email security) onto the Cloudflare Connectivity Cloud isn't just a security upgrade — it's a measurable line-item reduction across four enterprise contracts that Dolby's CFO already sees on the budget every quarter. Below is the modeled annual impact based on typical enterprise contract sizing for a $1.3B media & technology company.
Every number below is modeled from typical enterprise pricing for a global media & technology company of Dolby's scale (NYSE: DLB · ~2,000 employees · $1.3B FY24 revenue · global office footprint · multi-region OptiView platform on AWS). Final numbers will vary based on actual contract terms — these are conservative, sales-friendly estimates.
A note on these numbers: These are modeled estimates based on standard enterprise pricing for a company of Dolby's size — not committed quotes. Actual savings depend on Dolby's current contract terms, multi-year discounts already locked in with each vendor, and the specifics of OptiView's AWS architecture. The Cloudflare account team can produce a custom TCO analysis with NDA-protected pricing for each line item within two business days of a discovery conversation. The relative ratios (Cloudflare ~30–70% lower per workload) consistently hold across Cloudflare's enterprise media & technology customer base.
Dolby's value lives in pre-release content, source code, encoder IP, and the trust of every major studio, OEM, and broadcaster. Cloudflare Zero Trust replaces a stack of VPN concentrators, legacy SWG appliances, and one-off SaaS proxies with a single identity-aware network — built for a company whose attack surface spans Hollywood, Detroit, Seoul, and a developer platform with thousands of API consumers.
Vision masters and Atmos stems for unreleased films flowing to dozens of studios & mastering houses
THEO Technologies + Millicast brought new corp networks, identity providers, and SaaS tenants under one roof
BMW, Mahindra, Hyundai, Tata, LG, TOHO all need scoped access to Dolby encoders & certification portals
7,000+ patents (incl. acquired GE Licensing portfolio) — a target for nation-state and economic-espionage actors
Today, every studio that mixes a Dolby Atmos title or grades a Dolby Vision master likely connects via a legacy VPN concentrator (Cisco AnyConnect, Pulse, Palo Alto GlobalProtect). One stolen credential = full lateral movement to pre-release content. Cloudflare Access swaps the VPN for clientless, identity-aware reverse proxy to mastering tools, Dolby Professionals, and pre-release Vision portals — with device posture and conditional MFA per studio.
BMW, Mahindra, Tata, Hyundai, LG, TOHO — every Dolby licensee needs scoped, audited access to certification suites, encoder downloads, and IP licensing portals. Managed OAuth in Cloudflare Access (new in Agents Week 2026) gives every OEM a federated identity, scoped JIT permissions, full audit log per engineer, and instant revocation when a partner program ends.
Mastering engineers, sound designers, and ML researchers work across dozens of SaaS tools — Avid, Frame.io, GitHub, Figma, Hugging Face, OpenAI, Anthropic. Cloudflare Gateway inspects every egress request from corp devices, blocks shadow-AI uploads of unreleased content, enforces DLP on Atmos stems and Vision XMLs, and replaces the Zscaler / Netskope contract with a single agent (WARP) already deployed for Access.
The THEO Technologies and Millicast acquisitions brought two engineering orgs, two identity providers, and two cloud footprints (largely AWS). Rebuilding into one VPC is an 18-month, multi-million-dollar project. Cloudflare Tunnel + Mesh lets THEO/Millicast resources stay where they are, exposed only through identity-checked tunnels — no public IPs, no flat L3 network, integrated in days, not quarters.
The OptiView console (dashboard.dolby.io) is the control plane for live streams powering the NFL, NASCAR, Paddy Power, Bet365, and Sky Racing. A single compromised customer account can take down a live game. WAF + Bot Management + Turnstile defend the dashboard from credential stuffing, scraper bots, and account takeover — at the same edge that already terminates dolby.io traffic.
"Dolby" is one of the world's most-spoofed brands — phishing kits target consumers ("verify your Dolby Atmos subscription"), licensees ("urgent IP renewal"), and the press desk. Cloudflare Email Security (Area 1) inspects inbound mail against business-context AI, while Brand Protection watches new domain registrations for dolby-* and *-dolby.com lookalikes — and lets Dolby's IP & trust team file takedowns in one click.
Dolby runs a global engineering, mastering, and content-delivery footprint — San Francisco HQ, Beijing, Bengaluru, Wrocław (Poland), TOHO partner facilities in Tokyo, Dolby House Shanghai, plus the THEO Belgium and Millicast San Diego offices. Today that network is held together by some combination of MPLS circuits, SD-WAN, regional ISP transit, and dedicated DDoS scrubbing for OptiView's NFL and NASCAR ingest. Cloudflare's Network as a Service collapses all of that into one Anycast network already in 330+ cities — the same one that already serves dolby.com and dolby.io.
SF ↔ Beijing ↔ Bengaluru ↔ Wrocław ↔ Tokyo ↔ Shanghai over Cloudflare's Anycast backbone. Sub-second site turn-up, identity-aware routing — without a 90-day carrier provisioning cycle or per-Mbps bill.
Global L3/L4 firewall policy applied to every byte entering Dolby's network — office, cloud, partner. One rule plane, millisecond propagation worldwide. Decommission the appliance refresh cycle across all 8 office sites.
Global & local load balancing across OptiView origins, Dolby.io APIs, and AWS/GCP encode farms. Health checks every 15s, dynamic steering, session affinity. Replace the rack of F5s without losing the features.
Always-on L3/L4 DDoS mitigation at 500+ Tbps of edge capacity. Advertised via Dolby's own BGP. No swing during attacks — clean traffic forwards via GRE or CNI directly to OptiView's NFL+, NASCAR, & Paddy Power ingest.
Dolby's global engineering footprint (SF, Beijing, Bengaluru, Wrocław, Tokyo, Shanghai) likely runs MPLS or SD-WAN overlays from carriers like AT&T, NTT, or Tata Communications. Expensive, slow to provision, and not built for cloud-native traffic.
THEO (Belgium), Millicast (San Diego), and GE Licensing IP each came with their own transit, firewall stack, and ISP relationships. Integrating them into a unified Dolby WAN is a multi-quarter project per acquisition.
NFL+, NASCAR, Paddy Power, and Bet365 ingest endpoints are prime DDoS targets — especially during live betting windows. Today this likely runs through a dedicated scrubbing vendor (Arbor / Radware / Akamai Prolexic) on top of Cloudflare's edge.
OptiView's encoding pipelines, Vision mastering tools, and ML training likely sit across AWS, GCP, and on-prem GPU clusters. Inter-cloud and cloud-to-office traffic crosses the public internet — paying egress twice and gaining nothing.
OptiView's RTMP, WHIP, and SRT ingest endpoints for NFL+, NASCAR, Paddy Power, Sky Racing, and Bet365 are now mission-critical infrastructure. A single Sunday afternoon outage during NFL kickoff is a board-level event. Magic Transit advertises Dolby's IP space via BGP, scrubs L3/L4 DDoS volumetric & protocol attacks (SYN flood, UDP amp, DNS reflection, Memcached, Mirai variants) at 500+ Tbps of edge mitigation capacity, and forwards clean traffic via Anycast GRE or CNI. No BGP swing during attacks. No scrubbing trombone. No clean-pipe carrier on top.
Connect SF HQ, Beijing, Bengaluru, Wrocław (Dolby Poland), Tokyo (TOHO partner), Shanghai (Dolby House), Belgium (THEO), and San Diego (Millicast) over Cloudflare's Anycast backbone instead of carrier MPLS. Cancel the AT&T / NTT / Tata MPLS contract over 18 months as sites migrate one-by-one. Sub-second site turn-up, identity-aware routing, BFD failover, and full integration with Access & Gateway — without paying carrier per-Mbps rates that have not dropped since 2015.
Dolby's firewall policy today is fragmented across Palo Alto / Fortinet / Cisco ASA appliances per office, AWS Security Groups per VPC, and probably legacy stuff in the dark. Magic Firewall is a single global L3/L4 firewall + IDS that applies the same rules to every byte entering Dolby's network — office, cloud, partner — with millisecond rule propagation across 330+ cities. No more appliance refresh cycles at 8 sites every 5 years. No more change-control meetings to push a rule to 12 different consoles.
OptiView's origins span multiple AWS regions, GCP for ML workloads, and on-prem GPU clusters. Cloudflare Load Balancing replaces the rack of F5 BIG-IPs (and the AWS ELB / NLB / ALB stack on top) with one global L4/L7 load balancer. Active health checks every 15s, dynamic geo-steering for the closest healthy origin, session affinity for stateful streams, automatic failover during region outages, and weighted round-robin for canary deploys of new encoder versions.
CNI gives Dolby private, dedicated physical interconnects to AWS, GCP, Azure, Oracle, plus 50+ carriers at major exchanges (Equinix, Megaport, Digital Realty). Stop paying AWS Data Transfer + a Cloudflare egress on the same byte. OptiView's encode origins on AWS, Dolby's GPU clusters wherever they sit, and the mastering rigs in TOHO/Shanghai all land on Cloudflare's network without crossing the public internet. Combined with R2's zero-egress storage, the AWS bill shrinks materially.
Spectrum protects and accelerates every non-HTTP protocol Dolby runs: OptiView's WebRTC SFU, SRT ingest, RTMP for legacy broadcasters, NDI/Dante audio for mastering, plus SSH bastions and SFTP for studio handoffs — all behind the same DDoS protection dolby.io already gets. Magic WAN Connector bridges acquired companies (THEO, Millicast, future M&A) onto Dolby's backbone in hours via a 1U appliance — not quarters of IP-range renumbering.
Why this is the right moment for Dolby: OptiView turned Dolby into a real-time infrastructure provider. The NFL, NASCAR, and Paddy Power don't tolerate the same DDoS event-handling SLA an enterprise MPLS WAN tolerates. Cloudflare's NaaS is the only product set where the same network that already serves dolby.io traffic also runs your office WAN, your DDoS scrubbing, your cloud interconnect, and your acquired-company integration — without the multi-vendor hairball Dolby's network team is currently maintaining.
Dolby's web & API surface area is huge — dolby.com, dolby.io, optiview.dolby.com, dashboard.dolby.io, the OptiView player SDKs delivered to NFL+ apps, professional.dolby.com licensing portal, news.dolby.com, plus the dozens of customer-facing dashboards across THEO and Millicast. Cloudflare's Application Security & Performance stack is already partially in place — it should be the standard for every Dolby property.
Block OWASP Top 10, zero-days (Cloudflare patches before CVE publication), and L7 DDoS targeting OptiView's dashboard during NFL Sunday peaks. Managed rules + custom rules + emergency rules deployable in <30 seconds globally.
Sportsbook bots scraping odds, credential stuffing on dashboard.dolby.io, fake account signups, content scrapers stealing Atmos previews. ML-driven bot score on every request — block, challenge, or rate-limit by intent, not IP.
OptiView's REST + GraphQL APIs are how every customer (NFL, NASCAR, Paddy Power) integrates. Cloudflare API Shield does schema validation, mTLS enforcement, sequence/abuse detection, and discovery of shadow API endpoints engineers forgot to document.
Tiered Cache, Argo Smart Routing, Smart Hints, and HTTP/3 + 0-RTT for every Dolby property. Plus Cache Reserve for OptiView's long-tail VOD libraries — keeping rarely-accessed content close to viewers without origin hits.
dashboard.dolby.io is the control plane for every NFL, NASCAR, Paddy Power live stream. One compromised customer = a live game outage.
Competitors and arbitrage bots scrape OptiView odds-overlay APIs millions of times per day. Without ML bot detection, rate-limiting is a blunt tool.
Volumetric L3 DDoS is one thing — but slow-HTTP and application-layer attacks during NFL Sunday or a Paddy Power live race need an application-aware WAF.
After acquiring THEO + Millicast, OptiView's actual API surface (versus what's documented) is uncertain. Undocumented endpoints are the #1 source of API breaches.
Cloudflare's Managed Ruleset (OWASP CRS + Cloudflare's own threat intel) protects every Dolby app from injection, XSS, RCE, deserialization, and supply-chain attacks. When the next Log4Shell drops, Cloudflare ships an emergency rule before the CVE is even published — and Dolby's apps are protected in under 30 seconds without a code release.
L3 volumetric attacks get headlines, but the real damage to OptiView comes from L7 floods that look like legitimate viewer traffic. Cloudflare's HTTP DDoS engine uses 50+ signals (TLS fingerprint, IP reputation, request entropy, JS challenge response) to surgically block bad requests during NFL Sunday or a Bet365 in-play surge — without degrading real fans.
Cloudflare's ML-driven bot score evaluates every request against trillions of HTTP signals/day. For Dolby specifically: block arbitrage bots scraping OptiView odds, stop credential stuffing on dashboard.dolby.io, kill fake-account signups on Millicast self-serve, and Turnstile (the CAPTCHA replacement) ships on every signup form. Headless Chrome, Selenium, Playwright, and JA3 anomalies are all flagged automatically.
OptiView's REST & GraphQL APIs are the integration point for the NFL, NASCAR, Paddy Power, Sky Racing, Bet365, and every developer building on Millicast. API Shield auto-discovers every endpoint in production traffic (including the ones engineers forgot existed), validates against OpenAPI/GraphQL schemas, enforces mTLS for first-party clients, detects API abuse sequences, and blocks endpoints that drift from spec — without a single line of customer code change.
Every Dolby property gets HTTP/3 + 0-RTT for sub-50ms TLS resumption, Argo Smart Routing for ~30% faster origin fetches via Cloudflare's private backbone, Tiered Cache to reduce origin egress by another 60%+, and Smart Hints that auto-generate 103 Early Hints to start preloading critical assets before the HTML even arrives. Page Speed Insights jumps without a single front-end change.
Universal SSL + Advanced Certificate Manager handle every cert across dolby.com, dolby.io, optiview.dolby.com, and the 100s of vanity hostnames customer integrations create. Page Shield monitors every JavaScript Dolby's pages load (Google Analytics, Optimizely, Hotjar, partner SDKs) and alerts the second one is tampered with — the same Magecart-class attack vector that compromised Ticketmaster & British Airways.
Dolby is a 60-year-old audio & imaging R&D powerhouse — neural codecs (AC-4 has ML components), Vision 2 tone mapping, AI-driven loudness, Atmos object spatialization, music mastering assistants, automated highlight detection for live sports. The compute lives in expensive GPU clusters. Cloudflare's AI stack lets Dolby move inference to the edge, govern third-party AI usage, and ship AI-native features without a separate AI platform contract.
Run Llama 3.3, Mistral, Whisper, BGE embeddings, and Dolby's own ONNX models on Cloudflare's GPU fleet in 330+ cities — pay per neuron, not per dedicated H100/hour. Sub-30ms inference colocated with the OptiView player request.
Unified proxy for OpenAI, Anthropic, Bedrock, Vertex, Workers AI. Built-in caching (90%+ hit rate on repeated prompts), rate limiting, cost analytics, prompt logging, and PII redaction. One control plane for every AI call Dolby engineers make.
Index Dolby's entire knowledge base — engineering docs, support articles, partner SDK docs, customer-stories.json — into a managed RAG. Power "ask Dolby" copilots for support, sales, and developer self-serve without building a vector pipeline.
Build production AI agents with persistent memory, tools, and durable execution. Sandboxes safely execute code generated by encoder-tuning agents and untrusted advertiser creatives in OptiView's SGAI pipeline.
Dolby's ML team runs Atmos object detection, Vision 2 tone-mapping, and AC-4 encoders on dedicated AWS p4d/p5 or on-prem A100s. Idle GPU time is pure burn.
Engineers across Dolby (and acquired teams from THEO/Millicast) hit OpenAI & Anthropic APIs directly. No central observability, no caching, no rate limits, no PII controls.
Multiple Dolby teams have probably built their own RAG pipelines (Pinecone + LangChain + GPT-4) for internal docs. Each one is undermaintained and drifts from current docs.
Sound engineers using ChatGPT to summarize mix notes. Researchers uploading Atmos stems to Hugging Face Spaces. Real risk of unreleased-content leakage through GenAI tools.
Run automatic caption generation (Whisper), real-time content moderation, live highlight detection (custom CV models), Atmos loudness compliance, and per-viewer thumbnail personalization on Cloudflare's GPU fleet — in the same colo as the OptiView player request. Pay per neuron, not per hour of idle H100. Auto-scales to NFL Sunday peak and back to zero on Monday morning.
Every Dolby engineer's call to OpenAI, Anthropic, Bedrock, Vertex, or Workers AI routes through AI Gateway. 90%+ cache hit rates on repeated prompts cut LLM spend by 50%+ on day one. Per-team rate limits, real-time cost dashboards by department, prompt + response logging for safety review, PII redaction, and instant fallback when OpenAI is down.
Point AI Search at Dolby's docs corpus — developer.dolby.io, professional.dolby.com, internal wikis, customer-stories.json, the OptiView API reference — and it crawls, chunks, embeds, indexes, retrieves, and generates. No Pinecone bill. No LangChain spaghetti. No drift between docs and the RAG. Power a customer support copilot, a developer Q&A bot, and an internal sales-engineer copilot from one pipeline.
Build production AI agents with the Agents SDK (announced at Agents Week 2026). Per-fan agents that remember commentary preferences across NFL+ sessions, per-stream agents that coordinate SGAI ad selection during a Paddy Power live race, per-title encoding agents that learn from every Vision 2 master. Agent Memory (SQLite in Durable Objects) persists state across sessions and survives across regions.
Browser Run gives Dolby agents a real Chrome browser to interact with the web — perfect for cinema-ops agents monitoring projector consoles, content-ops agents checking OptiView playback on every device family, or pre-flight agents that test every customer integration before a release. Sandboxes GA safely executes untrusted code: advertiser creatives in SGAI, customer-uploaded encoder profiles, or experimental Workers AI inference jobs.
Cloudflare Gateway's AI shadow-IT controls detect when an engineer uploads an Atmos stem to Hugging Face or pastes Vision XMLs into ChatGPT — by content fingerprint, not just URL category. Agent Readiness assesses Dolby's security posture before launching agents in production. Enterprise MCP exposes OptiView APIs as governed MCP servers so Claude, ChatGPT, and Cursor can integrate safely.
OptiView's developer surface — Player SDKs, Streaming APIs, SGAI integrations, the Millicast WebRTC stack, THEO's player ecosystem — competes with the largest cloud platforms (AWS Elemental, GCP Live Stream API, Azure Media Services). Cloudflare's Developer Platform is purpose-built for the exact workloads OptiView runs: low-latency, globally distributed, stateful, real-time, video-aware. Dolby could be shipping new OptiView features in days, not quarters.
Every OptiView personalization decision — manifest stitching, DRM token issuance, geo-restriction enforcement, ad marker injection — runs in the same colo as the player. Sub-5ms response, no cold starts, no Lambda concurrency limits.
One DO per live OptiView stream coordinates viewer pools, interactive overlays, live betting tickers, multi-viewer sync. One DO per fan persists commentary preferences, watched-content history, & betting position across sessions.
R2 for zero-egress VOD archives. D1 for per-customer OptiView config. KV for sub-ms feature flags. Vectorize for content discovery. Hyperdrive for fronting OptiView's existing Postgres without rewriting it.
Workflows v2 orchestrates the bid → creative → manifest-stitch SGAI pipeline durably across thousands of concurrent ad breaks. Queues handle async fan-out: ingest events → encoder triggers → CDN purges.
OptiView's manifest service, DRM tokenizer, and SGAI orchestrator likely run on AWS Lambda (with cold starts) and ECS/Fargate (with always-on cost), behind ALB and CloudFront.
The 100s of TB of NFL+, NASCAR, and Paddy Power VOD archives sit in S3 — with CloudFront egress fees compounding every quarter. Cross-region replication is a separate bill again.
OptiView's config, customer metadata, and session state likely sit in RDS Postgres + ElastiCache Redis behind multiple VPCs. Connection pooling is a perennial problem.
Every OptiView dashboard PR probably gets a Vercel preview, a Heroku review app, or a one-off ECS environment. Bills add up. Developer experience is fragmented.
Every OptiView HLS/DASH manifest is currently a static-ish file with some token substitution. With Workers, every manifest is freshly assembled per viewer in <5ms: language tracks based on geo, SGAI ad markers based on the viewer's bidder result, geo-restricted feeds enforced at the manifest layer, DRM tokens minted per-session. The same Worker also handles edge auth, rate limiting, and player telemetry collection. Zero cold starts, 330+ cities, V8 isolates instead of Lambda containers.
For every live OptiView stream, instantiate one Durable Object that coordinates: viewer pool size, interactive overlay state (polls, fan reactions), live betting tickers synchronized to the <500ms latency feed, multi-viewer sync across devices, and chat moderation. SQLite-in-DO persists state without an external DB. DO Facets (Agents Week 2026) instantiates these per-entity DOs dynamically — one per VIN for in-car streams, one per NFL+ game, one per Paddy Power race.
Move Dolby's HDR masters, Atmos stem libraries, and OptiView's NFL+/NASCAR/Paddy Power VOD archives to R2. Zero egress fees — a massive shift versus the current S3 + CloudFront bill that compounds every quarter. R2 has S3-compatible API, multi-region replication built-in, and direct integration with Stream for video transcoding. The largest single line-item AWS cost reduction Dolby is likely to see.
SGAI (Server-Guided Ad Insertion) is the new economic engine of live sports streaming. Each ad break is actually a complex pipeline: bid → creative selection → personalization → manifest-stitch → playback verification. Workflows v2 (Agents Week 2026, with waitForEvent) orchestrates this durably across thousands of concurrent breaks. Queues handles fan-out: encoder triggers, CDN purges, analytics pipeline events.
KV for sub-millisecond feature flags & config (already the pattern for Flagship). D1 for per-customer OptiView configuration, multi-region SQLite with read replicas in every viewer's region. Hyperdrive fronts OptiView's existing Postgres without a rewrite — pooled connections, edge query cache, no application changes. Add Vectorize for content discovery (semantic search across NFL+ VOD library, "find me more games like this").
Pages for dashboard.dolby.io and every customer-facing console with per-PR preview URLs, Git integration, and instant rollback. Containers (Cloudflare's new container runtime) for the long-running workloads OptiView needs that don't fit Workers — custom FFmpeg encoders, legacy player SDKs. Realtime / Calls gives OptiView's WebRTC SFU stack a second global footprint with DDoS protection on every ingest endpoint.
waitForEvent for human-in-the-loop steps. No separate service to manage; runs inside the Workers runtime.Andrew Geiser leads the Cloudflare account team for Dolby. Let's spend 30 minutes mapping the highest-leverage 30-day quick wins.