In a CDN-fronted streaming pipeline, the origin is the place the CDN turns to when its edge does not have the requested file. For VOD, the origin is usually object storage — an S3 bucket or equivalent — with the pre-packaged HLS/DASH artifacts. For live, the origin is the packager output, often fronted by a small caching layer; the packager produces new segments continuously and the origin holds them in a hot store while the CDN fans them out.
Origin scale matters. A live event with 1 million concurrent viewers requesting the same 2-second segment can produce 500,000 requests/second at the moment the segment becomes available. If the CDN has no shield and each POP independently asks origin, that traffic hits origin directly. Origin shielding — a regional intermediate cache that consolidates requests from many POPs into one request per region — keeps origin RPS bounded at hundreds rather than millions.
Origin choices in 2026: AWS MediaPackage and CloudFront for AWS-native pipelines; Wowza, Nimble or Unified Streaming for self-hosted; commercial packagers like AnyOne, EZDRM and Bitmovin for hybrid. The principle is the same: origin should be cheap to read (CDN-friendly cache headers), expensive to write (only the packager writes), and protected by shielding so that read amplification doesn't melt it.
