DRM-X 6.0 dove and olive branch logoDRM-X 6.0Docs

Live DRM integration

Integrate DRM-X 6.0 Live DRM with CPIX or SPEKE packaging, rotating crypto periods, synchronized manifests, renewable authorization, and multi-platform testing.

View MarkdownLive examples ↗Updated 2026-09-05
Your backend decides access; DRM-X enforces the signed policy. Encrypted media and DRM licenses follow separate delivery paths.
Your backend decides access; DRM-X enforces the signed policy. Encrypted media and DRM licenses follow separate delivery paths.

Provision the channel#

  1. Create the live content identity and enabled DRM systems.
  2. Configure compatible CPIX or SPEKE key exchange with bounded authentication.
  3. Set the protected DASH and HLS delivery destinations.
  4. Choose the server-owned live license policy, renewal window, quality, and output controls.
  5. Qualify a complete rehearsal before selling or opening access.

Rotate without creating an unavailable KID#

The packager, manifest, and every required DRM provider must agree on the current and retained key periods. Do not publish a new KID until each selected provider can resolve the matching key. Retain enough prior periods for late join, latency, and controlled recovery.

Create the viewer session#

Request contentType: live after your backend approves the viewer. Return the registered live manifest, license details, renewal behavior, and release lifecycle with Cache-Control: no-store. Use a fresh session ID for each viewing attempt.

Pre-event acceptance matrix#

ScenarioRequired result
Late join during rotationManifest KID resolves and playback begins within the target start time.
Encoder restartChannel recovers without key disclosure or clear fallback.
License renewalAuthorized viewer continues; expired entitlement fails closed.
Provider or network failureBounded retry/failover preserves policy and avoids duplicate billing.
Viewer stopsConcurrent reservation is released promptly.