$GPU Rental Prices.com

Methodology

Every number on this site is either fetched from a provider source or computed by a formula we show. Nothing is typed in by hand, and nothing stale is presented as live.

Where prices come from

Once per day we fetch each provider's own pricing source: a public API where one exists, the official pricing page otherwise. Current providers: RunPod, Lambda, Hyperstack, CoreWeave, Nebius, DataCrunch, Voltage Park, Crusoe, Jarvislabs, OVHcloud, Spheron, Microsoft Azure, AWS, Together AI, fal, Modal, Vultr, Massed Compute, TensorDock, SaladCloud, Replicate, Fireworks AI, Baseten, DigitalOcean, GMI Cloud, Prime Intellect, Cerebrium, Koyeb, Thunder Compute, Latitude.sh, Hot Aisle, SF Compute, Scaleway, Google Cloud (expanding). Two exceptions to "provider's own source": AWS prices come from ec2.shop, a public mirror of AWS's on-demand and spot feeds (AWS's own bulk file is impractical to fetch daily), and Azure prices come from Azure's public Retail Prices API. Both are labeled with those sources on each row. Each row stores the price, the source URL, and the exact fetch timestamp. The Verified badge on every table shows that timestamp.

Three kinds of numbers

When a fetch fails

Providers change their pages. When a fetch or parse fails, that provider's rows are carried forward and visibly flagged with the date they were last verified: they never silently pretend to be today's price. Persistent failures get fixed or the provider is dropped.

The price ledger

Every daily snapshot is kept forever (49 so far, since 2026-07-05). That append-only ledger powers the per-GPU history charts and the downloadable dataset. History cannot be backfilled: which is exactly why we record it.

The GPU Rental Price Index (GRPI)

The GPU Rental Price Index turns the whole market into one number. It is chain-linked per GPU family: base 100 on the first ledger date, then each day the level is multiplied by that day's link, and the link is the equal-weight mean of per-family price ratios.

The provider intersection is taken independently for each family. A family's ratio compares its cohort median (a median of per-provider medians) across only the providers that list that family with a firm offer on both the current and the previous snapshot. A provider that is newly added, or that stays live overall but drops or re-adds a single family for a day, is simply not in that family's intersection on the affected day, so it contributes nothing to the move. This is why composition change never moves the level: the comparison is always like-for-like within each family, and a global "provider is live somewhere" test never leaks into a family whose own listing changed.

About the base. The 2026-07-05 base snapshot covered 2 providers (Lambda, RunPod) and was cleaned once (removal of a RunPod $0.50 sentinel value), so the first link (2026-07-05 to 2026-07-06, +4.27%) reflects early-capture volatility rather than a settled market, and the provider universe reached full coverage (18 providers, all live) on 2026-07-08. The base anchors only the level, never a fixed provider set: the like-for-like universe widens as the ledger accumulates.

Tiers explained

Secure / on-demand capacity runs in datacenters with availability guarantees. Community / spot capacity is cheaper and interruptible. We show both and label every row, because the cheapest number without its tier is a trap. Prices are per GPU per hour and exclude storage, egress and networking.

Affiliate disclosure

Provider buttons currently use each provider's plain URL, without our referral or affiliate tracking. If an approved referral link is added later, the link will be marked sponsored and this disclosure will be updated. Link status never influences ordering: tables sort by price, and the cheapest verified rate wins whether or not the provider pays us anything.

Revisions

This is a dated changelog for anything that changes how a published number is computed or which rows count toward it. Nothing here rewrites the ledger (rule #4: it is append-only). Every change below is either a read-time exclusion or a computation fix applied going forward.

Cite this data

Referencing the index in research or writing? Cite the snapshot you retrieved. The data page has the same formats plus the CSV and JSON downloads.

APA

GPU Rental Prices. (2026). GPU rental price index [Data set]. gpurentalprices.com. https://doi.org/10.5281/zenodo.21435394 (Retrieved 2026-08-22)

BibTeX

@misc{gpurentalprices_2026,
  title  = {GPU Rental Price Index},
  author = {{GPU Rental Prices}},
  year   = {2026},
  doi    = {10.5281/zenodo.21435394},
  howpublished = {\url{https://gpurentalprices.com/data}},
  note   = {Accessed 2026-08-22}
}

HTML

<a href="https://gpurentalprices.com/data">GPU Rental Price Index</a>. GPU Rental Prices, 2026. DOI: <a href="https://doi.org/10.5281/zenodo.21435394">10.5281/zenodo.21435394</a>. Accessed 2026-08-22.