Boundary 4x7b MoE i1 needs about 16.2 GB of memory at Q4_K_M (a 14.6 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 21 quants, from 5.0 GB (IQ1_S) to 19.8 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.
Boundary 4x7b MoE i1 – a 24.2B llama‑style mixture of experts model
Boundary 4x7b MoE i1 is a 24.2B parameter llama architecture model with a 32768 token context window. It is a mixture of experts and supports tool usage. The model is released under the apache-2.0 license.
Good at
- Tool integration
- Large context handling
- Mixture of experts architecture
Limits
- No vision support
- Requires large VRAM for higher quants
- No active parameter count provided
Best for
- Developers building tool‑enabled assistants
- Researchers needing long‑context models
- Applications requiring expert routing
Who it’s for. Engineers and researchers who need a large llama‑style model with expert routing and tool support. The model is suitable for local deployment on systems with sufficient VRAM.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 5.0 GB | 6.6 GB | Fits | Get file → | |
| IQ1_M | 5.5 GB | 7.1 GB | Fits | Get file → | |
| IQ2_XXS | 6.4 GB | 8.0 GB | Tight | Get file → | |
| IQ2_XS | 7.1 GB | 8.7 GB | Too big | Get file → | |
| IQ2_S | 7.3 GB | 8.9 GB | Too big | Get file → | |
| IQ2_M | 8.0 GB | 9.6 GB | Too big | Get file → | |
| Q2_K | 8.8 GB | 10.4 GB | Too big | Get file → | |
| IQ3_XXS | 9.3 GB | 10.9 GB | Too big | Get file → | |
| IQ3_XS | 9.9 GB | 11.5 GB | Too big | Get file → | |
| Q3_K_S | 10.4 GB | 12.0 GB | Too big | Get file → | |
| IQ3_S | 10.5 GB | 12.0 GB | Too big | Get file → | |
| IQ3_M | 10.6 GB | 12.2 GB | Too big | Get file → | |
| Q3_K_M | 11.6 GB | 13.2 GB | Too big | Get file → | |
| Q3_K_L | 12.5 GB | 14.1 GB | Too big | Get file → | |
| IQ4_XS | 12.9 GB | 14.5 GB | Too big | Get file → | |
| Q4_0 | 13.7 GB | 15.3 GB | Too big | Get file → | |
| Q4_K_S | 13.7 GB | 15.3 GB | Too big | Get file → | |
| Q4_K_M | 14.6 GB | 16.2 GB | Too big | Get file → | |
| Q5_K_S | 16.6 GB | 18.2 GB | Too big | Get file → | |
| Q5_K_M | 17.1 GB | 18.7 GB | Too big | Get file → | |
| Q6_K | 19.8 GB | 21.4 GB | Too big | Get file → |
For 8‑GB VRAM, use IQ1_S (5.01 GB, 6.6 GB memory) or IQ1_M (5.53 GB, 7.1 GB). With 12‑GB VRAM, IQ2_S (7.3 GB, 8.9 GB) or Q2_K (8.84 GB, 10.4 GB) are viable. Higher quants such as Q4_K_M (14.61 GB, 16.2 GB) need 16‑GB or more VRAM.
What GPU do you need for Boundary 4x7b MoE i1?
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: the best quant that fits is IQ2_XXS (6.4 GB file, about 8.0 GB in use).
- 12 GB VRAM: the best quant that fits is IQ3_S (10.5 GB file, about 12.0 GB in use).
- 16 GB VRAM: the best quant that fits is Q4_K_S (13.7 GB file, about 15.3 GB in use).
- 24 GB VRAM: the best quant that fits is Q6_K (19.8 GB file, about 21.4 GB in use).
Which Boundary 4x7b MoE i1 quant should you choose?
Q4_K_M is the usual starting point for Boundary 4x7b MoE i1: it balances file size and quality well. Here it is a 14.6 GB file.
If memory is tight, the smallest file is IQ1_S at 5.0 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 Boundary 4x7b MoE i1
How much VRAM does Boundary 4x7b MoE i1 need?
About 16.2 GB at Q4_K_M with an 8K context window. That is the 14.6 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 Boundary 4x7b MoE i1 on an 8 GB GPU?
Yes, with IQ2_XXS: the 6.4 GB file needs about 8.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Boundary 4x7b MoE i1 GGUF?
It depends on the quant: IQ1_S is 5.0 GB, IQ1_M is 5.5 GB, IQ2_XXS is 6.4 GB, IQ2_XS is 7.1 GB, IQ2_S is 7.3 GB, IQ2_M is 8.0 GB and 15 more.
What context length does Boundary 4x7b MoE i1 support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.3 GB at 32K.
Where can I download Boundary 4x7b MoE i1 GGUF?
The files are on Hugging Face in the mradermacher/Boundary-4x7b-MoE-i1-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 Boundary 4x7b MoE i1 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 Boundary 4x7b MoE i1 on 8 GB VRAM?
Use the IQ1_S or IQ1_M quant, which require about 6.6–7.1 GB memory at 8k context.
Does the model support vision?
No, the model has no vision capability.
What license applies to this model?
The model is released under the apache-2.0 license.