Kev 27b needs about 18.5 GB of memory at Q4_K_M (a 15.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 2 quants, from 15.8 GB (Q4_K_M) to 21.0 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
Kev 27b: a decision model built on Qwen3.8-27B
Kev 27b is a decision model that answers typed questions over a state text and returns probabilities. It is based on the Qwen3.8-27B architecture and uses a pointer head kept at Q8_0. The model is served through the /v1/systemone API of llama.cpp and LM Studio.
Good at
- Coding tasks
- Professional work
- Long‑horizon agentic tasks
Limits
- No vision input
- Requires at least 18.5 GB VRAM for Q4_K_M
- Apache‑2.0 license
Best for
- Decision making
- Typed question answering
- Probability scoring
Who it’s for. Developers who need a lightweight decision model that can be integrated via llama.cpp or LM Studio. The model is suitable for applications that require typed question answering and probability outputs.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 15.8 GB | 18.5 GB | Too big | Get file → | |
| Q6_K | 21.0 GB | 23.7 GB | Too big | Get file → |
For a 8 k context window, the Q4_K_M quantization file is 15.84 GB and needs about 18.5 GB of VRAM. The Q6_K file is 21.04 GB and needs about 23.7 GB of VRAM. Both estimates are approximate. Choose the quant that fits your VRAM budget.
What GPU do you need for Kev 27b?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is Q6_K (21.0 GB file, about 23.7 GB in use).
Which Kev 27b quant should you choose?
Q4_K_M is the usual starting point for Kev 27b: it balances file size and quality well. Here it is a 15.8 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Kev 27b
How much VRAM does Kev 27b need?
About 18.5 GB at Q4_K_M with an 8K context window. That is the 15.8 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Kev 27b on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 18.5 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Kev 27b GGUF?
It depends on the quant: Q4_K_M is 15.8 GB, Q6_K is 21.0 GB.
What context length does Kev 27b support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.6 GB at 32K.
Where can I download Kev 27b GGUF?
The files are on Hugging Face in the kdercksen/Kev-27B-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Kev 27b use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run Kev 27b on 8 GB VRAM?
No, the smallest quant requires at least 18.5 GB of VRAM for a 8 k context window.
Does Kev 27b support vision input?
No, Kev 27b does not accept vision input.