PL

Plano Orchestrator 30B A3B

PlanoGGUF by mradermacherUpdated 2026-04-04
Download on Hugging Face
Parameters30.5B
Context256K
Layers48
Architectureqwen3moe
Smallest quant0.1 GB
Quick answer

Plano Orchestrator 30B A3B needs about 19.9 GB of memory at Q4_K_M (a 18.6 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 24 quants, from 0.1 GB to 25.1 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 3.2 GB.

Plano Orchestrator 30B A3B – a routing and orchestration LLM

Plano Orchestrator 30B A3B is a 30.5 billion‑parameter model built on the qwen3moe architecture. It is a mixture of experts with 3 billion active parameters and is trained on 262144 context tokens. The model focuses on routing and orchestration tasks in multi‑agent systems.

Good at

  • Routing decisions for multi‑agent workflows
  • Multi‑turn context understanding
  • Multi‑intent detection

Limits

  • No vision support
  • License type is other
  • Requires large VRAM for full precision

Best for

  • Low‑latency production routing
  • Complex multi‑agent orchestration
  • Long‑context conversation analysis

Who it’s for. Engineers and developers building multi‑agent systems who need precise routing decisions. The model is suitable for production environments that can accommodate its memory requirements.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
—0.1 GB 1.4 GB
Fits Get file →
IQ1_S6.4 GB 7.7 GB
Tight Get file →
IQ1_M7.1 GB 8.4 GB
Too big Get file →
IQ2_XXS8.2 GB 9.5 GB
Too big Get file →
IQ2_XS9.1 GB 10.4 GB
Too big Get file →
IQ2_S9.3 GB 10.6 GB
Too big Get file →
IQ2_M10.2 GB 11.5 GB
Too big Get file →
Q2_K_S10.5 GB 11.8 GB
Too big Get file →
Q2_K11.3 GB 12.6 GB
Too big Get file →
IQ3_XXS11.8 GB 13.2 GB
Too big Get file →
IQ3_XS12.6 GB 13.9 GB
Too big Get file →
Q3_K_S13.3 GB 14.6 GB
Too big Get file →
IQ3_S13.3 GB 14.6 GB
Too big Get file →
IQ3_M13.5 GB 14.8 GB
Too big Get file →
Q3_K_M14.7 GB 16.0 GB
Too big Get file →
Q3_K_L15.9 GB 17.2 GB
Too big Get file →
IQ4_XS16.4 GB 17.7 GB
Too big Get file →
Q4_017.4 GB 18.7 GB
Too big Get file →
Q4_K_S17.5 GB 18.8 GB
Too big Get file →
Q4_K_M18.6 GB 19.9 GB
Too big Get file →
Q4_119.2 GB 20.5 GB
Too big Get file →
Q5_K_S21.1 GB 22.4 GB
Too big Get file →
Q5_K_M21.7 GB 23.0 GB
Too big Get file →
Q6_K25.1 GB 26.4 GB
Too big Get file →

For 8 GB VRAM, use IQ1_S (file size 6.42 GB, estimated 7.7 GB at 8k context). For 12 GB VRAM, use Q2_XXS (file size 8.18 GB, estimated 9.5 GB). For 16 GB VRAM, use Q3_K_M (file size 14.71 GB, estimated 16 GB).

What GPU do you need for Plano Orchestrator 30B A3B?

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 the main file (0.1 GB file, about 1.4 GB in use).
  • 6 GB VRAM: the best quant that fits is the main file (0.1 GB file, about 1.4 GB in use).
  • 8 GB VRAM: the best quant that fits is IQ1_S (6.4 GB file, about 7.7 GB in use).
  • 12 GB VRAM: the best quant that fits is Q2_K_S (10.5 GB file, about 11.8 GB in use).
  • 16 GB VRAM: the best quant that fits is Q3_K_M (14.7 GB file, about 16.0 GB in use).
  • 24 GB VRAM: the best quant that fits is Q5_K_M (21.7 GB file, about 23.0 GB in use).
  • 32 GB VRAM: the best quant that fits is Q6_K (25.1 GB file, about 26.4 GB in use).

Which Plano Orchestrator 30B A3B quant should you choose?

Q4_K_M is the usual starting point for Plano Orchestrator 30B A3B: it balances file size and quality well. Here it is a 18.6 GB file.

If memory is tight, the smallest file is the first one in the table at 0.1 GB, with the quality trade-offs that come with fewer bits.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architectureqwen3moe
Parameters30.5B (approximate, mixture of experts)
Active parameters3B
Layers48
Trained context262,144 tokens
KV cache (fp16)96 KB per token

Source

Quantized bymradermacher
FamilyPlano
Licenseother
Downloads (HF)1,237
Last updated2026-04-04

Frequently asked questions about Plano Orchestrator 30B A3B

How much VRAM does Plano Orchestrator 30B A3B need?

About 19.9 GB at Q4_K_M with an 8K context window. That is the 18.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 Plano Orchestrator 30B A3B on an 8 GB GPU?

Yes, with IQ1_S: the 6.4 GB file needs about 7.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Plano Orchestrator 30B A3B GGUF?

It depends on the quant: file is 0.1 GB, IQ1_S is 6.4 GB, IQ1_M is 7.1 GB, IQ2_XXS is 8.2 GB, IQ2_XS is 9.1 GB, IQ2_S is 9.3 GB and 18 more.

What context length does Plano Orchestrator 30B A3B support?

The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.8 GB at 8K and 3.2 GB at 32K.

Where can I download Plano Orchestrator 30B A3B GGUF?

The files are on Hugging Face in the mradermacher/Plano-Orchestrator-30B-A3B-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 Plano Orchestrator 30B A3B use?

Hugging Face lists the license as other. 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 this model on 8 GB VRAM?

Yes, the IQ1_S quant uses about 7.7 GB at 8k context, fitting within 8 GB VRAM.

Does the model support vision tasks?

No, the model has no vision capabilities.

What is the maximum context length?

The model was trained on 262144 tokens and can handle that context length.

Other GGUFs of Plano-Orchestrator-30B-A3B

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Plano models

All Plano →

Other medium models

All medium models →