On this page · 8 sections
Summary. At CES 2026, NVIDIA CEO Jensen Huang confirmed the Vera Rubin NVL72 is in full production, with volume ramping through the second half of 2026. NVIDIA says the Rubin GPU delivers up to 5x the inference performance and 10x lower cost per token than Blackwell, built from six new chips including a 288GB HBM4 Rubin GPU. AWS, Google Cloud, Microsoft, and Oracle Cloud are among the first to deploy Rubin-based instances. The counterintuitive part for a FinOps lead: better silicon does not automatically cut your bill. GPU supply stays tight, AWS raised EC2 Capacity Blocks for ML pricing by about 15% in early 2026, and Gartner forecasts $2.59 trillion in AI spending in 2026. On-demand GPUs still run $3 to $30-plus per hour. This article separates the hardware story from the budget story, and gives you the moves that actually control spend as Rubin lands.
The headline is real: Rubin is a large generational jump. The trap is assuming the price-performance gain flows straight to your invoice. It does not, at least not first, and understanding why is the difference between a budget that holds and one that blows.
What Rubin actually is
Vera Rubin is NVIDIA's next data-center architecture, built through what the company calls extreme co-design across six new chips: the Vera CPU, the Rubin GPU, the NVLink 6 switch, the ConnectX-9 SuperNIC, the BlueField-4 DPU, and the Spectrum-6 Ethernet switch, per NVIDIA's newsroom. The Rubin GPU carries 288GB of HBM4 memory and delivers 50 PFLOPs of NVFP4 inference, about 5x Blackwell, according to Tom's Hardware.
The headline efficiency claim is up to 10x lower cost per token than Blackwell. Huang confirmed the NVL72 is in full production during his CES keynote, as DCD reported. The rack is 100% liquid-cooled and cuts installation from about two hours on Blackwell systems to five minutes. First cloud deployers include AWS, Google Cloud, Microsoft, and OCI, alongside NVIDIA Cloud Partners such as CoreWeave, Lambda, Nebius, and Nscale.
| Dimension | Blackwell | Vera Rubin NVL72 |
|---|---|---|
| Inference performance | Baseline | Up to 5x |
| Cost per token | Baseline | Up to 10x lower |
| GPU memory | HBM3e generation | 288GB HBM4 |
| Cooling | Mixed | 100% liquid, fanless |
| Rack install time | About 2 hours | About 5 minutes |
| Cloud availability | Now | Ramping H2 2026 |
Why your bill may still rise first
Here is the disconnect. A 10x improvement in cost per token is a per-unit efficiency figure at the silicon level. Your invoice is set by market price and how much you consume, and both are moving against you in 2026.
Supply is the first pressure. Demand for AI compute outruns available capacity, and providers price accordingly. AWS raised EC2 Capacity Blocks for ML by roughly 15% in early 2026, reflecting tighter GPU supply, as Amplix documented. New silicon does not instantly relieve that: Rubin ramps through H2 2026, and early capacity commands a premium, not a discount.
Consumption is the second. Better price-performance tends to increase usage, not shrink budgets, because teams run bigger models and more agents once each token is cheaper. By June 2026, many organizations had already burned through 3x their entire annual AI budget, and 30-50% of GPU resources are wasted through over-provisioning, per FinOps analyses from Finout and nOps. Efficient hardware that fuels more usage can raise a bill even as cost per token falls.
The FinOps moves that actually matter
Rubin is a reason to tighten cost discipline now, not to relax it. These are the levers with the biggest effect on a GPU-heavy budget.
| Purchase model | Discount vs on-demand | Commitment |
|---|---|---|
| On-demand ($3-$30+/hr) | Baseline | None |
| Savings Plans / Reserved | 30-72% | 1-3 years |
| Committed-use contracts | 24-75% | 1-3 years |
| Spot / preemptible | 70-90% | Interruptible |
Four practices carry most of the value. Layer commitments strategically: cover your steady baseline with reserved or committed-use contracts for 30-72% off, and leave burst capacity on-demand. Move interruptible, checkpointed workloads such as training and batch inference to spot for 70-90% savings. Attack over-provisioning directly, since eliminating idle GPUs recovers the 30-50% that is routinely wasted. And stress-test the plan: finance leaders should model AI infrastructure at 110-125% of current GPU pricing to absorb further increases. We detail this in our FinOps playbook for AWS, Azure, and GCP and guide to cutting cloud spend.
When to wait for Rubin, and when not to
Rubin's efficiency is worth timing for some workloads and irrelevant for others. If you run large, sustained inference or training where cost per token dominates, plan a path to Rubin-based instances as capacity opens through H2 2026, and avoid signing long, inflexible commitments on older silicon at peak prices. If your GPU usage is modest or spiky, the generational jump matters less than fixing over-provisioning and using spot today. Do not stall a shipping product waiting for hardware; the biggest near-term savings come from FinOps hygiene, not from the next chip. Our analysis of Vera Rubin cloud instances goes deeper on the workload fit.
India-specific considerations
For Indian enterprises, the currency and capacity angles sharpen the decision. GPU capacity in India-region data centers is scarcer than in US regions, so committed-use contracts and India-region availability matter as much as the headline rate. Budget in rupees at 110-125% of today's pricing, because a weakening rupee against a dollar-priced GPU market can erase a hardware efficiency gain. For data that must stay in India under the Digital Personal Data Protection Act, 2023 (DPDP), verify Rubin-based instance availability in an Indian region before assuming you can use it; a cheaper token in a US region is no help if the data cannot leave the country. Spot and right-sizing deliver savings you can capture now, without waiting on regional Rubin rollout.
FAQ
How eCorpIT can help
eCorpIT (eCorp Information Technologies Private Limited, founded 2021, Gurugram) runs GPU FinOps programs that keep AI budgets predictable. Our senior-led teams, working as partners of AWS, Microsoft, and Google, right-size GPU workloads, structure committed-use and spot strategies, and model budgets against realistic price increases so a hardware transition like Rubin becomes a plan, not a surprise. We align data-residency choices with DPDP Act requirements for Indian workloads. To review your GPU spend, contact us.
References
_Last updated: July 13, 2026._