GPU Rental PricesGPU Rental Prices / GPU prices
Download data

Methodology

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

Price check status (2026-10-06)

No failed public-price checks in this snapshot.

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: Daytona, Lium, Impossible Cloud, Synteq, 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, Scaleway, Google Cloud (expanding). AWS uses its own public on-demand and spot feeds; Azure uses its Retail Prices API. Earlier AWS observations from a third-party mirror are excluded at read time, with the original history retained. Each row stores the price, the source URL, and the exact fetch timestamp. Each offer shows its own Updated date.

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

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 and community / spot remain separate price tiers. The tier does not prove stock or a service guarantee. Reserved commitments and serverless rates also remain separate; neither counts as a spot observation. We show both and label every row, so the billing models can be compared explicitly. Prices are per GPU per hour and exclude storage, egress and networking.

Affiliate disclosure

Provider buttons use direct URLs. No commission is currently arranged. Prices sort the tables; tracking never changes the order. Lium listing links include campaign parameters so the provider can count referrals; no commission is arranged for those links. The cheapest listed rate wins whether or not the provider pays us anything, and no program we join asks for placement.

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.

Configuration, availability and model estimates

GPU count, node totals, CPU, RAM, disk and region come from a published configuration. Missing fields say “not reported”; an absent node minimum is not treated as a confirmed single-GPU offer. A recent price does not establish available stock.

Monthly plan equivalents use 720 hours; listed annual Latitude plans use 8,760 hours. Model weights, supported KV-cache calculations, runtime headroom and training allowances are separated on each model page. They are estimates, not performance or compatibility claims.

Source observations and update dates are collected on the Sources page linked in the footer.

Compare your offers

Saved prices keep their original dates. Confirm the configuration, terms and availability at the source.

Select up to three offers to compare their rates and terms.