YouTube TV rolls flexible tiers
YouTube TV launched more than ten lower-priced, single-category subscription plans so viewers can buy only sports, news, or family channels — a move that forces real-time entitlement checks and more dynamic stream provisioning reported.
YouTube’s product blog officially introduced a new branded lineup called “YouTube TV Plans” and said it will include more than 10 genre-specific packages, with the announcement posted Feb. 9, 2026. (blog.youtube) YouTube published exact pricing: Sports Plan $64.99/month (or $54.99/month for new users for the first year) and Entertainment Plan $54.99/month (or $44.99/month for new users for the first three months), while the main YouTube TV plan remains $82.99/month. (blog.youtube) YouTube confirmed feature parity across these Plans — unlimited cloud DVR, up to six account members, multiview, and the ability to add existing add‑ons such as NFL Sunday Ticket and 4K Plus. (blog.youtube) Implementing genre-only access requires server-side manifest filtering or per-user manifest generation to exclude streams a subscriber isn’t entitled to, a pattern described in AWS Elemental MediaTailor’s manifest‑filtering documentation for tiered offerings. (docs.aws.amazon.com) Major CDN and edge vendors already expose “manifest personalization” or JIT manifest editing to support those per‑viewer playlists — Akamai’s Adaptive Media Delivery offers manifest personalization and Unified Streaming documents on‑the‑fly manifest edits for just‑in‑time workflows. (techdocs.akamai.com) Streaming vendors warn that manifest personalization and per‑user manifests increase cache fragmentation and reduce standard CDN cacheability, and cloud CDN best practices explicitly advise not to cache user‑specific content unless using specialized query‑forwarding and edge logic. (broadpeak.io) AWS’s integration guides show the operational steps required: CDNs must forward manifest query parameters to MediaPackage/MediaTailor, and provider‑specific setups (including a “manifest bypass” and segment‑caching rules) are recommended to balance personalization and edge caching during the 30–60‑minute configuration process. (docs.aws.amazon.com)