The rows that publish weights instead of plans
Three rows in this register have no plans at all. They publish model weights with a licence, so the question this grid asks is answered by a document rather than by a subscription, and the conditions sit inside that document. As of 2026-09-12.
| Vendor | The licence published | The condition attached |
|---|---|---|
| Wan | Apache 2.0 on the models in the repository | None on this point |
| HunyuanVideo | A community licence with a defined territory | Geography, and a user ceiling |
| Stable Video Diffusion | A community licence agreement | Annual revenue above a stated figure |
Inclusion rule. Vendors that publish model weights with a licence and no hosted plans, read from the licence or repository note itself. Order. By how much the licence attaches: none, then two conditions, then one.
1Why a self-hosted row belongs in a register about plans
Because the question is identical. A brand asking whether it may run generated video commercially does not care whether the answer arrives as a subscription tier or as a file in a repository.
What changes is who carries the work. A licence hands over the permission and the operational burden together, and the burden does not come with a support contract or somebody to escalate to.
2One of the three attaches nothing
A named permissive licence answers the commercial-use question without mentioning commerce: use, modification and distribution are permitted, and the text has been read by every legal team that has looked at open source.
The other two are the supplier's own documents wearing a similar shape. The name tells a reader nothing about what is inside, so each has to be read in full and re-read when a new model release ships a new file.
3What the conditions have in common
They are facts about the licensee rather than about the product: where it is established, how many people use what it builds, what it turns over. None of them is visible to the vendor.
That is the recurring shape of a weights licence. The grant is generous and the monitoring is delegated, which suits a large engineering team and surprises a marketing department.
- LicenceThe models in this repository are licensed under the Apache 2.0 Licensepublished with the weights
- Shape of the grantThe grant is a non-exclusive, non-transferable and royalty-free limited licenceno plan involved
- ThresholdThe community licence covers commercial use until the licensee has more than USD $1,000,000 in annual revenuestated as annual revenue
- Where the licence appliesTerritory is defined as the worldwide territory, excluding the territory of the European Union, United Kingdom and South Koreaa geographic carve-out
4What the output is for
Alongside the terms behind “Weights, not plans”, SceneMixer's guides describe the work itself this way:
You can recomposite with different end-card text, and in step-by-step mode you can reshoot individual segments. The finished file can also be downloaded and shared with a link.
SceneMixer, How to Make an Ad from One Photo — “Can I change the ad after it is finished?” (read 2026-10-13)
The final cut ends on an end card: your main image plus four lines — Brand, Product name, Tagline, Call to action. The first two are read from your photo and your brief; the tagline and call to action are written with the script.
SceneMixer, The End Card (read 2026-10-13)
5Sources
Each row quotes a plan card or a terms page, gathered on commercial use and read 2026-09-12. The test a sentence has to pass before it counts as a licence statement is set out on the reading page. Nothing here is legal advice. Nearby: Free and granted, Where it is filed, Consent records.