Rent a GPU Cluster: Multi-GPU and 8x Node Pricing
Some of the best per-GPU prices on our index are only available if you rent eight GPUs at once. A provider advertises an H100 rate that undercuts everyone, and the fine print says the smallest thing you can actually rent is a full 8-GPU node, so the real hourly hold on your card is eight times the headline. Most comparison sites quote that per-GPU number without the disclosure. We normalize every price to a per-GPU rate too, because that is the only way to compare providers, but we show the node size wherever the provider publishes it, and say so when it does not. This guide explains how those numbers work and when they are a good deal.
How to rent a GPU cluster without comparing the wrong unit
Start with the job, not the cheapest card row. Decide how many GPUs the job can keep busy, whether those GPUs must share a fast interconnect, and how long the node will run. Then compare four fields for every candidate: the normalized per-GPU rate, the minimum GPU count, the resulting full-node hourly meter, and any commitment or data-transfer terms. Our live GPU pages provide the first two fields from current offers. The fees matrix and provider source links help with the rest, but they are not a substitute for a configuration-specific quote.
If a row says 8x min, multiplying its displayed GPU-hour rate by eight gives the compute-only node meter. It still does not include storage, network services, egress, taxes, or an account-specific contract. A row marked 1× is a published single-GPU offer and should not be compared to an 8x cluster merely because both tables normalize to the same unit. A row with no node size is unknown, not single: check the provider's configuration before you budget for one GPU. For a broad view of full-node and single-GPU providers, start at GPU servers; for workload sizing, use the LLM training picks.
Why providers sell GPUs in blocks of eight
The 8x block is not a pricing gimmick; it is how the hardware is built. Datacenter GPUs like the H100, H200, and B200 ship to providers on baseboards that carry eight GPUs wired together with NVLink, a direct GPU-to-GPU interconnect that is far faster than routing traffic through the host machine. The eight cards share a chassis, power delivery, and network fabric. Carving one GPU out of that node and selling it separately is possible (some providers do, through virtualization), but many simply rent the node as the unit it physically is. That is also why the 8x configuration is what serious training work wants: the whole point of the baseboard is that the GPUs can talk to each other at full speed.
Per-GPU price vs the total node cost
Every price on this site is normalized to dollars per GPU per hour, whatever the node size behind it. That makes an 8x node rate directly comparable to a single-card rate, but it does not make them the same purchase.
Take the cheapest on-demand H100 on our index today: $1.80/hr per GPU. If a rate like that is sold only as an 8-GPU node, your actual meter runs at eight times the per-GPU figure for every hour the node is up, whether your job uses one of the GPUs or all eight. The per-GPU rate tells you whether the price is competitive. The node minimum tells you the size of the check. Both matter, which is why we publish both.
The corollary: a node-only rate is only cheap if you can keep all eight GPUs busy. At 50 percent utilization of the node, your effective per-GPU cost doubles, and a pricier single-card rental would have beaten it.
What the node sizes mean on our tables
On GPU pages and provider pages, the "Node · total per hour" column gives the published GPU count and the total for that node: "8×" means the rate is per GPU and the smallest configuration at that price is an 8-GPU node, while "1×" means the provider publishes a single-GPU configuration. A dash means the provider does not state the count, so the row may still be sold only as a node; confirm the configuration with the provider. Summary tables such as GPU servers mark node-only rates with a badge like "8× min". The multi-GPU node glossary entry covers the term. When two providers show similar per-GPU rates and one is sold as an 8-GPU node, they are different products: one is a card, the other is a cluster with a much larger minimum spend.
NVLink vs PCIe: what you are paying for
Inside a multi-GPU node, the interconnect is the difference between eight GPUs that act like one big accelerator and eight GPUs that happen to share a chassis. Our spec tables carry the interconnect for every card, from NVIDIA's published datasheets: the H100 SXM variant links GPUs at 900GB/s over NVLink. H100 PCIe cards talk to each other over the PCIe Gen5 bus unless the server pairs them with NVLink bridges, which NVIDIA rates at 600GB/s between two cards. A bridged pair is still two cards, not the eight-GPU NVLink baseboard described above. So the form factor alone does not tell you the interconnect; ask the provider whether the PCIe cards you rent are bridged, and in pairs. For workloads that shuttle gradients or model shards between GPUs constantly, the interconnect shows up directly in training throughput. For single-GPU work it is irrelevant, which is why the PCIe cards price lower and are often the better single-card rental. The SXM vs PCIe glossary entry has the details.
Training vs inference: who actually needs the node
Multi-GPU training is the clear case for the 8x node. Distributed training synchronizes gradients across GPUs every step, so interconnect bandwidth directly gates throughput, and NVLink-connected nodes are built for exactly this. If you are training or fine-tuning a model too large for one card, the node is the product you want.
Inference usually is not. Most inference workloads scale by replication: many independent single-GPU workers behind a load balancer, not one tightly coupled 8-GPU system. Unless a single model's weights exceed one card's VRAM even after quantization, single-GPU rentals scale inference more cheaply and with less idle risk than a node.
A single big GPU often beats a slice of a node. If your model fits on one 80GB card, one H100 with no minimum commitment is simpler and usually cheaper than buying into node-sized capacity you cannot fill. Compare what the same budget buys on the H100 vs A100 page before assuming you need more than one card.
The cluster fine print
Node rentals amplify every hidden cost in the bill. A minimum commitment on an 8x node is eight times the commitment of the same term on one card, and cluster products in particular like to pair an attractive per-hour headline with weekly or monthly minimums. Storage and egress scale with the job size too: training runs that produce terabytes of checkpoints pay real money to move them out on providers that bill egress. The fees page covers what each provider charges beyond compute, and the rent-vs-buy calculator will tell you when a sustained multi-GPU bill crosses the line where owning hardware wins.
FAQ
Why is the per-GPU price sometimes lower on an 8x node than for a single GPU?
Selling a whole node is operationally simpler for the provider: one tenant, full utilization of the baseboard, no virtualization overhead. Some providers pass that back as a lower per-GPU rate. You are being paid, in effect, for committing to the full node.
Can I rent just one H100 instead of a node?
Usually yes. Many providers on our H100 page sell single GPUs with no minimum; the rows marked 1× in the node column are the ones where the provider publishes a single-GPU configuration. Rows marked 8× are node-only, and rows with a dash do not state a size, so check those before planning on one GPU.
Does the node size change how the table sorts?
No. Tables sort by per-GPU price, whatever the node size, and referral status never affects ordering. The node size is a disclosure, not a ranking penalty: you decide whether a node-only rate fits your workload.
Do I need NVLink for fine-tuning?
If the fine-tune fits on one GPU (as many LoRA-style jobs do), no: interconnect only matters when GPUs must exchange data mid-job. If you are sharding a model or its optimizer state across GPUs, NVLink-connected nodes will train meaningfully faster than PCIe-connected cards.