What GPU do I need to run ornith-ai/Ornith-1.0-397B?

396.8B parameters, published in BF16. View on Hugging Face

396.8B
Parameters
BF16
Native precision
Qwen3_5MoeForConditionalGeneration
Architecture
text-generation
Pipeline

Ornith-1.0-397B is published by ornith-ai on Hugging Face, with 251,974 downloads and 261 likes to date. It's a Qwen3_5MoeForConditionalGeneration model built for text-generation, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF16739.1 GB886.9 GBNo capable live offer found––
FP8 (quantized)369.6 GB443.5 GBRTX PRO 60005$6.86/hr
INT4 (quantized)184.8 GB221.7 GBRTX 40905$2.68/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Ornith-1.0-397B: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Hybrid: only the full-attention layers cache per token; the other layers keep a fixed-size state. Cached per token: 30,720 bytes at 16-bit.

ContextKV cache, one sequence
4K0.12 GB
32K0.94 GB
128K3.8 GB
256K (model maximum)7.5 GB

Computed from the layer, head and window counts in the model's own configuration (ornith-ai/Ornith-1.0-397B), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Ornith-1.0-397B: common questions

Can Ornith-1.0-397B run on a single GPU?

Not on a desktop card. At BF16 it needs 886.9 GB of VRAM, more than a single 32 GB desktop card holds. No card currently listed on the marketplace both supports BF16 and has enough VRAM for it, so how many it would take is not something this page can answer today.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Ornith 1 models

All 17 Ornith 1 models: VRAM and GPU requirements

Lineage

Also published as: deepreinforce-ai/Ornith-1.0-397B. Identical copies of this model under another account.

Alternatives at this size

Other models for text-generation within about a third of Ornith-1.0-397B's 396.8B parameters, from other model lines.

More on Ornith-1.0-397B

Related reading: H100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.