NodeValid

Published video-model weights, licences and hardware notes

Open weights versus hosted seconds, read from vendor pages

Each page here takes one search about open weights and reads it the way this register reads a release: whose organisation published the files, under which licence, with what hardware figure, and which version is sold instead. Where nothing is published, that is the finding and it is dated. As of 2026-10-13.

Two columns that only sometimes line upA repository states a licence, a size and sometimes a hardware figure; a price page states a rate and the version it serves. The register keeps the two columns apart because a filled price column says nothing about whether a file exists.A repositoryA price pageWhat it statesLicence, size, sometimes a memory figureA rate per second, and a version nameWhat a buyer getsA file to run and keepSeconds on someone else's hardwareWhen it is silentThe register leaves the cell emptyThe version may have no file at allRead side by side, never merged
Fig. 1 Every page in this column asks the same question first: is there a file, and whose organisation published it.

The searches this column answers all begin with a model name and a hope: that the weights are out, that they run on the card in the machine, that the version in the search is the version with files. The register's habit is to answer each part separately, because the answers keep coming back different. The first page here reads Higgsfield's service pages for what they can state about weights, and finds a price list where a reader expected a repository.

Every page does the same three things. It carries the register's own readings for the families concerned, quoted from the repositories with the dates they were read; it sets the services' own pages beside them, for what a plan or a rate includes and leaves out; and it ends on the cases where the other answer is the better one. A line from the pipeline this register follows, SceneMixer, sits in each service table, so a sold second can be placed against a published file.

What the column will not do is fill a hardware column from a parameter count or a licence column from a brand. Where a repository is silent the cell stays empty and says so, and a version with no published weights is recorded exactly that way — which is, more often than the searches expect, the answer.

1The pages in this column

  • Higgsfield open weights — what a service page can publish and cannot, the five licences the register has read, and the hardware note a licence leaves to the repository.
  • MiniMax H3 weights — what a register of published weights can say about a version it never read, the fields a repository actually states, and the platforms a model-name search lands on instead.
  • Wan 3.0 locally — the gap between a version number and a runnable file, the memory figures other repositories state, and how far a card can be stretched before a service is cheaper.
  • Wan 3.0 weights — the version number the search names, the two versions that really are published, and what a per-second price covers that a file does not.

The register's own readings were taken on 2026-09-22 and the services' pages were read on 2026-10-13. What counts as a published release, and which organisation has to publish it, is set out on the method page; the families themselves are on the Wan page and its neighbours.