GPU economics
The GPU Hourly Rate Is Only Part of the Rental Bill
A GPU rental estimate starts with the entire billable node, then adds independently billed storage, networking, setup and other applicable services. Per-GPU division is a comparison metric rather than a promise of fractional-node availability. The calculator separates running and stopped storage rates, remaining transfer allowance and per-start minimums. Its flat-rate inputs are assumptions; tiered fees, contract terms and unknown charges must be resolved before treating the result as a complete purchasing estimate.
An hourly rate needs a denominator. A provider can advertise a per-GPU comparison price while requiring a complete multi-GPU instance. Another product can bill an accelerator separately from CPU, memory or storage. Those are different invoice structures even when the headline GPU name matches.
Start with the configuration that can actually be rented
AWS’s P5 specifications describe configurations with different GPU counts and networking capabilities. Azure’s NC A100 v4 specifications similarly distinguish one-, two- and four-GPU configurations. A comparison should retain the exact SKU and its hardware source rather than merging every appearance of a GPU family into one interchangeable product.
The rental total-cost calculator asks for whole nodes, GPUs per node and the entire node’s hourly rate. GPU count is used for the displayed comparison division; it does not divide the bill.
In the original default scenario, one eight-GPU node costs 8 dollars per node-hour and runs for 100 hours. Compute costs 800 dollars. A displayed 1-dollar GPU-hour metric does not reduce that invoice to 100 dollars.
Stopping compute does not necessarily delete storage
Storage has its own lifecycle. A persistent volume can continue to exist after compute stops, while a container disk may disappear. The Runpod pricing documentation distinguishes these cases and lists different running and stopped rates for volume storage. This editorial reference does not enable ingestion of Runpod’s catalog under its separate platform terms.
The calculator accepts a running storage rate, a stopped storage rate and the complete retention period. It uses deployment-wide storage rather than multiplying a shared volume by the node count. Add the volume capacities together when each node has a separate disk.
A 100 GB volume at a hypothetical 0.10 dollars per GB-month retained for the whole chosen month costs 10 dollars. That charge remains part of the example even though compute runs for only 100 hours. With a 50-dollar setup fee and no other entered charges, the example total is 860 dollars.
An allowance is not unlimited traffic
Oracle’s networking price list instead distinguishes a monthly free allowance and chargeable traffic beyond it. Its cloud price list retains regional charge distinctions. The first 10 TB being free must not become a blanket zero rate for every transfer volume.
An allowance can also be shared with other workloads in the same account or billing scope. Enter the allowance still available to this scenario, not the full quota repeatedly for each instance. The calculator’s overage rate is flat; crossing a tier requires a separately calculated tier subtotal in other costs. It does not pretend to implement every provider’s traffic tariff.
Address and network services have independent units
AWS VPC pricing prices public IPv4 addresses by address-hour, not by transferred gigabyte. NAT gateways, load balancers and data processing can add different dimensions. Cross-zone, inter-region and public outbound traffic must not be collapsed into one generic networking charge.
Storage can add request charges, retrieval fees, provisioned IOPS, throughput charges, snapshots, early deletion or minimum retention. Dedicated hardware can add setup, minimum commitment, support or software licenses. A price parser should preserve unknown values as unknown instead of producing a reassuring zero.
Minimums apply to allocation events
A one-minute minimum billed at every start behaves differently from second-based billing across a single long-running allocation. The calculator rounds each assumed equal-duration start independently. It does not infer a provider’s billing policy from a requirement to preload enough account balance for an hour; a balance requirement and a billing minimum are different rules.
Finally, the month length is explicit. A 730-hour planning month is an averaging convention, not the number of hours in every calendar month or a universal storage tariff. Currency conversion, tax eligibility, actual billing increments and contract-specific charges must be checked separately. The source policy explains why a complete-looking table is not evidence that all of these terms have been verified.
Sources
The GPU Hourly Rate Is Only Part of the Rental Bill. ByteCosts. Updated 2026-09-06. https://bytecosts.com/blog/gpu-rental-hidden-costs/