CPIX and SPEKE workflows
Exchange scoped live keys with compatible packaging infrastructure while keeping provider boundaries isolated.
6.0Live DRM
Protect live channels with the same authorization contract as VOD.
Coordinate live packaging, rotating key periods, registered manifests, license renewal, and viewer authorization across supported DRM ecosystems.
What this gives your businessOne live content identity that stays synchronized from encoder key exchange through protected playback and renewal.DRM-X 6.0 · request-time authorization · protected delivery
Capabilities
Security controls that stay practical to operate.
Retained crypto periods
Coordinate key rotation and late join without publishing a KID before every required license provider can resolve it.
Renewable authorization
Set bounded renewal behavior appropriate for long-running channels and refreshed entitlement decisions.
Operational evidence
Trace live session, license, renewal, and release stages through redacted correlation identifiers.
How it works
From your source to an authorized screen.
- 01
Register the live channel
Define its content identity, enabled DRM systems, packaging integration, and delivery destination.
- 02
Exchange and rotate keys
Use bounded CPIX/SPEKE requests and retain the periods required for viewers at the live edge.
- 03
Publish synchronized manifests
Expose only validated protected DASH and HLS outputs whose KIDs are available to every selected provider.
- 04
Authorize each viewer
Create a live playback session, renew it when appropriate, and release its reservation when viewing ends.
Designed for delivery teams
Clear boundaries across the complete workflow.
Your backend remains the authority for purchases, subscriptions, courses, rentals, and user access. DRM-X signs and enforces that decision without putting long-lived credentials in a player or mobile application.
- Playback
- DASH/CENC · HLS/CBCS
- Key exchange
- CPIX · SPEKE-compatible workflows
- Lifecycle
- Start · rotate · renew · stop · failover
- Acceptance
- Encoder restart · late join · blackout · renewal · provider failover
Where it fits
Built around real protected-content businesses.
Sports and ticketed events
Authorize paid viewers while keeping security policy and concurrent-stream control active throughout the event.
24/7 channels
Rotate keys and renew bounded authorization without changing the application’s core playback contract.
Live education
Apply the same enrolled-user and course-access logic used by protected on-demand lessons.
Questions
Answers before you integrate.
Is Live DRM a different client integration?
No. Clients set contentType to live and consume the same playback-session, license, renewal, and release fields.
What must be tested before a live event?
Test encoder restart, key rotation, late join, renewal, entitlement denial, concurrent limits, blackout behavior, and failover on every promised device.
Can a new key be published before providers receive it?
No. DRM-X should not publish a rotating KID until every required license provider can resolve the matching key.
Protect the next release