DRM video protection for your streaming service

Every title in the Flicknexs admin carries access rules: which subscription plans include it, whether it is sold per view, how many free-preview minutes a visitor gets, and which countries are blocked or allowed. When a viewer presses play, the platform checks the account against those rules first. A viewer who fails the check never receives a playback URL, so there is nothing to copy. This is the cheapest and most effective layer, and it is on every plan.

With the signed-URL flag turned on in storage settings, the platform issues a playback URL that carries a signature and an expiry. The time-to-live is a number you set. After it passes, the same link returns a refusal from the delivery layer. A viewer who copies the link out of the browser and pastes it into a forum has handed out something that dies in minutes, not a permanent door into your library.

The platform looks up the viewer country from the request IP through a geolocation service and compares it with the platform-wide block list or allow list, then with the per-title lists on that video, series or audio item. A blocked viewer gets a refusal message rather than a stream. Rights holders who license by territory usually accept this as the enforcement they asked for, provided you also explain the VPN limit covered further down.

In player settings you upload a logo, choose a corner or center position, set its opacity and add a link. The player draws it over the video on web and in the apps. It is a visible brand mark, not an invisible per-viewer identifier, so it does not tell you which subscriber recorded a clip. What it does is make a recording obviously yours when it turns up on a social feed, which is what takedown requests need.

Transcoding produces an adaptive-bitrate HLS output with a master playlist listing each rendition. The player picks a rendition to match the connection. When encryption is arranged for a title, the delivery layer encrypts those same segments and points the player at a license server for Widevine, FairPlay or PlayReady. Because HLS is already the platform format, adding the encrypted variant does not change how you upload or publish.

The Flicknexs platform code does not contain a license server, key management or content decryption module integration. For customers on an enterprise plan whose contracts require encryption, Flicknexs arranges DRM through the delivery layer on request. The scoping covers which titles, which key systems, which of your apps must play them and the license terms of the DRM providers. Until that scoping is agreed, no title is encrypted, and the page will never tell you otherwise.

There is no license server, key management or decryption module in the Flicknexs codebase. Encryption with Widevine, FairPlay and PlayReady is arranged through the delivery layer on request as part of an enterprise plan, and it is scoped and quoted per customer. Pages or salespeople who tell you otherwise are wrong. Operators on F1 through F3 get the signed-URL, geo-fencing, access-rule and watermark layers; encryption is an enterprise conversation.

The overlay is your brand mark with a position, opacity and link. It is the same for every viewer. It does not embed a per-session code, so it cannot tell you which account leaked a recording, and Flicknexs does not describe it as a forensic mark. If a studio contract demands per-viewer marking, raise that in the same enterprise scoping conversation as encryption, because it is a delivery-layer capability, not a platform feature.

Encryption stops the file from being decrypted outside a licensed player. It does not stop a phone pointed at a television, and on lower security levels it may not stop a capture card between a set-top box and the screen. Signed URLs and geo-fencing narrow who can press play. None of these layers make piracy impossible; they make it slower, riskier and easier to take down.

The country check uses the request IP. A viewer on a VPN that exits inside an allowed country will pass. Rules are per platform and per title only; there is no separate rule set per device app, so a country blocked on web is blocked on Android TV too. Most license contracts accept IP-based enforcement as commercially reasonable, but read your clause before promising more.

Hotlink protection is configured at the delivery layer rather than from the admin, so it is set up on request. Every domain and app that should play your video must be on the approved list, and a new marketing microsite that embeds the player will fail until it is added. Keep the list in your launch runbook alongside the DNS records.