Axinom DRM - FAQ
Axinom DRM is Axinom’s highly robust multi-DRM solution that enables customers to leverage leading DRM technologies with ease by using a unified API. It supports Microsoft PlayReady, Google Widevine, and Apple FairPlay Streaming. Axinom DRM can operate in the cloud, on-premises and even on board of vessels while being completely disconnected from the internet.
Axinom DRM features two core products:
Axinom DRM Licensing Service:
The licensing service enables secure creation and delivery of licenses to consumer devices. It features a comprehensive API that makes integration with existing websites/portals an efficient and hassle-free process.
Axinom Key Service:
Axinom Key Service is a cloud-hosted solution that is able to securely store encryption keys. It comes with APIs that allow the integration with modern encoders/packagers which request encryption keys from Axinom Key Service.
There are many things to consider when rolling out an online video solution with DRM.
The advantages of using multiple DRM technologies simultaneously are:
Broadest reach – supporting multiple DRM technologies allows you to reach a broader set of device types
Provide the best user experience by using the natively supported DRM technology
Avoid client-side licensing fees
Support native and web-based solutions
The disadvantages of using just one DRM technology:
Potentially expensive, because it is necessary to license client-side DRM technology and bring it to the device types where it is not supported natively (if at all possible)
Web-based solutions will be very limited, because browsers differ very much in terms of DRM technology support
For more information, we recommend reading our white paper
The cloud-hosted Axinom DRM license service allows for generating licenses that enable end users to consume protected content. The service comes with an extensive API that enables efficient integration with existing websites and online portals. It is accompanied by a set of tools that make adoption easy:
Yes. Axinom has all the needed relationships with the respective DRM technology vendors.
Yes. Axinom DRM is built on leading DRM technologies (Microsoft PlayReady, Google Widevine, Apple FairPlay Streaming) which have earned full trust from all major players.
Yes. Axinom DRM leverages leading DRM technologies with an impressive track record. PlayReady, Widevine, and FairPlay Streaming feature built-in security on many levels and come with sophisticated anti-tamper technology. Your content is persistently encrypted with state-of-the-art AES encryption technology prior to transferring it. Anyone “stealing” such content will not be able to consume it without the necessary decryption keys.
Axinom DRM allows protecting audio/video content. You cannot use it for other file types, such as PDF documents.
Yes. Axinom DRM supports several DRM technologies simultaneously. This allows our customers to reach broad audiences on all sorts of mobile device platforms like iOS (iPhone, iPad, iPod), Android, Windows, and browser-based solutions.
It is licensed as a SaaS (cloud-based) or as a software product.
The most common licensing option is using our cloud-based service. The cloud-based license delivery service allows you to build, deploy, and run end-to-end DRM solutions without the need and complexity of entering into, potentially expensive, agreements with DRM technology vendors. You just pay based on the number of licenses issued by your application. We take care of paying the applicable DRM technology license fees.
Alternatively, you may license our software and run it on your own servers.
See also: Axinom DRM Billing Models
Yes. We offer a free trial of 30 days during which you have access to our test environment, sample code, comprehensive documentation and support.
You could customize it with the Entitlement Message by applying different policies with different Widevine device security levels to different keys. As L3 is the default, you can keep the default Widevine device security level for keys associated with L3 quality levels. Alternatively, you can explicitly specify L3 for reasons of clarity. For the keys that require a security level higher than L3, you need to specify it explicitly.
Our cloud-hosted service runs in a load-balanced environment and is built to scale on demand. It is performance-optimized on several levels, reducing the round-trip time for acquiring licenses to a minimum, thus guaranteeing the best possible end user experience. Axinom DRM scales without limits. We even offer service capacity guarantees that you can take an advantage of. Doesn’t matter whether you need our service to deliver peak loads of 100, 1 000, 10,000, or more licenses per second – Axinom DRM can handle the load.
Check Delivering 100000 DRM Licenses Per Second article
A “license” means a relatively small data packet that is needed to view/play the content. It contains the key for decrypting the content, accompanied by rules that apply for that content. For example, a license could tell the player to limit playback to a certain time frame or a certain number of views. Using our API, you can configure the restrictions that you want to apply to your content.
See also: DRM Introduction
Axinom DRM is intended as a DRM solution for video content. However, its components - Key Service and License Service - are agnostic to the type of clients and content. Audio streams included as audio tracks together with a video can be protected without any issues. This applies to all DRM technologies that we provide: Widevine, PlayReady, and FairPlay.
In case of pure audio files to which you would like to apply a typical video DRM solution, simulate them to be videos. For example, you can generate a dummy video of the same length as your audio, consisting the standard video settings. Then encode it as if it were a regular video. Note that your player should be built in a way that it would not display the video stream and would only play audio.
For encoding, you can use Axinom Encoding or any other encoding software, e.g. Shaka Packager.
We are interested in user-specific, device-specific, location-specific, and time-specific restriction of playback. Does Axinom DRM support any of these?
All of these are supported. See Entitlement Message for details.
We are required to enforce output protection levels (OPL) when our content is played. Does Axinom DRM support this?
Yes. However, support for output protection differs between DRM technologies (PlayReady, Widevine, FairPlay Streaming). Using Axinom DRM, you can apply simple output protection across all technologies or address each technology separately and use it to its full extent.
Yes. Axinom DRM can be used with virtually all DRM-capable players available. The decisive factor is the respective platform’s DRM support. For example, the Google Chrome browser supports Widevine DRM on Windows and Mac OS, whereas Microsoft Internet Explorer and Edge browsers support PlayReady on Windows. See an overview of DRM technologies supported by different platforms in the DRM Introduction
Widevine can also be used on iOS using iOS Widevine CDM.
Check video players for more information.
Yes. Set-top box and Connected TV manufacturers integrate support for DRM technologies into their devices more and more. The vast majority of devices support either Microsoft PlayReady or Google Widevine.
Generally, yes. Our iOS and Android based players support download of DRM protected assets and offline playback. Our HTML5/JS based players will support this feature when the underlying browsers support it. At the point of writing this, it is not yet the case. However, support for offline playback is in the making at some browser manufacturers.
Yes. Axinom DRM does not impose restrictions on the use of 3rd party players. Check out our 3rd party player page. Among the players/SDKs we successfully tested are
There is no restriction regarding the technology you use for your backend/portal. Any technology capable of consuming Web services (such as PHP, Java, ASP.NET, node.js, etc.) can be used to integrate with Axinom DRM.
Axinom DRM supports Microsoft PlayReady, Google Widevine, and Apple FairPlay Streaming. Using these three trusted DRM technologies, our customers can reach an extremely broad set of client devices.
Axinom DRM can be used in conjunction with MPEG-DASH, CMAF, HLS, and Smooth Streaming.
We have a large Video portal up and running, but currently with no DRM. Can we integrate Axinom DRM into our existing infrastructure? How?
Yes. Our cloud-based Axinom DRM platform features a rich Web services API that can be used by any website or portal to create license rules. A typical workflow could look like this (many other possibilities exist):
For the description below, it is assumed that the content is already encrypted and published to some media server or CDN.
Step 1: The user navigates the customer app/website and decides to watch some content. The user clicks the “Play” button.
Step 2: The web portal/app backend processes the request and verifies the eligibility of the request. If the verification is successful, the web portal/app backend creates an Axinom DRM message that describes the usage rights for this particular request. It encrypts and signs the message and passes it to the requesting client device.
Step 3: The player application on the client device starts downloading the DRM-protected video. It determines the license acquisition URL (this information is typically contained in the asset manifest) and prepares a license request. It sends the license request together with the Axinom DRM message to the Axinom DRM license service.
Step 4: Axinom DRM license service receives the license request, verifies the integrity, and analyses the Axinom DRM message and prepares a respective license response which it sends to the requesting device.
Step 5: The player continues downloading and starts decryption and playback of the video.
If you receive the error "The request data does not represent a valid Widevine request" when using Axinom DRM with Widevine in the proxy mode, the request body might be transformed. Double check whether the proxy or some other component is doing the transformation. Try remove or bypass the proxy and see whether you get the same result. If the result is still the same, please contact product support for further help.