Every open model in our directory, ranked by how well it runs on NVIDIA Jetson Orin Nano Super Developer Kit (8GB) at 4-bit. Grades weigh whether the model fits in memory and how fast it should run.
NVIDIA Jetson Orin Nano Super Developer Kit has 8.0 GB of VRAM, enough to run 178 of the 298 open models we track at 4-bit. The largest that still fits well is Holo4-35B-A3B (35B), and the top-rated is Mellum2.1 at about 40 tok/s.
178 of 298 models run comfortably on NVIDIA Jetson Orin Nano Super Developer Kit.
See full NVIDIA Jetson Orin Nano Super Developer Kit specs and pricingThe top models this device can run at 4-bit, ranked by fit and speed.
| Model | Grade | Speed | VRAM |
|---|---|---|---|
| Mellum2.1JetBrains | SS | 40.4 tok/s | 2.0 GB |
| Holo4-35B-A3BHcompany | SS | 35.1 tok/s | 2.3 GB |
| LFM2.5-8B-A1BLiquid AI | AA | 28.3 tok/s | 2.9 GB |
| Qwen3-30B-A3BAlibaba | AA | 15.2 tok/s | 5.4 GB |
| Apertus 8BEPFL, ETH Zurich, CSCS | AA | 15.2 tok/s | 5.4 GB |
| BolmoAi2 | AA | 164.2 tok/s | 0.5 GB |
| Llama 3 8B InstructMeta | AA | 14.5 tok/s | 5.7 GB |
| LensVLM-9BApple | BB | 13.7 tok/s | 6.0 GB |
| Carnice-9b for Hermes agentkai-os | BB | 13.7 tok/s | 6.0 GB |
| PersonaPlex 7BNVIDIA | BB | 17.1 tok/s | 4.8 GB |
| Llama 2 7B ChatMeta | BB | 17.1 tok/s | 4.8 GB |
| Gemma 4 E2B ITGoogle | BB | 22.1 tok/s | 3.7 GB |
Mellum2.1JetBrains | 12B(2.5B active) | SS | 40.4 tok/s | 2.0 GB | |
Holo4-35B-A3BHcompany | 35B(3B active) | SS | 35.1 tok/s | 2.3 GB | |
LFM2.5-8B-A1BLiquid AI | 8.3B(1.5B active) | AA | 28.3 tok/s | 2.9 GB | |
Qwen3-30B-A3BAlibaba | 30B(3B active) | AA | 15.2 tok/s | 5.4 GB | |
Apertus 8BEPFL, ETH Zurich, CSCS | 8B | AA | 15.2 tok/s | 5.4 GB | |
BolmoAi2 | 0B | AA | 164.2 tok/s | 0.5 GB | |
| 8B | AA | 14.5 tok/s | 5.7 GB | ||
LensVLM-9BApple | 9B | BB | 13.7 tok/s | 6.0 GB | |
| Ad | |||||
| 9B | BB | 13.7 tok/s | 6.0 GB | ||
PersonaPlex 7BNVIDIA | 7B | BB | 17.1 tok/s | 4.8 GB | |
Llama 2 7B ChatMeta | 7B | BB | 17.1 tok/s | 4.8 GB | |
Gemma 4 E2B ITGoogle | 2B | BB | 22.1 tok/s | 3.7 GB | |
VibeThinker-3BWeiboAI | 3B | BB | 21.5 tok/s | 3.8 GB | |
MiniCPM5-2Bopenbmb | 2.52B | BB | 17.8 tok/s | 4.6 GB | |
Youtu-Parsing-Omnitencent | 5.33B | BB | 12.9 tok/s | 6.4 GB | |
Mistral 7B InstructMistral AI | 7B | BB | 12.8 tok/s | 6.4 GB | |
| Ad | |||||
LFM2.5-2.6BLiquid AI | 2.69B | BB | 16.8 tok/s | 4.9 GB | |
Gemma 4 E4B ITGoogle | 4B | BB | 11.9 tok/s | 6.9 GB | |
Gemma 3 4B ITGoogle | 4B | BB | 11.9 tok/s | 6.9 GB | |
| 81.29B(3B active) | CC | 9.6 tok/s | 8.5 GB | ||
North Mini CodeCohere | 30B(3B active) | DD | 9.8 tok/s | 8.4 GB | |
Nemotron 3 Nano OmniNVIDIA | 30B(3B active) | DD | 9.6 tok/s | 8.5 GB | |
Qwen3.6 35B-A3BAlibaba | 35B(3B active) | DD | 9.6 tok/s | 8.5 GB | |
Qwen3.5-35B-A3BAlibaba | 35B(3B active) | DD | 9.6 tok/s | 8.5 GB | |
| Ad | |||||
Llama 2 13B ChatMeta | 13B | DD | 9.7 tok/s | 8.5 GB | |

Model Compatibility
Use the calculator to weigh this device against any other, model by model, with speed and fit scores.
Straight answers to the questions we hear most often.
Can't find what you're looking for? Book a Discovery Call
Mellum2.1 is the highest-rated model that runs on NVIDIA Jetson Orin Nano Super Developer Kit at 4-bit, at about 40 tok/s. In total, NVIDIA Jetson Orin Nano Super Developer Kit can run 178 of the 298 open models we track.
We size each model at 4-bit (Q4_K_M), add the KV cache for its context length and a fixed runtime overhead, then compare that to this device VRAM. Each model is graded on how comfortably it fits and how fast it should run on this card.
It is an estimate of decode speed in tokens per second at 4-bit, based on this device memory bandwidth and each model size. Real speed depends on your runtime, batch size, and context length, so use it to compare models, not as a hard promise.
Lower-bit quantization shrinks a model so more of them fit. These grades already assume 4-bit, which is the common local default. Going below 4-bit can squeeze a larger model in at some quality cost; going above needs more VRAM and may not fit.
Mixture-of-experts models only activate a fraction of their parameters at a time, so their runtime memory is closer to the active size than the headline size. We score fit on the active parameters, which is why some very large models still fit.