Product Case Study · Video Security
How I identified and solved the tension between strict studio HDCP enforcement requirements and broadcasters' need to serve every viewer — without forcing a choice between the two.
01 · Problem Statement
Entertainment studios distributing premium content have strict protection requirements. Among them: HDCP (High-bandwidth Digital Content Protection), which enforces that HD content is only played on authorized, compliant devices — and blocks playback entirely on non-compliant ones.
For media broadcasters and OTT platforms, this created a real tension. To work with studio content, they needed to enforce HDCP. But enforcing it strictly meant blocking legitimate viewers on devices that didn't support it — older TVs, certain adapters, non-compliant setups. Blocking those viewers wasn't acceptable; it meant breaking the end-to-end playback experience for a portion of the audience through no fault of their own.
Why it matters: Studios won't license premium content to platforms that can't enforce their protection requirements. At the same time, broadcasters can't build products that arbitrarily fail for segments of their audience. A solution that only serves one side isn't a solution.
02 · How I Identified the Problem
This came out of the deeper market understanding I developed while working on Playback Restrictions. As I dug into what different customer segments needed from content protection, the distinction between entertainment studio requirements and broadcaster needs became clear. Studios operate under content owner agreements that mandate specific protection standards — HDCP enforcement isn't optional for them. But broadcasters care deeply about reach and reliability of playback across all devices.
Understanding both sides of that tension led directly to identifying Fallback HDCP as a gap worth solving — not from a feature request, but from keeping a close picture of how different customers were thinking about the same problem space.
03 · Approach
The key insight was that these two requirements — strict HDCP enforcement for studios, full-audience reach for broadcasters — weren't actually in conflict if the solution was designed correctly. The answer wasn't to choose one over the other; it was to enforce HDCP where the device supports it, and fall back gracefully where it doesn't.
I worked with engineering to define a solution that used multiple DRM keys to unlock different renditions depending on the device's HDCP compliance — giving studios the enforcement they required while giving broadcasters a path to serve every viewer.
04 · Solution
Fallback HDCP lets content owners enforce HDCP for HD playback while automatically falling back to standard definition (SD) for devices that don't support HDCP — ensuring the content is protected at the highest level the device supports, and that playback never fails entirely for a compliant viewer.
Instead of a single DRM key, the player uses a keychain with three keys — one for audio, one for HD, one for SD. The player selects the appropriate key automatically based on device compliance.
For HDCP-enabled devices, the player uses the HD key and serves encrypted HD renditions — meeting full studio protection requirements.
For non-compliant devices, the player falls back to SD renditions with a lower level of protection — preserving playback without violating studio requirements at the HD tier.
05 · Security Levels
| Level | HDCP Enforcement | Devices |
|---|---|---|
| Not required | None | All devices |
| Type 0 | HDCP enforced | All HDCP-compliant devices |
| Type 1 (highest) | HDCP 2.2+ enforced | Latest compliant devices only |
Widevine follows a similar pattern with its own security level tiers. The feature requires DRM to be enabled on the account.
06 · Metrics
Adoption rate among customers with studio licensing requirements
Reduction in playback failures on non-HDCP-compliant devices post-launch
Customer feedback on ability to close studio licensing deals requiring HDCP enforcement
07 · Outcome & Learnings
The feature gave Brightcove customers — particularly media broadcasters working with premium studio content — a credible answer to studio protection requirements without sacrificing audience reach. Platforms could now pursue or maintain studio licensing relationships while continuing to serve all viewers.
Knowing your customer segments deeply reveals where requirements appear to conflict but don't. Studios and broadcasters both had legitimate needs that seemed to pull in opposite directions. The solution came from understanding both well enough to see they weren't incompatible — they just required more nuanced product design.
Platform credibility in regulated markets requires meeting the market's standards, not negotiating around them. HDCP isn't a preference — it's a requirement from content owners. Building a solution that meets that bar expands what customers can do on the platform. Not building it means they build it elsewhere or lose their licensing.