Open weights, open source and free are different promises

Spicy's takeWhen an AI release is called open, separate three questions: what files are available, what you may do with them, and what you need to run them. Treating those as one question makes it too easy to confuse access with permission or convenience. [1][3]

OSI defines weights as learned parameters used with a model architecture. Its Open Source AI Definition 1.0 also calls for code and sufficiently detailed training-data information as part of the preferred form for modification. That is OSI's stated standard; a downloadable checkpoint alone does not demonstrate that every requirement is met. [1]

The Qwen3-8B repository on Hugging Face labels its license Apache 2.0. Its model card supplies loading and serving examples and identifies supported local applications. This gives a reader concrete things to inspect: a particular repository, its terms, and instructions for using that model. [3]

Spicy's takeThat example is not a claim that every Qwen release has identical terms, or that this older model is today's best choice. Check the exact model and version you intend to use. A family name is a starting point for research, not a substitute for reading the relevant release. [3]

Apache 2.0 grants broad copyright permissions subject to its conditions. Redistribution requirements include providing the license, marking modified files and preserving applicable notices; distributions with a NOTICE file have additional attribution requirements. The text also distinguishes copyright permissions from trademark permissions. [2]

Spicy's takeThe same license disclaims warranties and allows providers to charge for support or other accepted obligations. A no-charge license grant therefore should not be read as a promise that a separate hosted product costs nothing or that someone guarantees your results. [2]

Spicy's takeQwen's instructions show software being installed, a model being loaded and an inference server being started. Those steps illustrate why file availability and a ready-to-use service are different offerings. Before switching, investigate the setup and infrastructure your intended deployment actually requires. [3]

Spicy's takeAsk the provider which components are released and where their terms are published. Then ask what remains outside the download: training information, a hosted interface, support, or an operating service. These are suggested purchasing questions, not a finding that any named provider withholds a particular component. [1][2]

Spicy's takeUse the label as an invitation to inspect, not the end of the inspection. Downloadability answers an access question. The license answers permission questions. Deployment instructions help you investigate the work involved. None of these, by itself, establishes which model will perform best for you. [1][2][3]