Open-weight #6 OpenRouter overall #6
NVIDIA · Mamba-2 + latent MoE hybrid

Deploy Nemotron 3 Ultra 550B-A55B

NVIDIA's open reasoning and orchestration flagship with a million-token context.

Total / active550B / 55B
Context ceiling1M
Planning floor4×192GB
Resident weights~329GB
RuntimevLLM latest
LicenseOpenMDW 1.1
Practical target 4x B200-class GPUs or 8x 80GB H100-class GPUs

NVIDIA lists 4x B200/GB200-class GPUs or 8x H100s as the minimum supported deployment envelope.

Seven runbooks for Nemotron 3 Ultra 550B-A55B

Every card opens a setup sequence tailored to this model's runtime and memory floor.

RunPod Multi-GPU

4x B200-class GPUs

Fits one high-memory node, but needs tensor/expert parallel configuration.

Serverless vLLM for smaller models; dedicated Pods for multi-GPU models Open runbook →
Vast.ai Multi-GPU

4x B200-class GPUs

Fits one high-memory node, but needs tensor/expert parallel configuration.

A Docker template attached to a matching GPU marketplace offer Open runbook →
Lambda Multi-GPU

4x B200-class GPUs

Fits one high-memory node, but needs tensor/expert parallel configuration.

An On-Demand Cloud instance, or a 1-Click Cluster for larger deployments Open runbook →
AWS Multi-GPU

SageMaker/HyperPod GPU capacity with at least 4x B200-class accelerators

Fits one high-memory node, but needs tensor/expert parallel configuration.

SageMaker HyperPod with a Hugging Face model source and vLLM/SGLang worker Open runbook →
Google Cloud Multi-GPU

Vertex AI GPU deployment with at least 4x B200-class accelerators

Fits one high-memory node, but needs tensor/expert parallel configuration.

A custom vLLM container in Vertex AI, backed by Artifact Registry Open runbook →
Azure Multi-GPU

Azure ML GPU deployment with at least 4x B200-class accelerators

Fits one high-memory node, but needs tensor/expert parallel configuration.

Azure Machine Learning online endpoint with a bring-your-own vLLM/SGLang container Open runbook →
Oracle Cloud Multi-GPU

OCI GPU shape with at least 4x B200-class accelerators

Fits one high-memory node, but needs tensor/expert parallel configuration.

OCI Generative AI imported models when supported; OKE vLLM otherwise Open runbook →

Prove the runtime before chasing max context

Start at 32,768 tokens, confirm all GPUs are visible, load the official chat template, and send a short request. Increase context and concurrency only after recording free VRAM.

What is measured vs estimated

Rank comes from observed OpenRouter ordering. Parameters, context, license, and runtime notes come from the linked model card. The 4×192GB hardware figure is a planning floor with runtime and KV-cache headroom.

Hand this runbook to Claude Code or Codex

Open a terminal in the repository where you want the deployment files, start claude or codex, then paste this prompt. It asks the agent to verify sources and stop before it creates billable infrastructure.

Deployment prompt
Prepare a reproducible deployment project for Nemotron 3 Ultra 550B-A55B (nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-NVFP4); ask me to choose a provider before writing provider-specific infrastructure. Use this guide as the starting context: https://www.getflops.ai/models/nemotron-3-ultra-550b-a55b. Use a planning floor of 4x 192GB GPUs, 450GB storage, vllm latest, and an initial context limit of 32768 tokens. Open every linked primary source and flag any mismatch instead of guessing. Create a deployment folder containing README.md, .env.example with no secrets, a pinned start script or infrastructure manifest, and smoke-test.sh. Make the endpoint OpenAI-compatible where the runtime supports it. Run local/static validation, estimate the billable resources, and stop before provisioning paid infrastructure until I approve.
Guardrails included No secrets in files · verify primary docs · approval before spend

Verify before provisioning

Research checked 2026-07-27. Provider inventory and inference-engine support can change faster than this page.