Haihaisoft Releases
DRM-X 6.0 Beta

THE RELEASE

Protect the value of every stream.

Haihaisoft announces the availability of DRM-X 6.0 Beta, a Multi-DRM platform supporting Google Widevine, Apple FairPlay Streaming, Microsoft PlayReady, and Huawei WisePlay for protected video delivery across supported browsers, mobile devices, and TV applications.

The platform connects video encoding and DRM packaging with protected cloud storage, viewer authorization, license delivery, and playback controls. Content owners can build video-on-demand (VOD) services and live streaming experiences while keeping their existing customer accounts, subscriptions, purchases, and course-access rules.

For broadcasters, online education providers, OTT streaming services, and enterprise media teams, the objective is practical: protect premium content, reduce unauthorized access and account sharing, and support the revenue that makes continued creation possible.

01 / MULTI-DRM COVERAGE

Widevine, FairPlay, PlayReady, WisePlay.
Connected through one platform.

A single DRM technology cannot cover every viewing environment. DRM-X 6.0 brings four DRM ecosystems into a shared workflow, so application teams can use consistent business authorization while each supported device receives its native DRM license.

DRM-X uses a stable Content ID to connect a title to its registered protected packages. The playback workflow resolves the appropriate manifest and license route for the supported DRM system. This helps teams maintain a common content catalog across web, mobile, and TV applications.

02 / SECURITY THAT MATCHES YOUR RIGHTS

Strong hardware protection.
Flexible software compatibility.

DRM-X 6.0 lets content owners choose the strongest supported protection appropriate to their content rights and intended audience. Hardware-level DRM is available on compatible playback paths, while software-level DRM can extend device reach when the content owner's policy permits it.

Single-key and multi-key packaging support different business needs. A single-key presentation simplifies compatible playback. Quality-tiered multi-key packaging separates audio, SD, HD, and UHD keys so premium video tracks can carry stronger requirements.

For example, a service can permit SD playback on an approved software DRM path while requiring hardware-backed protection and suitable output controls for UHD. A device that cannot satisfy the required policy does not automatically receive access to the stronger tier.

• Short-lived DRM License Tokens: bind playback authorization to a trusted, server-approved request.
• Concurrent stream controls: reserve, renew, and release sessions to help limit account sharing.
• License and playback restrictions: apply permitted durations, quality ceilings, and output policies on supported DRM paths.
• Protected key management: keep content keys and provider credentials within controlled server-side services.
• Account and administrative controls: support MFA, scoped permissions, and auditable security events.

Security and compatibility depend on the actual device, operating system, codec, player, DRM implementation, and selected policy. DRM-X security controls are described as ISO 27001-aligned; this is not a claim of accredited certification. Read the security overview.

03 / FROM SOURCE VIDEO TO PROTECTED PLAYBACK

Automate batch encoding, packaging, and uploading.

The DRM-X Packager Suite helps content teams process video collections through a repeatable publishing workflow. The Windows desktop application combines batch processing and per-file progress with a command-line engine for scripted operations.

1. Analyze the source. Inspect input video and choose suitable output settings, including quality levels that do not upscale beyond the source.
2. Encode for adaptive streaming. Prepare multiple quality levels so a compatible player can adapt to viewing conditions within the permitted policy.
3. Encrypt and package. Create protected MPEG-DASH/CENC and HLS/CBCS output with the selected key model.
4. Verify the package. Check manifests and generated delivery artifacts before publishing.
5. Upload to your destination. Transfer protected files to a registered managed or customer-owned storage connection.
6. Publish for authorized playback. Register the release and connect its Content ID to your application.

Teams can process common source formats such as MP4, MOV, M4V, MKV, and WebM. Desktop batches are useful for operators preparing content libraries; the CLI supports teams connecting encoding and publishing to their existing production processes. See the DRM packaging documentation.

04 / CLOUD STORAGE & DELIVERY

Choose your cloud.
Keep a consistent protection workflow.

DRM-X 6.0 supports 1AICLOUD, Amazon S3, Cloudflare R2, and other compatible S3 storage services. Start with managed hosting or connect your existing cloud account and delivery infrastructure.

1AICLOUDManaged hosting Amazon S3Your AWS storage Cloudflare R2Your Cloudflare storage

Storage delivers the encrypted media; the DRM license service controls authorized playback. This separation helps businesses keep the cloud arrangement that suits their operations while applying a consistent access policy. Optional 1AICLOUD hosting and streaming are priced separately from DRM licensing.

05 / LIVE BROADCAST PROTECTION

Live DRM, connected to AWS.

DRM-X 6.0 integrates with AWS Elemental MediaLive, AWS Elemental MediaPackage v2, and Amazon CloudFront to support protected live channels and events. The workflow uses SPEKE 2.0 for DRM key exchange between compatible packaging infrastructure and DRM-X.

Live encodingMediaLive

DRM packagingMediaPackage v2

Global deliveryCloudFront

The current AWS integration uses Widevine for protected DASH, FairPlay for protected HLS, and PlayReady for protected DASH. The broader platform's four-DRM support does not mean that every DRM is available in every live packaging configuration.

Live capabilities include encryption-key rotation, retained key periods for supported viewing windows, renewable authorization, and concurrent stream controls. These support use cases such as subscription broadcasts, ticketed sports and entertainment, virtual conferences, and live education.

Your application remains the authority for event admission, subscription status, or course enrollment. Before an event, the beta evaluation should include real-device playback, late joining, license renewal, key rotation, and encoder restart. Read the Live DRM integration guide.

06 / BUILT TO FIT YOUR APPLICATION

Integrate across platforms and programming languages.

DRM-X 6.0 provides a common playback-session API alongside players, SDKs, examples, and integration guides. Your backend checks access; the browser or native player handles the appropriate protected playback flow.

Protected offline playback on Android

The Android SDK preview supports Widevine offline playback on supported devices when both encrypted media and the required persistent license are available. License duration and offline rights remain policy-controlled. Android SDK downloads are available to eligible Professional and Enterprise accounts; customers integrate the production download lifecycle into their own applications.

For learning platforms, enrollment and course-access checks can remain in the LMS. For OTT and subscription services, customer identity and payment entitlements remain in the existing backend. Long-lived DRM-X credentials stay on the server. Explore the integration overview and backend language examples.

07 / DAY-TO-DAY OPERATIONS

See your content, policies,
and usage in one console.

The customer console brings together protected content, packaging, storage connections, live channels, key and license policies, users and devices, and license activity. Teams can investigate playback behavior and manage delivery without maintaining separate customer workflows for each DRM provider.

Usage and billing views show monthly active users (MAU), successful license deliveries, included allowances, excess quantities, and calculated overage estimates. Published pricing explains the applicable usage bands, helping customers understand how license demand changes as their audience grows. See DRM-X 6.0 plans and usage pricing.

Customers can enable multi-factor authentication for additional account protection. Customers who have not enabled MFA receive a reminder after each new login and may skip it for that session.