Pre-publish rights clearance

Catch a rights conflict before it ships — not after legal does.

Before a title goes live on a streaming service, Cleared reads the rights, the avails, and the package, checks your release against the licensing rules, and tells you in one plain sentence whether it can go — and why.

Open the consoleSee how it works

The console is invite-only while we put identity in place.

heldlive decision

The Long QuietThis title isn't cleared for subscription VOD in India on Jun 15 — the SVOD window opens Jul 1.

window_not_openevidence: AV-2
Ad-supported VOD in Canada is clear today.

Rights live in paperwork. Releases happen in a hurry.

Territory, business model, licensing window, language entitlements — the rules that decide whether a title can stream somewhere are scattered across avails records and package manifests, each source spelling things its own way. One mismatch ships content where it isn't licensed. That's a legal and financial problem, and it's usually found too late.

How it works

Three steps, one honest answer.

01

Reads the paperwork

It normalizes your title metadata, rights and avails, and package manifest into one picture — bridging the fact that every source spells the same thing differently (CA, Canada, Can.).

02

Checks the request

For the territory, model, and date you want to publish, it asks: is there an open window that covers this, with the language tracks the release actually needs?

03

Answers plainly — and shows its work

Clear it, hold it, or send it to a person. Every reason points back to the exact record that justifies it. No invented rights.

Three honest answers

It won't pretend to be sure.

Cleared

The window is open, the rights cover it, the tracks exist. Ship it — with the matching avail named.

Held

Something doesn't line up — the window, the model, the territory, a missing track. You get the specific reason, and the nearest compliant alternative.

Needs a person

When the records are ambiguous or contradict each other, it won't guess. It routes to a human with both sources cited — because an agent that always answers is one that's sometimes confidently wrong.

Built to be trusted, and to last.

Every claim cites a record

No decision without a pointer back to the source it came from.

The rules live in your data

Nothing about a territory, model, or date is baked into the code — it reasons over the records you feed it.

The same request, the same answer

Verdicts are deterministic. The wording can breathe; the decision never flickers.

A contract that won't move

As it grows to batches, richer conflicts, and a live catalog, the answer it gives keeps its shape.

Want in?

The console is invite-only while we put identity in place. If you handle rights, avails, or release operations, we'd like to show you.

Request accessI have a code