Can you run it?
This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Install & run
Download the ungated safetensors from the verified nvidia org on Hugging Face and serve with vLLM, SGLang, Ollama, llama.cpp or NVIDIA NIM. Pick the variant to fit your hardware (Nano or Super), pin the exact revision, and verify checksums before loading.
Hardware & VRAM requirements
Nano (30B / 3.5B active) runs on modest single-GPU hardware, and Super (120B / 12B) is a mid-tier multi-GPU target. Official BF16, FP8 and NVFP4 quantizations are published for each. Size against the specific variant; exact per-GPU VRAM is not stated.
Serving stacks
Broad support: vLLM, SGLang, Ollama, llama.cpp and NVIDIA's own NIM self-hosted microservices. NIM runs on your own infrastructure, so data stays in your enclave. It is deployment tooling and not a hosted provider.
Safe-deployment controls & Deployment Ceiling
Deployment Ceiling: T3 (bounded autonomous), conditional. No model-level safety evaluation is published, so the deployer assembles the controls. NVIDIA ships the pieces at the family level: a downloadable guard classifier (Nemotron-3-Content-Safety), the NeMo Guardrails toolkit for input, output and action rails, and the garak red-team scanner.
Reaching T2 needs the guard classifier plus input/output rails. T3 additionally needs deterministic action limits, a kill switch and red-team sign-off. Run garak (or equivalent) for your own use case, and note that the guard-classifier scores are NVIDIA self-reported. The irrevocable licence carries no field-of-use restriction. Complete the pre-deployment gate in the safe-deployment playbook.
Available quantizations
NVIDIA publishes official BF16, FP8 and NVFP4 variants for both models alongside the base safetensors, so the low-precision path is first-party.
Fine-tuning & adaptation
Runnable training and fine-tuning recipes are released on GitHub (Pretrain -> SFT -> RL), and the post-training data is CC-BY-4.0, so adaptation is accessible. The recipes "train exclusively on the open-sourced subset of training data", so results differ from the tech-report benchmarks that used additional proprietary data.
API / OpenAI-compatible integration
Serve behind vLLM/SGLang or NVIDIA NIM for OpenAI-compatible endpoints. A hosted build.nvidia.com preview API exists for evaluation only: it does not store content at session end, yet reserves use of content "to improve NVIDIA products and services, including AI models".
How this scores
The ownership factors this domain covers, drawn from the one entry record.
ReliabilityIs it reliable and good enough for the job?
ModerateOperational is strong (4: broad serving, official quantizations, a small portable Nano), but safety is only 3: there is no published model-level safety evaluation or independent red-team, so misuse control is a gap you must fill yourself with the downloadable guard stack. Under the ownership rule a safety score of 3 caps this factor at moderate, however capable the models are.
Doesn't extract your dataDoes running it keep your knowledge and data yours?
StrongSelf-hosted via NIM, the weights and inference run on the deployer's own infrastructure and data never leaves the enclave. The licence claws back no rights: the grant is explicitly irrevocable and terminates only on the licensee's own IP litigation.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.