6.0Integrate the HTML5 Universal Player, Android SDK, Apple FairPlay development preview, native APIs or CMS packages through one server-side playback-session contract.
Start with your platform. Check the available release and device requirements before integrating.
Add protected playback to supported browsers with one Web Component and a working PHP example.
Read the Web integration guideIntegrate streaming and protected downloads. Try the public evaluation app, then obtain the customer SDK through an eligible Console account.
Read the Android integration guideUse Swift and AVFoundation for iOS, iPadOS and tvOS. The development player shares server authorization, playlist controls and viewing progress.
Read the Apple integration guideConfigure your published Content ID and server credentials, then replace the sample login and entitlement check with your application logic. Playlist and player branding settings are included.
Use automatic DRM selection, playlists, resume, captions, audio tracks and quality controls in supported browsers. Start with a runnable PHP sample.
Use Kotlin, Media3, and MediaDrm for Widevine on supported Android, Android TV, Google TV, and Fire TV devices.
Use Swift and AVContentKeySession for FairPlay certificate, SPC, CKC, renewal and session release. Native player and download refinements remain in development qualification.
Integrate platform DRM APIs, commercial players, WordPress, LearnDash, LearnPress, or Moodle.
Authenticate the viewer and request a DRM-X playback session from your backend.
The client never chooses arbitrary manifest or license URLs and never receives your API credentials.
Load the returned registered manifest and attach authorization only to DRM license and FairPlay certificate requests.
Free the concurrent-stream reservation on stop, replacement, terminal error, and application shutdown.
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.
Start with a complete PHP or ASP.NET Core package and change the clearly marked server-side settings.
Keep entitlement and policy on the backend while native frameworks handle protected media and platform CDMs.
Add protected playback through maintained WordPress and Moodle packages without placing DRM-X credentials in HTML.
Yes. Any compatible EME or native player can consume the Universal Playback Session Contract if it preserves native DRM challenge and response bytes.
Your server selects a named policy template or a complete approved custom policy when it requests the playback session.
The Universal Player detects supported key systems and resolves the correct registered manifest. Windows Edge prefers PlayReady, with bounded Widevine fallback in Auto mode.