Open-weight model license: verify, don’t assume

In procurement conversations, open weights get treated as three things at once: free to commercialize, permanently available, and independently verifiable. In a single week, the first two were disproved. On 20 September 2026, Alibaba Qwen-Image-2.1 moved from the previous generation Apache 2.0 licence to a research-only grant requiring separate commercial approval. The same day, a mirror site that turns 669,000 Hugging Face models into magnet links reached Hacker News. Our judgment: open weights are not a procurement conclusion but a precondition that has to be verified version by version and file by file. Treating them as a conclusion hands both legal and availability risk to someone else release schedule.

1. Fact one: a licence reversal inside one model family

On 20 September 2026 the Qwen team released Qwen-Image-2.1 as open weights: a 7B visual generation component plus a Qwen3-VL 8B text encoder, native RGBA, 2048 by 2048 output, up to 10 reference images and roughly 33GB for a local install. The parameters are not what procurement and legal need to look at. The licence is. The previous generation shipped under Apache 2.0; this one ships under the Qwen Research License Agreement dated 2026-09-20, restricted to non-commercial use, with commercial use requiring a separate grant. The primary text is the Qwen-Image-2.1 licence, which states FOR NON-COMMERCIAL PURPOSES ONLY and defines non-commercial as research or evaluation purposes only. Reporting matches: The Decoder notes that business users must apply to Qwen for a separate licence.

Our judgment: this is a textbook licence reversal. The damage is not the tightening itself, since publishers are entitled to tighten. The damage is the mismatch with how companies record licences. Most teams file the conclusion at family level, so a new release inherits the old assumption. When terms change per version, the register does not follow.

2. Fact two: availability moves outside any single publisher control

Also on 20 September, pirateface.co reached 88 points on Hacker News. The site converts open models and datasets on Hugging Face into magnet links, checking each file against the official SHA-256 checksum, marking taken-down models as Rescued and letting the swarm keep distributing them. It claims 669,000-plus mirrorable models and rewards seeding with points rather than tokens. Its core claim is that no single host can be shut down. Source: pirateface.co.

The boundary has to be stated: model counts, Rescued status and checksum mechanics are all self-reported and not third-party audited. What does hold is the direction it represents. The open layer enterprises depend on is having its access path moved onto carriers no single publisher controls. For procurement that is both an availability backstop and a new provenance question: once weights come from a mirror rather than the official release page, integrity checking stops being optional.

3. Our judgment: three independent diligence lines

Treating open source as a single procurement conclusion was the most common simplification of the past two years. The correct approach splits it into three lines that do not substitute for each other, each verified and documented separately:

The three lines behave like a weakest-link system. A licence tightening stops a product line, a takedown interrupts service, and an integrity failure makes both of the others meaningless. Miss one and the verification cost spent on the other two is wasted.

4. Procurement checklist: six actions you can take now

5. Conclusion and this month move

Our judgment: the value of open weights is real. It lets capability be self-hosted, independently verified and detached from one vendor price list. But that value only holds once all three lines are verified. Treating open source as a procurement conclusion outsources both legal and availability risk to someone else release schedule.

The smallest useful move this month: tabulate every open weight you run, fill in the licence snapshot, the commercial boundary and the file checksum for each, and attach retrieval dates. At the next procurement review, confirm the grant per version rather than per family. Then answer one question: if the open weights you run switched to a non-commercial licence tomorrow, which product line stops first?

References: Qwen-Image-2.1 licence text huggingface.co/Qwen/Qwen-Image-2.1/blob/main/LICENSE (HTTP 200, primary licence text, FOR NON-COMMERCIAL PURPOSES ONLY) | The Decoder report the-decoder.com report (HTTP 200, business users must apply for a separate licence) | Pirate Face site pirateface.co (HTTP 200, self-reported: 669,000-plus mirrorable models, Rescued status, SHA-256 reconciliation; not third-party audited).