← Back to Blog

NVIDIA Nemotron-Labs-TwoTower 60B Diffusion Model: 2.42x Throughput at 98.7% Quality — Coding Cost Math

By Eric Bush · July 2, 2026 · 9 min read

Close-up of a graphics processing unit with silver fan blades

The Release

NVIDIA published Nemotron-Labs-TwoTower on July 1, 2026 — an open-weight diffusion language model built on a novel two-tower architecture. The context tower is a frozen Nemotron-3-Nano-30B-A3B autoregressive backbone; the denoiser tower is trained fresh and joins the frozen backbone via layer-aligned cross-attention and state seeding.

Reported on 2×H100 in BF16: 98.7% of the AR baseline's quality, with 2.42x higher generation throughput at γ=0.8 and block size S=16. Total parameters ~60B, active parameters roughly 3B per tower per token. Backbone was pretrained on ~25T tokens; denoiser was trained on ~2.1T. It supports three decoding modes: diffusion, simulated AR, and pure AR.

Why Two Towers

Standard diffusion language models pay a training tax: the full model has to learn both context understanding and noise refinement. NVIDIA's insight is that a well-trained autoregressive model already knows context — freezing it means you keep 25T tokens of pretraining "for free" and only train the smaller denoiser (which is a much cheaper training run).

The practical consequence: 98.7% of the AR baseline's quality with 2.4x the throughput. Small quality gap, big cost gap. For self-hosted coding workloads that are throughput-bound (batch code generation, background agents, doc generation across large repos), this is a real economic shift.

Cost Math: Self-Hosted Inference

Start with a realistic self-hosted setup: 2×H100 rented at $2.20/GPU/hour on-demand ($4.40/hour combined). Assume 90% utilization, 24/7. Monthly hosting cost:

  • $4.40/hour × 24 × 30 × 0.9 utilization = ~$2,850/month

Baseline AR throughput on Nemotron-3-Nano-30B: roughly 200 tokens/sec sustained on this hardware. Monthly output at 90% utilization:

  • 200 × 3600 × 24 × 30 × 0.9 = ~4.66B tokens
  • Cost per million output tokens: $0.61

With TwoTower at 2.42x throughput on the same hardware:

  • ~484 tokens/sec sustained → ~11.28B tokens/month
  • Cost per million output tokens: $0.25

A 59% drop in effective per-token cost on the same hardware, with quality only 1.3% below the baseline. For teams already self-hosting, this is a straightforward win. For teams comparing to hosted APIs, the picture is more nuanced.

TwoTower Self-Hosted vs Hosted APIs

Option Cost / 1M Output Quality Tier Break-Even
TwoTower self-hosted (2×H100) $0.25 98.7% of 30B AR ~5M output tokens/day
DeepSeek V4-Flash API $0.14 Mid-tier coding n/a
Claude Sonnet 5 (promo) $10.00 Frontier n/a
Claude Fable 5 $50.00 Frontier+ n/a

DeepSeek's API is still cheaper on paper — but it comes with rate limits, data-residency questions, and no ability to customize the model. TwoTower self-hosted gives you a mid-tier model at 1.8x DeepSeek's cost with full control.

When Self-Hosting TwoTower Makes Sense

Break-even for a $2,850/month hosting bill against DeepSeek V4-Flash's $0.14/M is:

  • $2,850 / $0.14 = ~20.4M tokens/month gap must be closed by not paying API prices
  • You need to be generating at least 300–400M tokens/month for self-hosting to beat the cheapest API on cost alone

That's a real threshold for indie teams — most solo developers won't hit it. But for AI coding agencies, ML platform teams, or anyone running 24/7 background agents that generate code across large repos, 300M+ tokens/month is normal. Add in data privacy and customization value, and TwoTower is a real alternative to hosted mid-tier APIs.

Caveats

  1. Quality gap on coding-specific benchmarks. NVIDIA's 98.7% quality claim is against a general-purpose evaluation set. Coding tasks are often the sharpest quality differential in language models — until independent SWE-bench numbers land, budget for a 5–10% quality drop, not 1.3%.
  2. Diffusion decoding needs latency tuning. The 2.42x throughput is a batch number. For single-user interactive coding, latency per token matters more than throughput per second, and diffusion sampling can be tricky to tune.
  3. Hardware constraints. 60B total params requires 2×H100 minimum for BF16. Cheaper GPU tiers (A100, L40S) won't hold the weights comfortably.
  4. Open weight ≠ open training. The weights are released; the training recipe for the denoiser is only partially documented. If you plan to fine-tune, reserve budget for figuring out the pipeline.

Recommendation

  • If you're already self-hosting a mid-tier open model at 300M+ tokens/month, migrate a test workload to TwoTower and measure both cost per million and quality against your current baseline.
  • If you're on hosted APIs and your monthly bill is under $2K, TwoTower self-hosted won't beat DeepSeek or Cerebras APIs on cost — stay hosted.
  • If you value control (data residency, custom fine-tunes, air-gapped deployment), TwoTower's economics at 300M+ tokens/month are hard to ignore.

Want to calculate exact costs for your project?

Frequently Asked Questions

What is Nemotron-Labs-TwoTower?

An open-weight diffusion language model released by NVIDIA on July 1, 2026. It uses a two-tower architecture: a frozen 30B autoregressive backbone paired with a trained diffusion denoiser tower, connected via layer-aligned cross-attention.

How much faster is TwoTower than a standard autoregressive model?

NVIDIA reports 2.42x throughput at γ=0.8, block size 16, on 2×H100 in BF16, while retaining 98.7% of the AR baseline's quality on their general evaluation set.

What's the cost per million output tokens self-hosted?

On 2×H100 rented at $2.20/GPU/hour with 90% utilization, roughly $0.25 per million output tokens — about 59% cheaper than the same hardware running the pure AR baseline.

Should I switch from DeepSeek API to TwoTower self-hosted?

Only if you're generating at least 300M output tokens per month and value data privacy or model customization. DeepSeek V4-Flash's $0.14/M API pricing beats TwoTower's $0.25/M self-hosted on pure cost.

Does TwoTower work on cheaper GPUs?

Not comfortably. 60B parameters in BF16 need at least 2×H100 to run at published throughput. A100 80GB pairs can run it but with substantial quality/speed tradeoffs, and consumer cards can't fit the weights at all.