Customer login
Your application authenticates the viewer. Login alone does not establish access to every title.
6.0License service
Cloud DRM License Service With Your Access Rules
Keep subscriptions, purchases, rentals, tickets, and course access in your platform. After your backend approves a viewer, DRM-X processes the device license request and applies the selected security, duration, quality, output, offline, and concurrency policies.
01 / DRM-X 6.0
Your platform approves access; DRM-X delivers the license
Entitlement check
Your backend checks subscriptions, purchases, rentals, course enrollment, tickets, or company roles.
DRM License Token
After approval, DRM-X creates bounded playback authorization. Keep Site Key and Access Key credentials on your server.
DRM license
The device submits its native DRM request. DRM-X issues the license under the approved policy, and the device enforces its controls.
02 / DRM-X 6.0
DRM-specific security and download policies
Duration, quality tiers, output protection, and concurrent-stream policies must match each DRM and device. Follow the technology guides for precise behavior.
| DRM | Security policy | Persistent-license scope |
|---|---|---|
| Widevine | Require Widevine L1 and supported output controls when the content policy calls for them. | Supported Android downloads; obtain encrypted media and a persistent device license. |
| PlayReady | Require SL3000 and appropriate output protection on compatible clients. | Offline and embedded projects require separate qualification. |
| FairPlay Streaming | Apply Apple-supported output and license-duration controls for the selected workflow. | Supported iPhone and iPad SDK downloads; current tvOS SDK is streaming-only. |
| WisePlay | Apply supported device-security and output requirements on qualified Huawei devices. | Separate qualification; Android Widevine downloads do not establish WisePlay offline support. |
03 / DRM-X 6.0
Direct license delivery or a customer proxy
Choose the integration mode that fits your application architecture. Neither mode removes the need to protect server credentials and validate viewer access.
Direct delivery
The player sends its authorized DRM request to the DRM-X license route. Your backend still checks viewing access.
Customer proxy
Your backend proxies the authorized license exchange using the documented token-proxy integration. Preserve the native request and response.
04 / DRM-X 6.0
License operations and billing
Usage reporting
Review activity using the selected billing metric: monthly active users or successful license deliveries.
Successful-license billing
Under MAL billing, successful license deliveries count toward usage. Failed license requests are not successful deliveries.
Request diagnostics
Use request identifiers and redacted errors to distinguish access, license, media, and device failures.
Capacity planning
DRM-X operates cloud licensing on AWS. Plan expected audiences, event peaks, regions, and service commitments with our team before launch.
05 / DRM-X 6.0
Content keys and device licenses have different roles
Content keys encrypt and decrypt media. DRM-X protects stored keys and exchanges them with authorized processing services. Device licenses carry the rights and protected key material needed by the DRM system.
Your CDN serves encrypted media independently of license delivery. The player does not receive clear content keys through your application API.
Questions
Common questions
Do I put server credentials in my player?
No. Site Key and Access Key remain on your backend. The client receives only the bounded playback configuration needed for the authorized session.
Does a DRM License Token replace the device license?
No. The token authorizes the exchange. The device must still acquire a native DRM license.
Can a persistent license be revoked immediately offline?
A disconnected device cannot receive a new revocation decision. Set license duration and renewal rules to match your access policy.
Your next step
Start your free first month
Use the relevant guide or contact our team to plan your supported workflow.