BrandVideoAI

What each vendor's terms say about commercial use

What changes when you run the model yourself

Running published weights removes the plan question and adds three others: which conditions the licence attaches, whether anybody is watching them, and who answers for what the model produces. As of 2026-09-12.

Swapping a subscription for a licence fileSelf-hosting removes the plan question and adds three: which conditions the licence attaches, whether anybody is watching them, and who answers for what the model produces.What changes, in order of how much work it addsThe permissionOften simpler: a named licence answers the question in threewords.The monitoringDelegated: thresholds are measured in your accounts or youranalytics.The obligationsNotices and licence text, which are conditions where adisclaimer depends on compliance.The responsibilityYours, explicitly. No escalation path and no moderation layer.Which is why a self-hosted row belongs in the same register
Fig. 1 A subscription tells you when you crossed a line by charging you. A threshold does not.
What a licence file replaces, and what it hands over. Recorded 2026-09-12.
With a subscriptionWith published weights
A plan decides the permissionA licence file decides it
The supplier sees your usageNobody sees it but you
Support and escalation existNeither, and warranties are disclaimed
Terms change when the supplier saysConditions change with a model release

Inclusion rule. Differences that change how a rights position is maintained rather than what it permits. Order. From what decides the permission to what happens when it changes.

1The permission usually gets simpler and the monitoring does not

A named permissive licence answers the commercial-use question in three words. A community licence answers it with conditions measured in the licensee's own accounts or analytics, which nobody at the publisher can see.

That delegation is the real change. A subscription tells you when you have crossed a line by charging you; a threshold in a licence file tells nobody anything.

2Obligations that look like formalities

Preserving notices and licence text is a condition where an output disclaimer is conditioned on compliance. A pipeline that ships without them has not lost anything and has stopped satisfying the sentence it relies on.

For video that usually means one line in a credits file or a repository note, which is the kind of task that only happens when it is in a checklist.

3Responsibility arrives with the permission

There is no supplier to escalate to when something in the output turns out to be somebody else's, and no moderation layer catching material before it leaves. Several licences say so explicitly.

Which is not an argument against self-hosting. It is the reason a self-hosted row belongs in the same register as a subscription, and the reason its cells record a mechanism rather than a price.

4Where the vendor statements are kept

The mechanics above apply to anyone. What a given vendor has committed to in writing is held on the register instead, each line with the plan page it came from and the date it was checked.

An explainer, not an entry in the register. Vendor statements are held, with their sources, on commercial use, and nothing on this page is legal advice. Related: Consent paperwork, Labels and disclosure.

5What the output is for

Alongside the terms behind “Running weights”, SceneMixer's guides describe the work itself this way:

The script is written from the photos and the one-line description. In step-by-step mode you can rewrite it before anything is shot.

SceneMixer, How to Make an Ad from One Photo — “Do I need a script?” (read 2026-10-13)

On a segment’s card, Insert adds a blank segment right after it: write its header and shots.

SceneMixer, Inserting and Deleting Segments (read 2026-10-13)