What runs this LLM?
Pick the model you want to serve. We size it from the released checkpoint and list the cheapest configurations you can rent today that hold it — with the on-demand and serverless rate for each.
1 · Choose a model
2 · What it needs
Qwen3 4B at 16-bit
9.7 GB of VRAM
at short context — measured from the released checkpoint, not estimated from parameter count.
- Model weights
- 8 GB
- KV cachefolded into overhead
- —
- Runtime overhead20% of weights
- 1.6 GB
About this model
- Parameters
- 4B
- Released at
- 16-bit
- Measured weights
- 8 GB
3 · Where to run it
Bookable configurations
Cheapest first, checked against 98 GPU types with live bookable capacity.
| Configuration | Total VRAM | On-demand | Serverless | GPU details |
|---|---|---|---|---|
| 1× NVIDIA Tesla V100 16GB | 16 GB 6.3 GB free | $0.03/hr  Vast.ai | — | See all prices |
| 1× NVIDIA RTX 3080 | 10 GB 0.3 GB free | $0.03/hr Vast.ai | — | See all prices |
| 2× NVIDIA GTX 1660 Super | 12 GB 2.3 GB free | $0.04/hr $0.02/GPU-hr Vast.ai | — | See all prices |
| 1× NVIDIA RTX A2000 | 12 GB 2.3 GB free | $0.04/hr Vast.ai | — | See all prices |
| 1× NVIDIA RTX 3060 | 12 GB 2.3 GB free | $0.05/hr  Theta EdgeCloud | — | See all prices |
| 2× NVIDIA GTX 1080 | 16 GB 6.3 GB free | $0.06/hr $0.03/GPU-hr Vast.ai | — | See all prices |
| 1× NVIDIA GTX Titan X | 12 GB 2.3 GB free | $0.06/hr Vast.ai | — | See all prices |
| 1× NVIDIA Titan Xp | 12 GB 2.3 GB free | $0.06/hr Vast.ai | — | See all prices |
Showing the 8 cheapest. Model weights plus 20% for runtime overhead, from measured checkpoint sizes; a stated context length adds its KV cache on top. Each price is the cheapest bookable rate for that exact instance size, for the whole configuration — the cheaper of the two is highlighted and orders the table. A ×N figure is total VRAM across N cards and makes no claim about interconnect throughput.
How this is worked out
Weight sizes are measured from the actual checkpoint files on Hugging Face — never derived from parameter count, which gets quantized releases wrong. On top of the weights we assume 20% for activations, CUDA context and allocator slack. Stating a context length adds its KV cache explicitly, computed only for architectures whose cache shape the config states unambiguously.
A configuration that holds the weights and cache but not that full margin is marked as a tight fit rather than hidden — it will load, and may well run at batch size one, but expect trouble under load.
Prices are the cheapest bookable rate for that exact instance size, refreshed with the rest of the catalog.