Alpha
Contact
Use · NVIDIA Nemotron 3 Ultra

Is it good enough?

Ownership levelSubstantialnone·limited·partial·substantial·fullAnalytical input C ยท 63.6/100

This page is a projection of the one entry record, the Reliability factor that Use 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

Capabilities & modalities

Ultra covers frontier-scale reasoning, chat, complex agentic workflows and long-context analysis. It is text in / text out. The architecture is a Mamba2-Transformer hybrid Latent Mixture-of-Experts with Multi-Token Prediction, built for efficiency at very long context and large scale.

Context window & long-context behaviour

Ultra supports up to 1M tokens. OneHill has not independently measured effective long-context recall, and the released recipe notes the 1M-context data is not open, so treat the maximum as an architectural ceiling rather than a verified working depth.

Language coverage

English and code are primary, with supported multilingual contexts. Per-language model depth is not exhaustively documented.

Function / tool calling

Ultra is positioned for complex agentic workflows. Expose tools through your serving layer's function-calling API, and, given the autonomous deployment ceiling, allow-list tools and bound their effects with NeMo Guardrails action rails.

How this scores

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

3

ReliabilityIs it reliable and good enough for the job?

Moderate

Operational is 3 (runs on mainstream stacks with official quantizations, but is a multi-node-only 550B model with no small-variant drop-in) and safety is 3 (no dedicated model-level safety evaluation, so misuse control is a gap you must fill yourself). Under the ownership rule, a safety score of 3 caps this factor at moderate.

How this scores (AOI sub-dimensions)
Operational3/5how practical it is to run, serve and maintain in productionRuns on mainstream stacks (vLLM, SGLang, NVIDIA NIM) with official BF16 / NVFP4 quantizations and documented hardware expectations.
Safety3/5whether misuse risks are evaluated and guardrails are providedA safety-tuned release (post-training safety data plus keyword/regex filtering) with the downloadable family guard stack - the Nemotron-3-Content-Safety classifier, the Apache-2.0 NeMo Guardrails toolkit and the Apache-2.0 garak scanner - genuinely attributable to Ultra.
What this means for adoptionUltra is the one Nemotron 3 release whose ownership reaches substantial: the OpenMDW 'deal without restriction' grant makes use-and-modify strong, self-hosting via NIM makes data control strong, and the open_weights_recipe transparency is strong - so you can use it, see it and keep your data outright. It stops short of full because reliability is only moderate: there is no dedicated model-level safety evaluation, and at 550B / 55B active it is a multi-node deployment. Self-host, assemble the downloadable guard stack, red-team for your own use case, and treat EU systemic-risk status as unresolved until NVIDIA discloses training compute.

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-08-03
Nemotron 3 Ultra model card on the verified nvidia HF org: 550B total / 55B active; Mamba2-Transformer hybrid LatentMoE + MTP; up to 1M context; ~20T training tokens; ungated safetensors with BF16/NVFP4 variants; card states "open models with open weights, training data, and recipes"; licence tag openmdw-1.1.
Licenceread2026-08-03
OpenMDW License Agreement v1.1, read: "permission is hereby granted, free of charge, to deal in the Model Materials without restriction, including under all copyright, patent, database, and trade secret rights"; "Model Materials" covers weights, data, documentation and software.
Documentationread2026-08-03
Ultra training recipe at github.com/NVIDIA-NeMo/Nemotron (docs/nemotron/ultra3, Pretrain -> SFT -> MOPD -> Quant), read: described as "a representative single pass"; the "intermediate checkpoints it depends on have not been open-sourced" and the "1M-context LC phase is not included because its data ...
Technical_reportread2026-08-03
Nemotron 3 White Paper (arXiv 2512.20856), read: Ultra is a Mamba2-Transformer hybrid LatentMoE, up to 1M context.
Model cardread2026-08-03
Safety, read: no dedicated model-level safety evaluation for Ultra (white paper safety section is a contributor list; safety appears only as post-training data curation - Nemotron Content Safety v2 + Gretel refusal data + keyword/regex filtering).
Documentationread2026-08-03
Verified nvidia org on Hugging Face; the Ultra weight repo is ungated safetensors with published BF16/NVFP4 quantization variants.
Terms of serviceread2026-08-03
NVIDIA NIM is self-hosted deployment tooling ("data never leaves your secure enclave"), so NVIDIA is not an AOI inference-provider entry and self-hosting Ultra supports data control.
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 was located.