The weights that are open are not the ones being sold

NodeValid records which video model weights a vendor has actually released, under what licence and on what hardware. In both families tracked here the published weights are an earlier generation than the version the hosted services bill by the second. As of 2026-09-12.

Inclusion rule. Model families whose vendor has published at least one release openly. Where no hosted service in this register sells a version of the family, the last two columns are recorded as not applicable. Order. Alphabetical by family.

1How this register is laid out

Model pages and hosted pages, kept apart. A model page records what a vendor has released from its own organisations: versions, licence, and any hardware figure the repository itself states. A hosted page records which version a paid service sells and whether weights for that exact version exist in the open.

Keeping them apart matters because the brand is shared and the version numbers are close. Wan 2.2 is open; Wan 3.0 is sold. LTX-Video is open; LTX-2.5 is sold. Reading either pair as one thing turns every cost and quality comparison into a comparison of different models.

2Start here

• Wan — 2.1 and 2.2 published under Apache 2.0; 3.0 is not.
• LTX-Video — 13B with distilled and fp8 variants, Apache 2.0.
• HunyuanVideo — 13B under a licence the vendor wrote itself.
• CogVideoX — one family, two licences, and a 4GB entry point.
• Mochi 1 — Apache 2.0, 10B, an H100 and 480p.
• SceneMixer — sells Wan 3.0 seconds, names the version on its price list.
• LTX Studio — sells LTX-2.5 seconds while its parent publishes LTX-Video.
• Requirements — a 4090 and 80GB of VRAM, both from the same repository.
• How read — vendor organisations only, hardware quoted not derived.
• Two kinds of open — open weights come under two kinds of licence
• The VRAM ladder — from four gigabytes to eighty
• Naming the card — why naming the gpu beats stating a memory figure
• How long a clip — how long a clip each family states
• Nobody sells these — published families that no hosted service names

3Questions the register answers

4Explainers

Craft notes on reading releases: what a licence file governs, and how to read a stated hardware figure. These pages carry no vendor facts of their own — the sourced rows are on the model and hosted pages.

• Reading a licence — what a licence on published weights governs, and what it leaves untouched.
• Planning hardware — how to read a stated VRAM figure, and what it leaves out.

• Two kinds of open — open weights come under two kinds of licence
• The VRAM ladder — from four gigabytes to eighty
• Naming the card — why naming the gpu beats stating a memory figure
• How long a clip — how long a clip each family states
• Nobody sells these — published families that no hosted service names
• Licence vs weights — apache 2.0 on both, and it settles less than it seems
• Which version — the version sold is not the version published
• Running it locally — what the repository says you can run on one card
• 4090 or 80GB — why one repository publishes two hardware answers
• Clip length — how long a clip the published weights can make
• Buy or run — renting seconds against running your own card

5Why a parameter count is not a requirement

The most repeated number about any open model is its parameter count, and it is the one that answers the fewest questions. A 5B model and a 14B model from the same family can need a consumer card and 80GB of VRAM respectively, and the repository says so in both cases. This register quotes those statements and does not estimate anything from size.

The second most repeated number is the licence, and it travels better. Apache 2.0 on both families here means the published releases can be used commercially without asking, which is a real difference from a research-only release and is the reason these two are worth tracking at all. It says nothing about the versions being sold, which carry no public licence because they carry no public weights.

NodeValid records published releases and published rates. It does not benchmark models and it does not recommend running anything locally.