What GPU do I need to run OuteAI/Lite-Oute-1-300M?

300M parameters, published in F32. View on Hugging Face

300M
Parameters
F32
Native precision
MistralForCausalLM
Architecture
text-generation
Pipeline

Lite-Oute-1-300M is published by OuteAI on Hugging Face, with 37,653 downloads and 9 likes to date. It's a MistralForCausalLM model built for text-generation, published natively in F32.

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)
FP321.1 GB1.3 GBRTX 30701$0.088/hr
FP8 (quantized)0.3 GB0.3 GBRTX 5060 Ti1$0.180/hr
INT4 (quantized)0.1 GB0.2 GBRTX 30701$0.088/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.

Cheapest way to run Lite-Oute-1-300M at its published (F32) precision: 1× RTX 3070, at $0.088/hr per GPU ($0.088/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Lite-Oute-1-300M: 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.

Sliding-window attention: windowed layers stop growing at the window, the full-attention layers keep growing. Cached per token: 35,840 bytes at 16-bit while the context is inside the window.

ContextKV cache, one sequence
4K0.14 GB

Computed from the layer, head and window counts in the model's own configuration (OuteAI/Lite-Oute-1-300M), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Lite-Oute-1-300M: common questions

How much VRAM does Lite-Oute-1-300M need?

1.3 GB at FP32, 0.3 GB at FP8 (quantized), 0.2 GB at INT4 (quantized). All of those sit under 6 GB, the smallest capacity this page reasons about, so VRAM is not what limits where this model runs. The 1.1 GB of weights plus inference overhead is the whole requirement.

Can Lite-Oute-1-300M run in 16-bit instead of FP32?

Yes. Its published weights are FP32, 1.1 GB, or 1.3 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 0.6 GB, or 0.7 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.

How many copies of Lite-Oute-1-300M fit on one RTX 3070?

5, by VRAM alone. That card carries 8.0 GB and one copy needs 1.3 GB at FP32, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 5 copies is not 5 times the requests served.

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

OuteAI models

Alternatives at this size

Other models for text-generation within about a third of Lite-Oute-1-300M's 300M parameters, from other model lines.

More on Lite-Oute-1-300M

Related reading: RTX 3070 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.