The price of one GPU-hourFile copy · not for publication

Identical hardware.Quoted the same day.Two times apart.

$9.80Google Cloud · on demand
1.8×
$17.57Azure · on demand

Basis studies what makes identical compute cost differently — and how much of that difference observable facts still cannot explain. Every figure traces back to the raw response a provider returned.

118 on demand quotes · H100 SXM 80GB · 5 providers · USD/GPU-hour · Sep 19 · 20:01 UTC

Open the findings
01 · The briefA study, not a product

Commodities convergetoward a price.GPU-hours don’t.

An H100 SXM 80GB has the same silicon wherever you rent it.1 Region, commitment, and contract structure explain part of the spread — but once those observable differences are accounted for, prices ought to converge. They don’t. Not even close.

Nobody had published, on public data, with a method you can rerun, how much of that dispersion is actually explainable. So we started asking twice a day, and writing down every answer.

Sample receiptQuote #984196

Vast.ai · spot · $0.72/GPU-hr

Provider response · collected Sep 19 · 20:01 UTC

Inspect on Basis →
02 · Exhibit A

Same accelerator.Same day.1.8× apart.

H100 SXM 80GBGoogle Cloud · UNKNOWN · on demand
$9.80
H100 SXM 80GBAzure · AE · on demand
$17.57
03 · The name

The gap has a name.

In commodity markets, basis names the gap between a local cash price and the relevant futures price — the part geography, timing, and contract terms cannot standardize away.2 Traders have a word for the gap between a reference price and the price realized in a particular market. We borrow it for compute.

If GPU compute is becoming a commodity, it appears to carry a basis of its own. In this study, Basis is the share of quoted price dispersion that remains after provider, region, commitment, and other observable terms are accounted for — not the raw spread between two quotes, but the part normalization still cannot explain.

REFERENCE PRICEQUOTED PRICE
Median quote · same SKU & collection dayObserved quotes only. Basis names what normalization cannot explain.
04 · The method

Twice a day. Four steps.Every answer kept.

Collect → file → canonicalize → account. The full procedure is documented separately.

  1. 01Collect08:00 / 20:00 UTC
  2. 02Fileraw, immutable
  3. 03Canonicalizerule-based only
  4. 04Accountvariance decomposition
05 · Exhibit B

One collection day.One canonical GPU.

H100 SXM 80GB · 2026-09-19 · Sep 19 · 20:01 UTC · 500 quotes · raw dispersion before controlsLog scale: equal horizontal distance is an equal price multiple. Hover, tap or arrow through a lane to read a quote.

Raw quoted dispersion · log scale · USD per GPU-hour · before controlsn = 500 of 638 recorded
Vast.ai7
AWS15
RunPod6
Google Cloud376
Azure96

We report the middle 90% (p5–p95), not the mean — the quote distribution is skewed, and outliers can distort an average without describing the market.

Quote slipday summary
$6.98/hr
Canonical SKU
H100 SXM 80GB
Provider
median of 500
Region
all countries
Commitment
all types
Recorded
2026-09-19

Pick a quote to read the one behind it.

Pull the raw observation

The spread is real. Region, commitment, provider, and bundle explain some of it. Next, we remove what we can explain.

06 · Exhibit C

The settlement sheet. One hundredunits of disagreement, filed againstwhat sellers disclose.

Sample populationmarket-priced · Azure and Google Cloud excluded

Where the machine is. How it’s rented. Who sells it. What comes bundled with it. Everything observable, accounted for, and still a share of the price has no explanation.

Four observable factors
97.2%
The remainder
2.8%
Market-priced range
023%across 30 days

Change the order of the factors and the four credits move. The remainder does not. That is why the remainder is the headline. The ledger it comes off, filed row by row, is on the Basis page.

07 · Findings of record

Three sheets that survived review.

Subject · observable boundBound, not victory

A richer model on the same days still falls short.

Forty-five features, day-based validation, and a leakage guard — scored on the same held-out days as the four-factor bound.

Four factors · same holdout days56.3%
45 features · out-of-sample45.4%
Δ 10.9ppas of Jul 31
Show the method

Splits fall on ordered days, never rows. The final 10 days never enter selection. Scoring is day-demeaned, so the model gets no credit for knowing roughly what an H100 costs this month. A permuted-target holdout above 0.05 kills the run; this one scored -0.19. Both bars use the same holdout window (10 days). The gap bounds what observables can do. It says nothing about what nobody publishes.

Subject · host identityIdentity, not specs

The remainder isn’t only noise. It persists by host.

0.55Intraclass correlation · host identity · 61 hosts · 10-day tenure

Over half of what survives the subtraction tracks which host listed the offer, day after day. That persistence is inconsistent with a fully fungible market — at least within the factors and period studied.

Show the sensitivity
  • 5d0.551
  • 20d0.531

Published side by side, across every tenure threshold we tried. No threshold was chosen for flattery.

Subject · the moving shareA range, not a favorite

The number moves. We publish the range it moves in.

0%23%

Unexplained share in market-priced segments across the last 30 days. A single figure would be a snapshot pretending to be a constant, so the file quotes both ends and dates them.

  • Limitation L1Quoted prices, not transactions. Negotiated and realized prices are not observed.
  • Limitation L2A marketplace and a hyperscaler are not like-for-like populations.

Somebody is about to writethe rules for how computegets priced.

You can’t build financial plumbing on a price you can’t explain. There is growing interest in treating AI compute like a commodity, with indexes, futures and contracts on top of it.3 All of that assumes a GPU-hour has a knowable market price. That unexplained remainder is the risk any benchmark would silently absorb.

  • It’s a study, not a product

    Nothing for sale, no paid feed as a required input. Public quotes and a method you can rerun.

  • Every number has a receipt

    Headline share, contributing offers, raw response, exact rules applied. Four clicks, no exceptions.

  • Honest about limits

    One collection outage found, published, root-caused and turned into a standing alarm rather than smoothed away.

The file is open

It is not asking to be believed. It is asking to be checked.

I was just bored and curious. So here it is:

— Raj

Sources
  1. Hardware identity within a canonical SKU: normalization rules and variant separation — Basis methodology §3 (canonical schema).
  2. Commodity basis — cash price minus futures price; CME Group education materials on basis and hedging.
  3. Compute-as-commodity framing — Ornn AI public materials; the essays referenced in the original Basis proposal.

The GPU spread itself is our own live data. See the dispersion page.