TL;DR
On August 12, 2026, Alibaba published the Qwen3.8-Max open weights on Hugging Face and ModelScope — the first time a Qwen-Max-tier flagship has been downloadable at all. The model is a 2.4-trillion-parameter Mixture-of-Experts that activates only ~95B parameters per token, with a 1M-token context and $2 input / $6 output per M on the hosted API.
Three things are easy to miss in the announcement:
- The license is not Apache 2.0. It's a custom "qwen3.8-max" license with thresholds: past 100M monthly active users or $20M monthly revenue you must display the model name; MaaS / AI-assistant businesses past $50M trailing revenue need a separate commercial license. Internal use is exempt.
- The flagship is a datacenter play. Cheapest usable quant is ~450GB of combined RAM+VRAM; lossless BF16 is ~4.9TB. Alibaba's own reference deployment uses 72 Blackwell Ultra GPUs. "Open weights" here means "you can download it", not "you can run it".
- Every benchmark number is Alibaba's own. 86.6% on TerminalBench 2.1, 67.7 SWE-bench Pro, 93.0 PaperBench — none independently verified yet. It briefly topped the Artificial Analysis Agentic Index before a methodology update moved it to a near-tie for #2.
The release that actually matters for most developers is the Qwen3.8-27B sibling — a ~14-16GB-VRAM model at 4-bit that runs on an RTX 4090.
What actually shipped
Alibaba previewed Qwen3.8-Max at WAIC Shanghai on July 19 with a parameter count and nothing else. The hosted API went GA on August 3, paired with a promise that open weights were coming "next week". The weights landed August 11-12 — roughly a week late by the stated schedule, a delay the developer community noticed.
What's in the repos (Qwen/Qwen3.8-2.4T-A95B plus an FP8 variant):
| Spec | Qwen3.8-Max | Qwen3.8-27B |
|---|---|---|
| Total params | 2.4T (MoE) | 27B |
| Active per token | ~95B | 27B (dense) |
| Context | 1M (native 262K, extendable) | — |
| Max output | 131,072 tokens | — |
| Multimodal | API yes; checkpoint text-only* | Text |
| API price (in/out per M) | $2 / $6 | — |
| Cache read | $0.25 / M (implicit) | — |
* LocalLLaMA users reported the open checkpoint ships text-only while the hosted API keeps vision input — the Hugging Face card lists vision, non-thinking mode, 1M default context and built-in tools as "Max"-side additions on top of the raw checkpoint.
The hosted API also matters on its own: at $2 / $6 per M (cached input $0.25), it's roughly 5x cheaper on input than Claude Fable 5 ($10/$50) and cheaper than Claude Opus 5 ($5/$25) on output. For agent workloads that re-read the same codebase every turn, cached input at $0.25 is the number that actually moves your bill.
The license: "open" with a gate
The repo's LICENSE file is titled qwen3.8-max, not Apache 2.0. Two operative conditions, per the license text:
- Attribution gate: if your product or service crosses 100M monthly active users or $20M in monthly revenue, you must display the model name prominently in your UI.
- Commercial gate: if you run a Model-as-a-Service or "AI Work Assistant" business (inference hosting, or standalone coding/office AI products) generating more than $50M aggregate revenue over any 12-month period, you need a separate commercial license from Qwen before continuing to use it for that purpose.
Pure internal use — no third-party access — is exempt from both.
Several outlets headline this as a "revenue-share" license drawing a line to Moonshot's Kimi K3 terms. That comparison doesn't hold: there is no percentage anywhere in the Qwen3.8-Max license. It's a usage-gate (negotiate a separate license when you cross a threshold), not a revenue-share. The distinction matters if you're actually budgeting for it.
The broader pattern is a reversal, not a first. Qwen-72B and Qwen2-72B shipped under near-identical custom terms years ago (including the same 100M-MAU trigger; Qwen2's license went further with a non-compete clause). Then all of Qwen3 shipped Apache 2.0 — the most permissive release Alibaba had done. Qwen3.8-Max walks that back, and the developer reaction has been split: a New Stack piece summarized the mood as watching "an API business model wearing an open source jacket".
Practical guidance: for research, internal use, and startups, the license is effectively free. If you're a large or inference-hosting business, read the LICENSE file in the actual repo before you plan an architecture around it — and treat any secondhand summary (including this one) as a prompt to verify.
Can you actually run it
Almost certainly not, on hardware you own. The honest numbers:
| Configuration | Memory requirement | Reference deployment |
|---|---|---|
| Dynamic 1-bit quant (cheapest usable) | ~450GB RAM+VRAM | Multi-node cluster |
| BF16 (lossless) | ~4.9TB | Not practical |
| Alibaba's own reference | — | 72 × Blackwell Ultra (GB300 NVL72) |
That means self-hosting the flagship is effectively renting a cloud cluster, which somewhat defeats the practical case for "open weights" as an alternative to the API in the first place. The value of the open release is real but different: fine-tuning, distillation, offline eval, and data-control for teams that already run multi-node inference — not a laptop experiment.
The 27B that matters
The release most developers can actually use is Qwen3.8-27B, shipped in the same wave:
- ~14-16GB VRAM at 4-bit — an RTX 4090 runs it. FP8 lands around 27GB, workable on an L40S.
- Community quantizations (GGUF/AWQ) typically arrive 1-2 weeks after official weights; vLLM and SGLang usually have day-one support. Ollama waits on GGUF, so don't plan a launch around it in week one.
- KV cache scales with context length and concurrency — serving multiple long-context requests can double the memory footprint.
If your goal is a local Qwen model on hardware you own, the 27B is the model worth tracking — not the 2.4T flagship making the headlines.
Benchmarks: vendor-reported
Alibaba's own published table (August 3) is competitive on paper:
| Benchmark | Qwen3.8-Max | Qwen3.7-Max (prev.) |
|---|---|---|
| TerminalBench 2.1 | 86.6 | 74.5 |
| SWE-bench Pro | 67.7 | 60.6 |
| PaperBench | 93.0 | 64.8 |
| OSWorld-Verified | 86.1 | — |
| FrontierSWE | 73.5 | 40.7 |
All of it is self-reported. Scale AI's public SWE-bench Pro leaderboard has no Qwen3.8-Max entry as of this writing, and there's no independent Artificial Analysis or LMArena score for the open checkpoint. The SWE-bench Pro number puts the model mid-pack: ahead of GPT-5.6 Sol (64.6), behind Claude Opus 4.8 (69.2), and 12 points below Fable 5 (80.0).
There was one genuinely independent datapoint this week, and it was a rollercoaster: Qwen3.8-Max briefly topped the Artificial Analysis Agentic Index, driving a #6-ranked Hacker News thread (~544 points) about Chinese frontier models closing the gap. Days later, a methodology update (v4.1.1 — new grader models, newer τ³-Banking) moved it to a near-tie for #2 at 58, behind Claude Opus 5 max-effort at 59. Same model, different yardstick — a reminder to always check the methodology version next to the score.
vs Kimi K3, DeepSeek & Claude
Qwen3.8-Max lands in an open-weight class now populated by real competitors:
| Dimension | Qwen3.8-Max | Kimi K3 | DeepSeek V4-Flash | Claude Opus 5 |
|---|---|---|---|---|
| Params (active) | 2.4T (95B) | 2.8T (104B) | 284B (13B) | Closed |
| Context | 1M | 1M | — | 1M |
| API in / out (per M) | $2 / $6 | $3 / $15 | $0.08 / $0.18 | $5 / $25 |
| License | Custom (usage-gate) | Custom (reported rev-share) | MIT | Closed |
| Open weights | Yes (first Max-tier) | Yes | Yes | No |
| Independent verification | Pending | Limited | Limited | — |
The strategic read: this is the third open-weight release from a Chinese lab in two months (Kimi K3, then DeepSeek V4-Flash, now Qwen3.8-Max), and the "open weights at frontier" category is no longer fringe. For teams comparing self-hosted options, the license table is now a first-order decision input — DeepSeek's MIT is the most permissive, Qwen's usage-gate is middle, and Kimi's reported revenue-share is the most aggressive. All three cost far less than any closed frontier tier.
Who should use it
Seriously evaluate it if:
- You run a multi-node inference cluster and want Max-class coding quality under your own control — the open release is the first time that's an option.
- You need fine-tuning, distillation, or offline eval against a frontier-scale checkpoint.
- You're on OpenAI/Anthropic-compatible APIs — QwenCloud exposes both chat-completions and Responses-style endpoints, and Alibaba published plug-in examples for Claude Code, Codex, Qoder, Qwen Code and OpenClaw, so the migration cost is low.
- You're a local-deployment team — use the 27B, not the 2.4T.
Hold off if:
- You're a large or inference-hosting business and haven't read the LICENSE file yet — the commercial gate applies above $50M trailing MaaS revenue.
- You're choosing purely on benchmarks — nothing is independently verified yet; Alibaba's own numbers put it mid-pack on SWE-bench Pro behind closed frontier models.
- You expected "open weights" to mean "runs on my workstation" — the flagship doesn't. The 27B does.
How we wrote this
This piece was compiled on August 14, 2026, two days after the weights landed. We cross-referenced:
- The Hugging Face model card and LICENSE file, fetched directly, plus the official Qwen3.8-Max announcement.
- Independent technical coverage from sdd.sh (license reality check), ByteIota (hardware floor), and Subagentic (Agentic Index timeline).
- Hacker News and r/LocalLLaMA discussion for developer sentiment on the license and the text-only checkpoint.
We have not independently run or benchmarked Qwen3.8-Max. All benchmark figures are Alibaba-reported. Pricing is current as of August 14, 2026. The license thresholds are drawn from the repo's LICENSE file, not secondhand summaries — verify against the live repo before any architecture decision.
Corrections or counter-evidence welcome in the comments or via our about page contact.