Home / Companies / Cloudflare / Blog / Post Details
Content Deep Dive

Behind the scenes with Stream Live, Cloudflare’s live streaming service

Blog post from Cloudflare

Post Details
Company
Date Published
Author
Kyle Boutette, Jacob Curtis
Word Count
2,150
Company Posts That Month
11
Language
English
Hacker News Points
-
Post removed?
No
Summary

Cloudflare's Stream Live accepts audio/video content from broadcasters and delivers it to viewers around the world in real-time through the Cloudflare network. The service leverages the distributed nature of Cloudflare's network, with ingest and delivery happening at multiple data centers worldwide. Stream Live ingests content using protocols such as RTMPS, SRT, or WHIP, which define how content is packaged and transmitted. Once ingested, content is handled by a Spectrum application that exposes listening ports to specific broadcasters, forwarding connections to an ingest service running on the same server. The ingest service uses Durable Objects to store customer configuration and broadcast state, allowing for geographically distributed broadcasts while maintaining high availability. Content is then delivered to viewers through HLS or DASH playlists, which contain segment metadata for progressive downloading. A Cloudflare Worker called delivery-worker handles all requests for Stream content, rendering playlists and performing various functions. On-the-fly encoding by OTFE (on-the-fly-encoder) service encodes segments in real-time based on viewer request formats, optimizing power and CPU usage. The service is built on top of the Cloudflare network, utilizing tiered caching and request coalescing to support multiple viewers simultaneously.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 7 3,671 840 202 +19%
AI Model Fine-tuning 5 862 147 71 +81%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.