Q

Qwen3.8-27B

Alibaba · Released Aug 2026

pending

Qwen3.8-27B is Alibaba's 27-billion-parameter open-weight model announced August 3, 2026 as the single-GPU companion to the 2.4T Qwen3.8-Max flagship. Open weights were promised for the week of August 10, 2026 on Hugging Face and ModelScope but have not yet shipped. No benchmarks, no license, no architecture details, and no context window have been published — the model is a commitment with a parameter count. If it ships as promised under a permissive license, it could become the most important local AI release of the year; until then, it's vaporware backed by Alibaba's word.

Is it right for you?

Good for

  • Single-GPU self-hosting — 27B parameters fits a single consumer or datacenter GPU when quantized (4-bit: ~15GB VRAM, FP8: ~27GB, BF16: ~54GB)
  • Open-weight ownership — full control over fine-tuning, data privacy, and deployment without API vendor lock-in
  • Qwen 3.6 lineage — predecessor Qwen3.6-27B delivered strong open-weight coding and agent performance under Apache 2.0; 3.8 generation inherits training improvements
  • Cost-sensitive volume deployments — self-hosting breaks even vs. API at several billion tokens/month

Not good for

  • Immediate production use — no benchmarks published, no license disclosed, weights not yet on Hugging Face
  • Regulated environments requiring auditable model cards, verified safety evaluations, and clear license terms
  • Maximum capability workloads — the 27B model will not match the 2.4T Qwen3.8-Max flagship on complex reasoning or frontier benchmarks
  • Teams who need predictable API pricing and SLAs — no API offering exists; this is a self-host-only model

Pricing

Input

Free (open weights — self-hosted)

Output

Free (open weights — self-hosted)

Context

TBD — context window not published

View full pricing

No verdict changes yet

The clock starts day one — changes land here as our verdict evolves.

Verification log

No verification checks yet

We haven't logged a verification check for this entry. Once a check runs, its history shows here.

How we evaluate