After Llama, Mistral, and DeepSeek, Qwen (Tongyi Qianwen) is Alibaba’s major open LLM family—and Alibaba Cloud is how many enterprises consume it as Model Studio / DashScope APIs. Vol. 11.5 Qwen covered the lineage (dense + MoE, multilingual, VL/audio siblings). This card is vendor choice: download Qwen vs call Alibaba Cloud vs call a Western host of the same weights.
Qwen is often the default when the product is CJK-heavy, needs a wide size ladder (edge → server), or already runs on Alibaba Cloud. Same geopolitical/data-path diligence as DeepSeek applies for some Vol. 21 verticals. Module 22.1 then closes with Microsoft Phi + Copilot—SLMs and the Copilot distribution machine.
Learning Objectives
By the end of this lesson, students should be able to:
- Identify Qwen as Alibaba’s open-weight (plus cloud API) family with multilingual and multimodal branches.
- Separate Qwen weights from Alibaba Cloud Model Studio / DashScope as the commercial control plane.
- Write a qualitative Pricing / Strengths / Weaknesses card vs Llama, Mistral, and DeepSeek.
- Choose size-ladder + VL/audio siblings without inventing unpublished architecture.
- Sketch an OpenAI-compatible or DashScope-style chat call with a pinned Qwen SKU.
- Flag license, region, and data-path checks before production.
Qwen is the Qwen team / Alibaba family of foundation language and multimodal models, widely released as open weights across many sizes (instruct, coder, MoE, VL, audio—confirm current cards). Alibaba Cloud offers hosted Qwen (and other) models via developer APIs often branded Model Studio / DashScope, plus consumer Tongyi products. Open Qwen ≠ a dump of every Alibaba production model. Licenses vary by checkpoint—read each one.
Product Surfaces
| Surface | Access | Typical job |
|---|---|---|
| Qwen dense / MoE open weights | HF / ModelScope / Alibaba releases | Multilingual assistants, agents, coding; size ladder from small to large |
| Qwen-VL / audio siblings | Open multimodal checkpoints | Image+text or speech lines—eval modalities separately (Vol. 16) |
| Alibaba Cloud Model Studio / DashScope | Metered cloud API | Production Qwen without owning GPUs; China + international endpoint stories |
| Tongyi / consumer apps | Product UIs | Exploration—not your multi-tenant backend |
| Western hosts of Qwen | Together, Fireworks, HF, etc. | Same weights, different ToS/region than Alibaba Cloud |
Pricing / Strengths / Weaknesses
| Axis | Pricing (qualitative) | Strengths | Weaknesses |
|---|---|---|---|
| Open weights / self-host | No Alibaba token fee; pay GPU/ops. Tiny Qwen SKUs fit edge/Tier 2; large MoE needs serious serving (Vol. 18.4). | Broadest open size menu among many labs; strong multilingual (especially Chinese + English) narrative; frequent releases; VL/audio options. | Release cadence = pin-or-perish; license differs by card; you own eval on each language slice (Vol. 20 fairness). |
| Alibaba Cloud API | Token-metered (sometimes cheaper international vs China endpoints—read live tables, do not invent CNY/$). Consumer Tongyi ≠ API invoice. Context-caching / batch modes may exist—confirm. | Native home for Qwen; good fit if the estate is already Aliyun; OpenAI-compatible modes reduce Vol. 18 friction. | Endpoint/region choice is a data-map decision; Western enterprises may prefer a non-Aliyun host of the same weights. |
| Multimodal Qwen | VL/audio APIs or self-host GPUs; usually costlier than text-only tokens per request. | Open multimodal alternative to closed Gemini/GPT vision. | Not Imagen/Veo/Sora; stills/video generation catalogs stay in Vol. 16 / Module 22.2–22.3. |
| Enterprise | Aliyun commitments, VPC, and marketplace listings elsewhere—not public stickers. | One cloud bill if you already run Alibaba Cloud. | Jurisdictional review similar to DeepSeek for some regulated Vol. 21 products. |
Vs Llama
- Often stronger CJK / multilingual story
- Wider published size ladder including tiny SKUs
- Llama still wins some Western ecosystem defaults
Vs Mistral / DeepSeek
- Mistral: EU vendor + Mixtral MoE focus
- DeepSeek: sharper reasoning-SKU marketing
- Qwen: multilingual + VL siblings + Aliyun gravity
Pick Qwen when
- Chinese/multilingual product quality is a gate
- You need one family from 0.5B-class to large MoE
- Alibaba Cloud is already the estate—or you will self-host
Why Qwen is on open shortlists
- Size + modality coverage from one brand
- HF/ModelScope gravity in Asia and globally
- Compatible APIs keep integration cheap
Limits
- Do not treat every Qwen card as the same license
- Aliyun API ≠ a Western host ≠ Tongyi app
- No fake multilingual BLEU crowns here—slice your eval
Practical API Sketch
DashScope / Model Studio often exposes an OpenAI-compatible mode. Confirm base URL, region, and model IDs. International vs China endpoints change the data path.
Related Lectures
| Lecture | Role |
|---|---|
| DeepSeek | Previous dual-track lab; similar jurisdiction diligence |
| Qwen (11.5) | Family lineage: sizes, MoE, VL |
| Llama / Mistral | Open-weight peers |
| Vision / multimodal Vol. 16 | Eval Qwen-VL separately from text |
| OpenAI SDK | Compatible client pattern |
| Microsoft (Phi, Copilot) | Next: SLMs + Copilot distribution |
Qwen open weights are Alibaba’s entire production stack. Second: one license covers every Qwen checkpoint. Third: DashScope international and China endpoints are the same data path. Fourth: Qwen-VL replaces Imagen/Veo/Sora. Fifth: this lecture invents token prices and multilingual leaderboards. Sixth: picking Qwen skips Vol. 19 language-slice eval and Vol. 20 privacy.
Knowledge Check
- Short Answer: What is Qwen in this catalog? Answer: Alibaba’s open-weight (plus cloud API) LLM/multimodal family.
- True/False: Alibaba Cloud Model Studio/DashScope is the same as downloading weights. Answer: False.
- Multiple Choice: A common Qwen strength is: (a) multilingual + wide size ladder, (b) being OSI Gemini weights, (c) replacing Vertex IAM. Answer: (a).
- Short Answer: Why might a team use a Western host of Qwen instead of Aliyun? Answer: Data-path / ToS / region policy—same weights, different vendor contract.
- True/False: Every Qwen checkpoint shares one license. Answer: False.
- Multiple Choice: Qwen-VL should be evaluated: (a) as a separate multimodal SKU (Vol. 16), (b) only with BLEU on English news, (c) as Sora. Answer: (a).
- Short Answer: Which Vol. 11.5 lecture is the Qwen family home? Answer: Qwen.
- True/False: This page wants you to memorize invented Qwen dollar prices. Answer: False.
- Multiple Choice: Pick Qwen when: (a) CJK/multilingual + size ladder or Aliyun estate, (b) you need Claude Artifacts only, (c) you refuse eval. Answer: (a).
- Short Answer: Which provider lecture closes Module 22.1? Answer: Microsoft (Phi, Copilot).
Key Takeaways
- Qwen = Alibaba’s open family; Alibaba Cloud = hosted Model Studio/DashScope path.
- Qualitative pricing: GPUs vs Aliyun tokens vs consumer Tongyi; region endpoints change the map.
- Strength: multilingual, size ladder, VL siblings. Weakness: license/region churn; not a video-gen lab.
- Cross-link Vol. 11.5 Qwen, Vol. 16 multimodal, Vol. 18 compatible SDK.
- Next: Microsoft Phi & Copilot, then Module 22.2 Stability AI.
Lab: Multilingual vendor card: Llama vs Qwen vs Mistral for a two-language RAG app. Students pick size (edge vs server), API vs self-host vs Western host, and write the data-region sentence. Optional DashScope or Ollama spike.
Whiteboard: Open four (Llama, Mistral, DeepSeek, Qwen) then arrow to Microsoft: “SLM + Copilot distribution, not another open 70B.”
Recap: Qwen is Alibaba’s multilingual open family plus Aliyun APIs. Module 22.1 ends with Microsoft (Phi, Copilot).