DynaGuard AIO needs about 2.5 GB of memory at Q4_K_M (a 1.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 32 quants, from 0.8 GB (Q2_K) to 16.1 GB (F32). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
DynaGuard AIO – a lightweight guardian model for on‑device moderation
DynaGuard AIO is a 1.72B‑parameter decoder‑only transformer based on Qwen3. It evaluates text against user‑defined policies and can produce a fast PASS/FAIL or a chain‑of‑thought explanation. The model is licensed under apache‑2.0 and supports only text input.
Good at
- Custom policy enforcement
- Fast inference with sub‑50 ms latency
- Chain‑of‑thought reasoning for interpretability
Limits
- No vision support
- Requires 8 k context for the provided memory estimates
- Only text‑based moderation
Best for
- Real‑time chatbot moderation
- Enterprise compliance filtering
- On‑device safety checks
Who it’s for. Developers building chatbots or generative AI services that need configurable, natural‑language guardrails. The model is suitable for both cloud and edge deployments where low latency and small footprint are important.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 0.8 GB | 2.2 GB | Fits | Get file → | |
| Q3_K_S | 0.9 GB | 2.3 GB | Fits | Get file → | |
| Q3_K_M | 0.9 GB | 2.4 GB | Fits | Get file → | |
| Q3_K_L | 1.0 GB | 2.4 GB | Fits | Get file → | |
| Q4_0 | 1.1 GB | 2.5 GB | Fits | Get file → | |
| Q4_K_S | 1.1 GB | 2.5 GB | Fits | Get file → | |
| Q4_K | 1.1 GB | 2.5 GB | Fits | Get file → | |
| Q4_K_M | 1.1 GB | 2.5 GB | Fits | Get file → | |
| Q4_1 | 1.1 GB | 2.6 GB | Fits | Get file → | |
| Q5_0 | 1.2 GB | 2.7 GB | Fits | Get file → | |
| Q5_K_S | 1.2 GB | 2.7 GB | Fits | Get file → | |
| Q5_K | 1.3 GB | 2.7 GB | Fits | Get file → | |
| Q5_K_M | 1.3 GB | 2.7 GB | Fits | Get file → | |
| Q5_1 | 1.3 GB | 2.8 GB | Fits | Get file → | |
| Q6_K | 1.4 GB | 2.9 GB | Fits | Get file → | |
| Q2_K | 1.7 GB | 3.1 GB | Fits | Get file → | |
| Q8_0 | 1.8 GB | 3.3 GB | Fits | Get file → | |
| Q3_K_S | 1.9 GB | 3.3 GB | Fits | Get file → | |
| Q3_K_M | 2.1 GB | 3.5 GB | Fits | Get file → | |
| Q3_K_L | 2.2 GB | 3.7 GB | Fits | Get file → | |
| Q4_K_S | 2.4 GB | 3.8 GB | Fits | Get file → | |
| Q4_K_M | 2.5 GB | 3.9 GB | Fits | Get file → | |
| Q5_K_S | 2.8 GB | 4.3 GB | Fits | Get file → | |
| Q5_K_M | 2.9 GB | 4.3 GB | Fits | Get file → | |
| Q6_K | 3.3 GB | 4.7 GB | Fits | Get file → | |
| BF16 | 3.4 GB | 4.9 GB | Fits | Get file → | |
| F16 | 3.4 GB | 4.9 GB | Fits | Get file → | |
| Q8_0 | 4.3 GB | 5.7 GB | Fits | Get file → | |
| F32 | 6.9 GB | 8.3 GB | Too big | Get file → | |
| BF16 | 8.1 GB | 9.5 GB | Too big | Get file → | |
| F16 | 8.1 GB | 9.5 GB | Too big | Get file → | |
| F32 | 16.1 GB | 17.5 GB | Too big | Get file → |
For 8 GB VRAM use Q4_K or Q4_K_S (file size 1.11 GB, memory 2.5 GB). If 12 GB VRAM is available, Q5_K_M (file size 1.26 GB, memory 2.7 GB) offers higher quality. For 16 GB VRAM, Q6_K (file size 1.42 GB, memory 2.9 GB) provides a balance between size and performance.
What GPU do you need for DynaGuard AIO?
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: the best quant that fits is Q4_K_M (2.5 GB file, about 3.9 GB in use).
- 6 GB VRAM: the best quant that fits is Q8_0 (4.3 GB file, about 5.7 GB in use).
- 8 GB VRAM: the best quant that fits is Q8_0 (4.3 GB file, about 5.7 GB in use).
- 12 GB VRAM: the best quant that fits is BF16 (8.1 GB file, about 9.5 GB in use).
- 16 GB VRAM: the best quant that fits is BF16 (8.1 GB file, about 9.5 GB in use).
- 24 GB VRAM: the best quant that fits is F32 (16.1 GB file, about 17.5 GB in use).
Which DynaGuard AIO quant should you choose?
Q4_K_M is the usual starting point for DynaGuard AIO: it balances file size and quality well. Here it is a 1.1 GB file.
The Q8_0 file is 1.8 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q2_K at 0.8 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about DynaGuard AIO
How much VRAM does DynaGuard AIO need?
About 2.5 GB at Q4_K_M with an 8K context window. That is the 1.1 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 DynaGuard AIO on an 8 GB GPU?
Yes, with Q8_0: the 4.3 GB file needs about 5.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of DynaGuard AIO GGUF?
It depends on the quant: Q2_K is 0.8 GB, Q3_K_S is 0.9 GB, Q3_K_M is 0.9 GB, Q3_K_L is 1.0 GB, Q4_0 is 1.1 GB, Q4_K_S is 1.1 GB and 26 more.
What context length does DynaGuard AIO support?
The GGUF header lists a trained context length of 40,960 tokens (40K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download DynaGuard AIO GGUF?
The files are on Hugging Face in the prithivMLmods/DynaGuard-AIO-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 DynaGuard AIO 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 DynaGuard AIO on 8 GB VRAM?
Yes, the Q4_K quant uses about 2.5 GB of VRAM at 8 k context, which fits within an 8 GB budget.
Does the model support image input?
No, DynaGuard AIO only processes text and does not have vision capabilities.
What license applies to this model?
The model is released under the apache‑2.0 license.