⬡viabandwidthGPU Compute
viabandwidthResearch field guide · 2026

Beyond the GPU-Hour

A practical GPU cloud pricing comparison built around completed-workload cost, official list-rate evidence and a two-supplier quotation worksheet.

$3.99
Runpod H100 SXM list rate
$4.29
Lambda 1x H100 SXM list rate
$917.70
Illustrative 230-hour compute bill
15%
Idle-time uplift in that scenario

The purchasing question

The cheapest GPU-hour is not necessarily the cheapest completed workload. A headline rate excludes the amount of billable time a job consumes and may exclude persistent storage, data movement, support, minimum commitments and tax.

01 · Cost metricStart with the completed workload

Record three figures separately: the provider's native quoted rate, the billable consumption under its start-and-stop rules, and the successful output produced at the required quality and deadline.

Completion-cost equation. Total workload cost = GPU or instance charges + mandatory storage + data movement + managed-service and support fees + minimum commitments + applicable tax. Effective cost per completed workload = total workload cost ÷ successful completed jobs.

At Runpod's published $3.99 H100 SXM Pods rate, 230 billed hours for 200 productive hours produces a compute-only bill of $917.70, or $4.59 per productive GPU-hour. This is transparent arithmetic, not an observed Runpod workload or a claim about its idle behavior.

02 · Public evidenceOfficial rates are leads, not interchangeable bids

Provider and sold objectGPUNative list rate
Runpod PodsH100 SXM 80 GB$3.99/GPU-hour
Lambda 1x instanceH100 SXM 80 GB$4.29/GPU-hour
Runpod PodsH200 141 GB$5.29/GPU-hour
Crusoe GPU instanceH200 141 GB HGX$4.29/GPU-hour
Lambda 1x instanceB200 SXM6 180 GB$6.99/GPU-hour
Runpod PodsA100 SXM 80 GB$1.79/GPU-hour

Rates rechecked on 2 November 2026. Provider selectors, region, availability, attached resources and tax can change the transactable configuration. Only the two 1-GPU H100 SXM examples form the worked comparison below; the remaining rows are deliberately directional.

03 · Worked comparisonWhen the lower GPU-hour can lose

If both H100 offers require 200 billable hours, Runpod's listed rate produces $798 in compute charges and Lambda's produces $858. But at Lambda's $4.29 rate, the break-even runtime is just under 186.01 hours for the same accepted workload.

TestRunpod exampleLambda example
Same billed time200 h × $3.99 = $798200 h × $4.29 = $858
Break-even runtime200 h at agreed qualityLess than 186.01 h at the same quality
Unpriced obligationsStorage, network and tax: unknownStorage, network and tax: unknown

No benchmark supports the 186-hour premise. It is a break-even illustration, not a provider performance claim. Buyers must measure or contract the completed result.

04 · InvoiceUnknown must not silently become zero

  • 01Compute: when does the meter begin, pause and stop?
  • 02Storage: what persists after the instance terminates, and at what rate?
  • 03Movement: which ingress, egress, cross-zone and interconnect rules apply?
  • 04Service: which platform, scheduler and support charges are bundled?
  • 05Contract: what remains payable if utilization is zero?

Lambda's billing documentation, for example, says running on-demand instances are billed even when unused and that filesystems continue billing while they exist. It also states that filesystem ingress and egress are not charged, illustrating why blanket cloud-cost assumptions are unsafe.

05 · Quote worksheetMake suppliers price the same object

The downloadable eight-page field guide includes a two-supplier worksheet covering GPU variant and count, sold object, topology, host resources, region, commitment, billing increments, storage, data movement, support, tax, measured billable hours and all-in completed-workload cost.

Qualification gate. Require model and memory variant, physical GPU count or partition, sold object, CPU/RAM/storage and fabric, region, term, tax treatment, billing granularity and dated official source. If an essential field is missing, label the comparison directional or not comparable.

06 · MethodWhat this guide can support

This is a buyer guide, not a market census or benchmark. It uses official public list rates and illustrative arithmetic. It does not claim tested throughput, current stock, identical bundles, negotiated pricing or supplier-specific idle behavior.

Historical context only: ViaBandwidth's private 60-offer Q2-to-October same-offer cohort included 41 unchanged prices, 15 increases and four decreases across 10 provider domains. That narrow cohort cannot establish market-wide price inflation.

viabandwidth is the verified directory of GPU compute, colocation and carrier networks.

Public list prices are dated observations, not signed quotations or evidence of available stock. Worked runtimes are illustrative arithmetic, not measured supplier performance. Buyers must confirm the complete configuration, billing rules, region, availability, tax and contract terms before purchase.

© 2026 viabandwidth (Steven Higashi). All rights reserved. The figures and charts in this paper may be quoted with clear attribution to viabandwidth.

Cite as: ViaBandwidth, Beyond the GPU-Hour: The 2026 GPU Cloud Pricing Buyer's Guide, viabandwidth.com/gpu/guides/gpu-cloud-pricing-comparison.

viabandwidth.com · [email protected]