On-prem models / Alibaba Qwen

Run Qwen3.8-27B on-prem

Dense 27B vision-language model in the Qwen3.8 generation, using the Qwen3.5 hybrid layout of 3 Gated DeltaNet layers per gated-attention layer. Thinking is on by default and can be disabled per request.

27.8B dense256K contextApache-2.0text + visionthinking modetool callingreleased 2026-08

Memory needed

PrecisionWeightsKV per request, 8KKV per request, 32KKV per request, 128K
BF16 (full precision)55.6 GB0.54 GB2.15 GB8.59 GB
FP827.8 GB0.27 GB1.07 GB4.29 GB
INT4 (AWQ / GPTQ)15.6 GB0.27 GB1.07 GB4.29 GB
GGUF Q4_K_M16.7 GB0.27 GB1.07 GB4.29 GB

KV cache from the published config: 64 layers, 4 KV heads x 256 dims, 16 full-attention layers. 16-bit cache for BF16 rows, 8-bit otherwise.

Fit for ERP and manufacturing work

Probably the best single-GPU default for plant or HQ on-prem use: good at text-to-SQL over large ERP schemas, structured extraction from scanned POs, invoices and mill certificates, and tool-calling agents. Supports 201 languages per the Qwen3.5 family card, which helps multilingual plants.

Strengths

  • Strong all-rounder that fits one 80 GB GPU in FP8 or one 48 GB card at 4-bit
  • Native image, document and video understanding
  • Small KV cache for its size because only 16 layers keep KV
  • Apache 2.0

Watch out for

  • About 56 GB in BF16; long context still needs extra memory for the 16 attention layers
  • Dense model, so decode is slower than 3B-active MoE options
  • Card advises keeping at least 128K context for best thinking behaviour

GPUs that run it

One user, 8K context, FP8

HardwareCountMemory usedTok/s per user
NVIDIA A100 40GB PCIe130 / 36 GB32
NVIDIA L4 24GB232 / 43 GB11
NVIDIA A10 24GB232 / 43 GB22
NVIDIA L40S 48GB130 / 43 GB18
NVIDIA RTX A6000 48GB130 / 43 GB16
NVIDIA RTX 6000 Ada 48GB130 / 43 GB20
NVIDIA GeForce RTX 4090 24GB232 / 43 GB35
NVIDIA GeForce RTX 5090 32GB232 / 57 GB58

20 people at once, 16K context, FP8

HardwareCountMemory usedTok/s per user
NVIDIA L4 24GB242 / 43 GB9
NVIDIA A10 24GB242 / 43 GB18
NVIDIA L40S 48GB141 / 43 GB15
NVIDIA RTX A6000 48GB141 / 43 GB14
NVIDIA RTX 6000 Ada 48GB141 / 43 GB17
NVIDIA GeForce RTX 4090 24GB242 / 43 GB30
NVIDIA GeForce RTX 5090 32GB242 / 57 GB50
AMD Instinct MI210 64GB141 / 57 GB28

Serving and licence

SGLang cookbook and vLLM recipe for Qwen3.8-27B; Qwen/Qwen3.8-27B-FP8 is official. Use --reasoning-parser qwen3 and qwen3_coder tool parser. Community GGUFs run in llama.cpp/Ollama builds that support the qwen3.5 hybrid architecture.

Apache-2.0. Apache 2.0: commercial use, modification and redistribution allowed with notice; no usage caps.

Model card on Hugging Face

Design a Qwen3.8-27B deployment

Preloaded with Qwen3.8-27B. Add your ERP and documents, change GPUs or users, and export the diagram.

Loading the architecture builder...

Questions

How much VRAM does Qwen3.8-27B need?

The weights alone take about 55.6 GB in BF16, 27.8 GB in FP8 and 15.6 GB in 4-bit. On top of that each request holds a KV cache of about 0.27 GB at 8K tokens of context (FP8 cache), so 20 people generating at once need roughly 5.37 GB more, plus a few GB of runtime overhead.

What is the smallest GPU setup that runs Qwen3.8-27B?

For a single user at 8K context in FP8, 1 x NVIDIA A100 40GB PCIe (40 GB each) fits, at an estimated 32 tokens per second. For a team, size for concurrent requests and context; the builder above does that.

Is Qwen3.8-27B allowed for commercial use?

Qwen3.8-27B is released under Apache-2.0. Apache 2.0: commercial use, modification and redistribution allowed with notice; no usage caps. Check the licence text on the model card with your legal team before production use.

Which engine should serve Qwen3.8-27B on-prem?

SGLang cookbook and vLLM recipe for Qwen3.8-27B; Qwen/Qwen3.8-27B-FP8 is official. Use --reasoning-parser qwen3 and qwen3_coder tool parser. Community GGUFs run in llama.cpp/Ollama builds that support the qwen3.5 hybrid architecture.