MK.IO's Multiview architecture combines multiple live feeds into a single composed stream — server-side, in the cloud, with no client changes required. That composed stream still needs to reach 20 million subscribers across North America at the exact moment they open the NCAA tournament or an NFL Sunday. That's where Cloudflare Stream fits.
How MK.IO Works
MK.IO Multiview is explicitly server-side — multiple live feeds are combined into a single stream in the cloud, requiring no changes on set-top boxes or client apps. Cloudflare Stream operates at the next layer: getting that single composed output to every subscriber, globally, without buffering.
Why Stream for MK.IO
At 35K+ live events per year and 20M+ subscribers, the delivery layer is where the subscriber experience is won or lost. These are the specific problems Cloudflare Stream addresses for MK.IO's architecture.
The NAB article specifically called out "hundreds of thousands of Multiview viewing hours within days of launch" for the NCAA tournament. That's a simultaneous surge — millions of Charter subscribers opening the same composed stream within minutes of each other. Without edge caching, every one of those requests hits MK.IO's origin.
HLS segment caching at 330+ edge PoPs. The composed Multiview stream's manifest and video segments are served from the PoP nearest each subscriber — not from MK.IO's cloud origin. Origin only serves unique cache misses. Tournament launch spikes are absorbed at the edge with zero origin load increase.
Charter and Comcast subscribers have entitlements — not every subscriber has access to every sports package. MK.IO's composed Multiview stream needs to be gated so only entitled subscribers can watch. At 20M subscribers, this requires per-token authentication that doesn't add latency to the viewing experience.
Signed URLs with access rules baked into the JWT token. MK.IO's platform generates a signed token per subscriber session — Cloudflare validates it at the edge with no round-trip to origin. Rules can enforce: subscriber tier, geographic restriction, time window, and device type. Zero latency overhead on playback; full entitlement enforcement.
{
"sub": "multiview-nba-stream-id",
"exp": 1748000000,
"kid": "charter-signing-key",
"accessRules": [
{ "type": "ip.geoip.country",
"action": "allow",
"country": ["US"] },
{ "type": "any",
"action": "block" }
]
}MediaKind cited "hundreds of thousands of Multiview viewing hours within days" — that data is the proof point for Charter's investment in MK.IO and for MediaKind's commercial reporting. Accurate, granular per-stream analytics at the delivery layer is critical for operator billing and product development decisions.
Per-stream analytics via the Stream API: viewer count, minutes watched, buffering ratio, geographic distribution, device type breakdown. The same data that powers the "viewing hours" headline is accessible programmatically — MediaKind can surface it in MK.IO's dashboard or pipe it directly to operators like Charter via webhook.
MK.IO delivers 5M+ viewing hours per day. That's multi-terabyte daily egress from the cloud origin. On AWS CloudFront or Azure CDN, outbound data transfer charges compound quickly at this scale. The cost of delivering a composed Multiview stream (larger payload than single-stream) compounds the problem.
Cloudflare Stream charges for encoding and storage, not egress bandwidth. Delivering a stream to 100 subscribers or 100,000 costs the same in egress. For MK.IO's scale — particularly during high-concurrency sports events — eliminating per-GB delivery charges directly reduces the cost of running MK.IO Multiview at operator scale.
Cloudflare Stream
Stream is purpose-built for high-concurrency live events — not general-purpose CDN with video bolted on. The features map directly to MK.IO's operational requirements.
MK.IO's 20M North American subscribers are spread across every market. Cloudflare's anycast network means each subscriber request is answered by the geographically nearest PoP — not routed across the country to a regional CDN cluster. The composed Multiview stream segments are cached globally after the first request per PoP, eliminating origin round-trips for all subsequent viewers in that region.
MK.IO outputs a composed stream. Stream handles ABR delivery — serving each subscriber the highest quality their connection supports, automatically. Charter subscribers on 1Gbps fiber get 1080p; mobile subscribers on LTE get 480p. No manual quality ladder management.
Each playback session gets a signed token generated by MK.IO's platform. The token encodes the subscriber's access rules — content tier, geographic restriction, session window. Cloudflare validates it at the edge. No auth service round-trip, no latency on playback start, full operator entitlement enforcement.
For VOD content alongside live — post-event highlights, on-demand replays of composed Multiview sessions — Stream accepts direct uploads without routing through MK.IO's origin. Signed upload URLs let content flow directly from production to Cloudflare's network.
Stream's HLS delivery is compatible with any player — Comcast X1's native player, Charter's app, third-party OTT players. No SDK changes required. The same stream URL works across every endpoint MK.IO serves without additional player integration work.
Live sports events are high-value attack targets. A Multiview outage during March Madness or an NFL Sunday is front-page news and a direct threat to Charter's subscriber relationship. Cloudflare's unmetered L3/L4 and L7 DDoS protection activates automatically — no bandwidth overage, no manual response required.
The Numbers
Estimates based on published MK.IO metrics and typical sports streaming concurrency patterns. Actual figures depend on MK.IO's specific configuration.
Estimates illustrative. Actual AWS/Azure costs depend on region and commitment tiers. Cloudflare Stream charges per minute of video stored and encoded — not per GB delivered.
Cloudflare Stream integrates at the output of MK.IO's processing pipeline — after the composed Multiview stream leaves MK.IO's cloud, before it reaches Charter and Comcast subscribers. The integration point is a CDN origin configuration, not a platform change.
Happy to run a 20-minute technical walkthrough focused on the specific MK.IO integration: how Stream ingests the composed HLS output, how signed URLs map to MK.IO's subscriber entitlement model, and what the analytics surface looks like for operator reporting.