Support · Qwen
Will it last?
Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 67.6/100
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
Which domain expands which factor
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Common problems & fixes
Common pitfalls from the model cards and ecosystem are out-of-memory errors on the large variants (235B MoE, 480B-Coder), chat-template or thinking-mode mismatch, and checksum drift across hubs.
Quantise or add GPUs for the first. Apply the tokenizer's chat template and choose thinking or non-thinking mode explicitly for the second. Verify that Hugging Face and ModelScope weights match and pin the revision for the third. The list is a starting catalogue.
Versions, changelog & cadence
Qwen ships on a rapid generational cadence (Qwen3 dense, MoE and Coder lines), tracked as immutable revisions on the verified Qwen org across Hugging Face and ModelScope. Pin a specific revision for reproducibility.
Support is community-driven: Qwen Hugging Face and ModelScope org discussions, plus a broad presence across serving-stack ecosystems (Ollama, vLLM). No enterprise support desk is documented for the open weights.
Tracked known issues
Known issues are China-aligned topic censorship, lighter safety coverage than at frontier labs, and an unclosed EU Article 55 gap on the largest (systemic-risk) variants.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
2
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
WeakThe weights are held but cannot be inspected: training data and code are closed and China-aligned topic censorship is built into behaviour, so sensitive-topic coverage is distorted in ways that cannot be audited. On the hosted path, the binding Alibaba Cloud Product Terms (Sec 4.48, updated 19 Oct 2026) say Alibaba Cloud 'will not use your Member Content to develop or improve the models on Model Studio, unless you separately provide your consent'. The FAQ repeats a softer 'never uses your data for model training'. The Terms state no retention period, storage region or opt-out mechanism.
How this scores (AOI sub-dimensions)
Provenance3/5how well we can trace and verify what went into the modelThe Qwen org on Hugging Face is verified, the models are also officially published on ModelScope, and checkpoints are safetensors with checksums and no canonical-org malicious incident (checklist 5/8).
Governance3/5how accountable and well-documented the publisher isAlibaba's Qwen team is an active, accountable publisher with a rapid release cadence and a verified presence on two hubs.
What this means for adoptionQwen is partly owned. The Apache-licensed mainstream Qwen3 sizes can be run, modified and self-hosted, they perform strongly (especially at coding), and self-hosted data stays on the deployer's infrastructure. Two things cap ownership at partial. First, the licence is per checkpoint: Apache-2.0 on mainstream Qwen3, but the legacy and large Tongyi Qianwen checkpoints (Qwen-72B, Qwen2.5-72B-Instruct) carry a >100M-MAU trigger and 'Built with Qwen' attribution, so verify the LICENSE on the exact checkpoint. Second, transparency is weak: China-aligned censorship is built in and training is closed. The hosted path carries a binding no-training-without-consent term (Alibaba Cloud Product Terms Sec 4.48) alongside a privacy policy that documents Singapore storage, SCC/DPF transfers and retention, but no document gives an exact retention period, a Model Studio storage region or an opt-out. Adopt with hard limits: keep politically sensitive and regulated workloads off it, confirm the per-checkpoint licence, and close the Article 55 gap yourself if a systemic-risk-scale variant goes on the EU market.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.
Model cardread2026-11-19
Qwen3 checkpoints are hosted on the verified Qwen org on Hugging Face in safetensors with checksums.
Licenceread2026-11-19
Mainstream Qwen3 checkpoints are released under Apache-2.0 with unconditional commercial use and no monthly-active-user clause.
Licenceread2026-11-19
Legacy and large Tongyi Qianwen checkpoints (Qwen-72B, Qwen2.5-72B-Instruct) are not Apache-2.0.
Technical_reportread2026-11-19
The Qwen3 Technical Report (arXiv 2505.09388) documents the Qwen3 family, thinking/non-thinking modes, thinking budget and multilingual coverage (~119 languages).
Privacy Policyread2026-11-19
The general Alibaba Cloud International Website Privacy Policy (Last Updated 4 Sep 2026) ties retention to "ongoing legitimate business need" (Sec F).
Documentationread2026-11-19
The Alibaba Cloud Model Studio FAQ states: "Alibaba Cloud strictly protects data privacy and never uses your data for model training." All data transmitted "is encrypted with AES-256".
Terms of serviceread2026-11-19
Alibaba Cloud International Website Product Terms of Service (Last Updated 19 Oct 2026), Sec 4.48 Model Studio, treat Input and Output as "Member Content" processed "for your purposes and on your behalf".
Model cardread2026-11-19
Qwen is also officially published on Alibaba's ModelScope hub (dual distribution).
Third-party analysisunverified2026-07-25
No public EU AI Act training-content summary, copyright policy, or Article 55 documentation for the systemic-risk large variants.
Third-party analysisunverified2026-07-25
Qwen instruct variants are safety-tuned but with lighter alignment coverage than Western frontier labs.
Third-party analysisunverified2026-07-25
Qwen models exhibit topic censorship aligned with Chinese content rules.
Third-party analysisunverified2026-07-25
Qwen3-Coder is among the strongest open coding models on independent evaluation.
Third-party analysisunverified2026-07-25
Qwen is broadly supported across serving stacks (vLLM, llama.cpp, Ollama, TGI, MLX) with many community quants.