Does it fit?
Break total memory into weights, KV cache, and runtime workspace instead of relying on parameter count alone.
Open-model deployment planner
Turn model size, quantization, context, and concurrency into a practical GPU plan—before you reserve a machine.
Start with an open model, then adjust the details that actually change memory: precision, context length, concurrent sequences, and tensor-parallel GPU count.
Includes 15% operating headroom for the selected runtime profile.
Carry this workload estimate into the product and review currently available GPU options.
Sample planning rates only—not live Flatkey quotes or availability.
vllm serve YOUR_COMPATIBLE_QUANTIZED_MODEL_ID --tensor-parallel-size 1 --max-model-len 8192 --quantization YOUR_MATCHING_BACKEND4-bit is a memory assumption, not a checkpoint choice. Replace both placeholders with a compatible quantized artifact and its vLLM backend.
Curated model cards keep parameter counts, context limits, architecture notes, and source links separate from the calculator itself.
Explore the full model directory →Break total memory into weights, KV cache, and runtime workspace instead of relying on parameter count alone.
Match the per-device estimate to practical GPU profiles and keep enough headroom for stable serving.
Carry context, cache precision, and parallelism into a command template. Quantized plans still need a compatible checkpoint and backend.
Use the hardware profiles and field guides to understand why the estimate changes—and what to validate before renting a machine.
See which starter models fit across 16 GB to 192 GB hardware envelopes.
9 profiles →Guide 01Break memory into weights, KV cache, runtime workspace, and operating headroom.
Read guide →Guide 02Understand how active tokens, concurrent sequences, and cache precision use memory.
Read guide →