NodeValid

Published video-model weights, licences and hardware notes

Weights questions the repositories themselves settle

A question is answered here when a repository, a licence file or a model card settles it. Anything needing a benchmark run, a particular machine or a lawyer is named and left alone. As of 2026-09-12.

Where a weights question can and cannot be settledA licence file settles what may be done with the files. A model card settles sizes and sometimes hardware. A benchmark run settles speed, and a lawyer settles what a licence means for a particular business. The register answers the first two and names the other two rather than approximating them.What would settle itA file in the repoAnsweredLicence text, a model cardfigure or a release tag,quoted with its address.A machineNamed, not answeredThroughput and memorydepend on a configurationnobody publishes.A lawyerNamed, not answeredWhat a licence permits forone business is not aregister question.Two branches stay open on purpose
Fig. 1 Approximating the right-hand branches is how a register stops being checkable and starts being a rumour with a citation.

Hardware is where the temptation is strongest. Everyone wants to know whether a model runs on a given card, and the honest answer is usually that the repository does not say. Filling that gap with a number from a forum would make this register the source of a claim it cannot support.

Licence questions are the other recurring kind. What a licence permits is often readable; what it means for a particular commercial arrangement is a legal question, and the register marks the boundary rather than crossing it.

The questions that do get answered are the structural ones: which variant the weights belong to, whether the licence covers outputs, whether the released version matches the hosted one. Those decide whether a self-hosted plan is viable at all.

1The questions

  • Two kinds of open — Three families here carry a standard permissive licence.
  • The VRAM ladder — Published hardware figures across these families span a factor of twenty, from a laptop-class card to a rented data-centre one.
  • Naming the card — Two families name the card their figures were measured on.
  • How long a clip — Published lengths run from a few seconds up to sixty, and the repositories state them in different units, so the table carries both.
  • Nobody sells these — Two of the five families here have no counterpart on any priced page in this register, so their cost cannot be compared with anything.
  • Licence vs weights — Both open releases here carry the same permissive licence, so the licence cannot separate them; the version that is published is what does.
  • Which version — Weights exist for two earlier generations of one family, while the generation that hosted services actually sell has none published at all.
  • Running it locally — A 5B model is described as running on a consumer graphics card, with a stated time for producing a five-second clip at 720P.
  • 4090 or 80GB — The same repository names a consumer card for one command and an 80GB floor for others, and both of those figures are correct.
  • Clip length — One repository states support for up to sixty seconds, far longer than any single generation the hosted services in this register sell.
  • Buy or run — Both hosted services here publish per-second rates, but comparing them with local compute means comparing two different versions of the model.

Where a repository is silent, the answer says so and names the file that would have to carry it.

Also in the register: Models, Hosted, Learn, Data. What a release has to publish is set out on the reading page.