NodeValid

Published video-model weights, licences and hardware notes

Apache 2.0 on both, and it settles less than it seems

The two weight releases compared on this page are both Apache 2.0. A permissive licence on both means the licence column cannot distinguish them, and the question that does is which version the weights correspond to. As of 2026-09-12.

What a permissive licence settles and what it leaves openBoth published weight releases in this register carry the same permissive licence, so the licence column cannot tell them apart. The question that does distinguish them is which version the weights correspond to, and whether that version is the one being sold.Apache 2.0 on both releasesSettlesThe legal questionTerms a reader alreadyknows, with nothing tonegotiate.Does not settleWhich version this isWhether the weights matchanything on sale.Does not settleWhether anyone supportsitA licence says nothingabout publishing behaviourafterwards.Same licence, different publishing behaviour
Fig. 1 When a column holds the same value for everything in it, the column has stopped being a way to choose. This one has.
The licence attached to each published weight release. Recorded 2026-09-12.
ItemWhat is publishedDetail
WanApache 2.0Stated in the repository
LTX-VideoApache 2.0Stated in the repository
The distinguishing fieldWhich version is publishedNot the licence

Inclusion rule. Licences stated in the vendor's own repository. A licence named in press coverage is not recorded. Order. The two published families first, then the field that separates them.

1A permissive licence answers the legal question and not the practical one

Apache 2.0 settles whether weights can be used commercially, modified and redistributed. It says nothing about whether the published version is the one anybody is actually selling, which is the question a team comparing a local deployment against an API needs answered.

Both entries on this page clear the licence bar identically. Everything that differentiates them sits in the other columns, and a reader who stops at the licence has learned the least discriminating fact on the page.

2Same licence, different publishing behaviour

One vendor publishes weights for two earlier generations while selling a newer one. The other publishes an open model under one name and sells a differently named product. Both are consistent with Apache 2.0 and they are quite different positions for a buyer.

The register keeps licence and version as separate columns because they move independently, and because the licence is the field most likely to be quoted on its own.

3What a licence cannot tell you about support

Permissive terms carry no obligation to keep publishing, to document, or to answer anything. A repository can go quiet while the licence on the last release stays valid forever, and the weights already downloaded keep working.

That is a real form of durability and it is worth saying plainly: an open release is not maintained because it is open, it is merely still usable.

4Open weights, hosted

Instead of local hardware for “Licence vs weights”, SceneMixer runs hosted models; its guides describe the result:

A short drama episode has two jobs: stop the scroll in its first seconds, and make the next episode feel necessary in its last.

SceneMixer, Writing Hooks and Cliffhangers Into a Short Drama Script (read 2026-10-13)

The Seedance 2.0 tiers render segments up to 15 seconds; use a Seedance 2.5 or Wan tier for 30-second takes.

SceneMixer, Seedance 2.0 Fast — “Does Fast render 30-second takes?” (read 2026-10-13)

5Sources

Repository statements and hosted rates are linked from the model pages and the method page, checked 2026-09-12. Hardware figures are set out on requirements. Nearby: Which version, Running it locally, 4090 or 80GB.