Two customer paths. Both end with a concrete hardware recommendation and a total price.
You want to self-host a frontier open-source model without paying cloud GPU bills month after month. You're cost-sensitive. You want something that actually works — not enterprise overhead.
You're looking at the three models from our AI page — all between 284B and 753B parameters. All of them need 341–904 GB of GPU memory.
You want to self-host a frontier open-source model without paying cloud bills forever. The minimum hardware that can run any of the three models on our page.
All three listed models need 341–893 GB of GPU memory. A single 8×H200 server has 1,128 GB — enough for any of them, with breathing room for inference overhead. There is no cheaper path to running these specific models on your own hardware.
If you outgrow one server, add a second H200 system and connect them over InfiniBand for ~2,256 GB total.
You need serious capacity — multiple models, multiple teams, room to grow. Downtime costs you money. You're thinking in years, not months. Cloud GPU bills are becoming significant.
You need to serve multiple models or multiple teams, can't afford downtime, and expect your workloads to grow. One rack handles it all.
20 TB of pooled GPU memory lets you run all three listed models simultaneously — each model gets 600–900 GB of headroom, still leaving 17+ TB for other workloads. NVLink at 72-GPU scale is true datacenter clustering: models can span all 72 GPUs with no software tricks, delivering maximum throughput per dollar at this scale.
Most organizations configure two NVL72 racks: one production, one for training and evaluation. Your team can fine-tune on new data without touching the serving rack.
The GB300 NVL72's 72 GPUs are connected by NVLink Switch — a dedicated high-speed fabric operating at ~900 GB/s between any two GPUs. All 72 GPUs share one memory address space. A 753B parameter model can be split across all 72 chips seamlessly, as if they were one massive GPU.
Compare this to buying 72 separate RTX 5090s and networking them: you'd get 72 isolated 32 GB pools, connected by Ethernet or InfiniBand at 10–100× lower bandwidth. Software (tensor parallelism) can coordinate them, but each inter-GPU data transfer crosses a slow link. For large-model inference, latency multiplies with each network hop.
| Metric | GB300 NVL72 (NVLink) | 72× RTX 5090 (networked) |
|---|---|---|
| Total memory | 20 TB (one pool) | 2,304 GB (72 isolated pools) |
| GPU-to-GPU bandwidth | ~900 GB/s | 25–400 GB/s (network) |
| Memory sharing | Hardware-level, seamless | Software coordination required |
| Inference latency | Low — no network hop | Higher — crosses interconnect |
| Management overhead | One system | 72 nodes to manage |
| Approximate cost | $3.7M–$6.5M | ~$173K (but can't run 744B+ models) |