Single-key compatibility
Protect one presentation with a shared key model designed for broad four-platform playback.
6.0Content Packaging
Turn encoded media into protected, publish-ready streams.
Create validated DASH/CENC and HLS/CBCS releases for VOD or live delivery using managed workflows, the DRM-X CLI Packager, or CPIX-based integration.
What this gives your businessImmutable protected releases with registered manifests, managed keys, and a Content ID your application can safely reference.DRM-X 6.0 · request-time authorization · protected delivery
Capabilities
Security controls that stay practical to operate.
Quality-tiered keys
Separate AUDIO, SD, HD, and UHD key scopes so stronger devices can receive stronger tiers.
Managed or customer storage
Publish through 1AICLOUD or registered Amazon S3 and Cloudflare R2 destinations.
One-use packaging access
Run the CLI Packager with bounded, short-lived authorization instead of permanent content-key credentials.
How it works
From your source to an authorized screen.
- 01
Prepare encoded input
Supply the bitrate ladder, audio languages, subtitles, and source metadata your service requires.
- 02
Choose the key model
Use Single Key for widest compatibility or Multi-key Quality Tiered for differentiated protection.
- 03
Encrypt and upload
Package CENC and CBCS outputs, validate manifests and segments, and upload only protected delivery artifacts.
- 04
Publish the release
DRM-X registers the authoritative manifest variants and exposes the stable Content ID for playback authorization.
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.
- VOD outputs
- DASH/CENC · HLS/CBCS
- Key exchange
- One-use CPIX packaging session
- Storage
- 1AICLOUD · Amazon S3 · Cloudflare R2
- Release model
- Validated immutable package output with registered manifests
Where it fits
Built around real protected-content businesses.
Fast launch
Use managed packaging and hosting to publish a protected title without building a media-security pipeline first.
Existing cloud workflow
Keep media in registered customer-owned object storage with scoped upload and public delivery boundaries.
Custom media operations
Use the CLI and CPIX contract alongside your encoding, catalog, and publishing orchestration.
Questions
Answers before you integrate.
Does DRM-X accept an arbitrary manifest URL at playback time?
No. Playback resolves a registered manifest from a Published protected file selected by its trusted Content ID.
Should I use single-key or multi-key?
Use single-key when broad compatibility is primary. Use multi-key when HD and UHD tiers require distinct security or output-protection rules.
Can protected output stay in my cloud account?
Yes. Registered Amazon S3 and Cloudflare R2 destinations are supported alongside managed 1AICLOUD hosting.
Protect the next release