Home / Data / GPU cloud pricing and availability

GPU cloud pricing and availability

The prices and availability neoclouds and hyperscalers publish through their pricing APIs and published pricing pages. Each observation records the price as published, its source and its UTC capture time.

Coverage

Eleven GPU classes, priced by hyperscalers and neoclouds, recorded by region, term and pricing type.

GPU classes

GPU classMakerArchitecture
H100NVIDIAHopper
H200NVIDIAHopper
B200NVIDIABlackwell
B300NVIDIABlackwell Ultra
GB200 NVL72NVIDIAGrace Blackwell, rack scale
GB300 NVL72NVIDIAGrace Blackwell Ultra, rack scale
MI300XAMDInstinct, CDNA 3
MI325XAMDInstinct, CDNA 3
MI355XAMDInstinct, CDNA 4
L40SNVIDIAAda Lovelace
A100NVIDIAAmpere

What each price is recorded against

Provider segment
Hyperscalers, the large general-purpose clouds, and neoclouds, the clouds built around GPU capacity. The two are kept separate.
Pricing type
On-demand, spot or preemptible, and reserved.
Region
Each provider's published regions, mapped to one region list.
Term
Hourly on-demand rates and reserved terms in months, as each provider states them.
Configuration
GPU variant, interconnect and GPUs per node, recorded with every price.

For what GPU systems cost to own, see GPU systems pricing.

Observation schema

One record per offer per capture. The price as published is kept beside its normalized form.

FieldTypeMeaning
observation_idstringOne identifier per offer per capture
captured_atUTC timestampWhen the price was captured
sourceenum: pricing_api, published_pageWhere the observation came from
raw_snapshot_idstringThe stored raw capture the observation was read from
provider_segmentenum: hyperscaler, neocloudProvider type
provider_idstringProvider, from the Rillor source register
regionstringProvider region, mapped to the Rillor region list
gpu_classenum: H100, H200, B200, B300, ...One of the 11 tracked GPU classes
gpu_variantstringForm factor and memory variant as the provider lists them
interconnectstringGPU interconnect as the provider lists it
gpus_per_nodeintegerGPUs in the priced instance or node
pricing_typeenum: on_demand, spot, reservedSpot includes preemptible offers
term_monthsintegerCommitment term; zero for on-demand and spot
usd_per_gpu_hourdecimalPrice for one GPU for one hour, in U.S. dollars
price_as_publisheddecimal, currency, unitThe price exactly as the provider states it
availability_as_publishedstringThe provider's own availability field, unchanged
reported_availablebooleanWhether the provider reports the offer as available to rent

How it is captured

From the provider's published price to a record you can audit back to the original response.

Capture pipeline for GPU cloud pricesThe methodology captures provider pricing APIs and published pricing pages within each source's terms, with a UTC timestamp. Each raw response is stored unchanged for audit. Prices are then normalized to U.S. dollars per GPU-hour and tagged with GPU variant, interconnect, node size, region and term. The result is one observation record per offer per capture, which feeds the Rillor Compute Index rental and availability series.Provider sourcesofficial pricing APIspublished pricing pagesCapturewithin each source's termsUTC timestampRaw snapshotstored unchangedkept for auditNormalizeUSD per GPU-hour, GPU variant,interconnect, node size, region, termObservation recordsGPU cloud pricing datasetone per offer per captureRillor Compute IndexRCI RentalRCI Availability
Every observation links back to the raw response it was read from.Process diagram
Sources
Official provider pricing APIs and published pricing pages, used within each source's terms.
Timing
Each observation records its capture time as a UTC timestamp.
Raw snapshots
Each raw response is stored unchanged and linked to the observations read from it, so any value can be traced to its source.
Normalization
Prices are converted to U.S. dollars per GPU-hour. Per-instance and whole-term prices are brought to one GPU for one hour, and each offer is tagged with GPU variant, interconnect, node size, region and term.
Corrections
A corrected observation is stored as a new version, and the original stays on record.

What availability means

Availability means what a provider reports as available to rent.

We keep the provider's own field exactly as published, such as an in-stock flag or a stock level, and map it to one yes-or-no value for comparison. It is recorded at the moment of capture, beside the price, and describes rentable offers at that moment.

What it is used for

Decisions about renting, buying and financing GPU capacity.

Capacity planning

Compare what each GPU class costs to rent by region, term and pricing type before committing to capacity.

Procurement

Check a quote against what providers publish for the same GPU class, configuration and term.

Financing diligence

Rental prices for the GPU class behind a loan or lease, as context for collateral and residual value.

GPU financing

The Rillor Compute Index

These observations are the input to the RCI Rental and RCI Availability series.

Rillor Compute Index

Notices

Index. Rillor Compute Index series are for research and planning use. They are not offered for settlement of any contract.

Trademarks. NVIDIA, AMD and related product names are trademarks of their owners and are used only to identify products. No affiliation or endorsement is implied.

Tell us which GPU classes and regions you track.

Request pricing data