ICU Mark, Serve and Trace
Three layers. Adopt them in order, or take the whole stack.
ICU Mark — prepare the title
Takes your master and produces the marked mosaic of the title, verified piece by piece, with the title number carried in the mark.
On your machine. A desktop encoder for your render box. Drop a master in a folder; it renders the marked title, verifies it, and uploads straight to storage. Survives power cuts and resumes.
Managed. Send us the masters; we run the same encoder and return the marked title into your storage.
A master file (ProRes, DNxHR, high-bitrate H.264 or similar). Keep burning in your own logo if you do; the mark is independent of it.
The marked title ready to serve, with its index sidecars and a record file for your archive. Sprites, trailer and poster are produced in the same pass if you want them.
ICU Serve — deliver each viewer their own copy
Serves HLS streams and progressive downloads assembled for the viewer, from an edge network, with the per-viewer combination in both.
You point a hostname (e.g. cdn.yourbrand.com) at ICU.
Your backend mints a playback token for a signed-in member (one line of code; we provide the function in your language).
Your player loads:
https://cdn.yourbrand.com/v/<title>/index.m3u8?token=…Download button: same host,
/dl/<title>.mp4?token=…Members, checkout, billing, player, branding, storage account if you want it in your own name.
Cloudflare's edge network, 300+ cities, so the first byte comes from the data centre nearest the viewer. No origin server of ours to go down; storage and delivery live on the same network.
Byte-range downloads, clip excerpts with a minimum length, stream tokens with expiry, per-title and per-account access logs you can export, cache at the edge so repeated plays do not hit storage.
ICU Trace — read a leak back to the account
Given a leaked clip, identifies the title and the account that received that combination, and reports the odds of a false match.
Upload the clip, or the combination already read from it.
Trace recovers the title from the mark and searches the candidate accounts (everyone who ever received that title, or a narrower list you choose).
You get the account id, the position in the title where the clip starts, how much of the combination matched, and the expected false-match count.
Export an evidence sheet (PDF) for the takedown, the processor or counsel: title, account id, stream date and time, position and length of the matched run, expected false matches, and the account's purchase reference for that title as recorded in your system.
Your staff, from a web dashboard. ICU analysts on request for difficult captures (low light, heavy compression, long re-encode chains) —
What a leak costs you with and without ICU
Integration timeline (typical)
Self-serve dashboard with API keys.
Multi-bitrate ladders.
Automated reading of the combination from an uploaded file.
Takedown partner hand-off: the attribution record goes straight into the notice.