Alpha
Contact
Support · NVIDIA Nemotron 3 Nano Omni

Will it last?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 60/100

This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

Common problems & fixes

Typical pitfalls for a small multimodal hybrid Mamba-Transformer MoE are multimodal preprocessing and processor-config mismatches, kernel-to-engine version mismatches for the Mamba-2 and MoE layers, the wrong repo path because of the missing "NVIDIA-" prefix, and revision drift on download. Match engine and kernel versions to the documented stack, confirm the processor config, pin the revision and verify checksums. The list is not exhaustive.

Versions, changelog & cadence

Nemotron 3 Nano Omni was released on 2026-04-20 (BF16; FP8 and NVFP4 followed on 2026-04-24, and build.nvidia.com on 2026-04-28) on the verified nvidia org. There is no single-checkpoint changelog; the Hugging Face revision hash is the anchor, so pin it. The licence version line is "v. March 9, 2026" while its web page shows an April 2, 2026 release date.

Security / vulnerability disclosure

NVIDIA maintains a general corporate product-security reporting path (nvidia.com/en-us/security/). No model-specific vulnerability-disclosure policy for Nemotron is confirmed, so route model-level issue reports through the Hugging Face and GitHub org presence.

Community & support channels

Support is the NVIDIA open-model presence: the nvidia Hugging Face org (model discussions), the NVIDIA-NeMo GitHub organisation (the omni3 recipe and NeMo Guardrails), and the NVIDIA/garak repository for red-team and safety-tooling questions.

Tracked known issues

The recurring caveats are the weaker open-data posture and unadvertised recipe, the absence of a model-level safety evaluation over the multimodal input path, and the two dates on the licence page. Track them against your own control stack and red-team, as no published issue tracker covers them.

How this scores

The ownership factor this domain covers, drawn from the one entry record.

2

TransparencyDo you know what it is: weights, training, behaviour, and legible terms?

Moderate

open_weights, not open_weights_recipe. The weights are ungated and inspectable and there is a model card and licence, but the card does not carry the family's open-data/recipe self-description, links only an image-training dataset, and the recipe that exists surfaces only the public subset. The weights are visible but the data and full recipe are not clearly released, which is the anchor for moderate, not strong.

How this scores (AOI sub-dimensions)
Provenance3/5how well we can trace and verify what went into the modelThe verified nvidia org on Hugging Face distributes ungated safetensors with official BF16 / FP8 / NVFP4 variants and a clear canonical source (checklist ~4/8).
Governance3/5how accountable and well-documented the publisher isNVIDIA is a reputable, accountable publisher with a verified hub presence, an active release cadence and a general corporate security-reporting path.
What this means for adoptionNano Omni gives you a small, portable, natively multimodal model under a clean irrevocable licence, and self-hosting keeps your data and rights yours, so data control is strong. Ownership stays partial for three reasons. Use-and-modify is moderate (a non-OSI third licence and a public-subset-only recipe). Transparency is moderate (open_weights, not open_weights_recipe: the card does not release the data or advertise the recipe). Reliability is moderate (no model-level safety evaluation over a wider multimodal misuse surface). Self-host, assemble the multimodal guard stack, red-team the video/audio/image input path, and keep a copy of the licence version the weights were downloaded under.

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.

Model cardread2026-11-19
The Nemotron 3 Nano Omni model card is on the verified nvidia HF org (nvidia/Nemotron-3-Nano-Omni-30B-A3B-Reasoning-BF16, no "NVIDIA-" prefix).
Licenceread2026-11-19
The NVIDIA Open Model Agreement (v.
Documentationread2026-08-03
A training recipe for Nano Omni exists in the NeMo repo (github.com/NVIDIA-NeMo/Nemotron docs/nemotron/omni3, SFT then RL).
Model cardread2026-11-19
There is no dedicated model-level safety evaluation for Nano Omni; safety is post-training data curation only, over a wider multimodal (video/audio/image) misuse surface.
Documentationread2026-11-19
The nvidia org on Hugging Face is verified, and the Nano Omni weight repo is ungated safetensors with official BF16, FP8 and NVFP4 variants.
Terms of serviceread2026-08-03
NVIDIA NIM is self-hosted deployment tooling ("data never leaves your secure enclave"), and the Nano Omni card links a TensorRT-LLM deploy cookbook, so self-hosting supports data control and NVIDIA is not an AOI inference-provider entry.
Third-party analysisread2026-08-03
NVIDIA is not a signatory to the EU GPAI Code of Practice (EU signatory list), and no NVIDIA training-content summary or copyright policy for Nemotron is published.