About

Methodology & sources

One place for the numbers behind AI compute — compiled from primary sources, normalized so they compare honestly, and labeled when they’re estimates.

What this is

AI Compute Tracker (aicomputetracker.com) tracks the economics of AI compute: what GPUs rent for, what the chips can do, what a million tokens costs, and how much capital is pouring into the buildout. It exists because these numbers are scattered across provider pages, earnings decks, and research posts — and because most public comparisons quietly mix incompatible units.

Independence & funding

What the release gate checks

  • No affiliate or referral links. None of the 139 source links behind the quotes, token prices, hardware specs and buildout claims carries an affiliate, referral or tracking parameter, and no link on these pages does.
  • No ads, no third-party scripts. Every script on these pages is served from aicomputetracker.com.
  • Prices from public pages. Each of the 20 quote sources is a public page or API read without an account or key, linked from its row. The evidence ledger lists the published quote snapshot’s content ID, and its reference list the evidence reference behind every verified price observation.

Tests and the release gate check each one on every pull request.

Dataset status

The market snapshot and the core surveys refresh independently. Their stamps stay separate everywhere on the site.

Market snapshot

Forward curves, the terminal, and the market rail. Rebuilt by the forward-market pipeline from Kalshi ladder snapshots; this pill flags itself stale past 26 hours.

Live quotes

Latest automated collection. Healthy rows refresh independently; unavailable sources retain their original observation dates, shown beside each quote. The manual/core survey clock is unchanged. Flags itself stale past 10 days.

Core review · mixed · full survey due

Latest domain review is shown separately from the last complete survey. Partial reviews retain older inputs and their original dates; review scope is listed below. The full survey is due past 60 days.

Last complete survey: .

  • Manual GPU quotes: 2026-10-14 · partial; retained inputs since 2026-07-06.
  • Hardware specifications: 2026-10-15 · complete.
  • Inference list prices: 2026-10-15 · complete.
  • Financials and guidance: 2026-10-15 · complete.
  • Cluster buildout claims: 2026-10-14 · complete.
Current status and coverage of AI Compute Tracker datasets
DatasetAs ofCoverageStatusReview target
Market-implied curvesInstrument anchor + monthly tenors to Aug ’277 quality-passed / 53 thin or interpolatedStale past 26 hours
GPU rental quotesProvider list and marketplace ratesPublished snapshot 2026-10-14 + 11 automated rows 2026-10-14; manual observation coverage belowAutomated rows stale past 10 days
Manual GPU quotes59 of 71 manual quote observations are dated 2026-10-14. Older observations are retained from 2026-07-06; each quote keeps its own observation date.Partial review · older inputs retainedEvery 30 days; last complete 2026-07-23; overdue since 2026-08-22
Hardware specificationsEvery field of every row was checked on Oct 15: technical figures against the vendor documents /hardware lists with each chip, launch months against vendor releases and filings, availability against vendor pages and press reports, and purchase-price estimates against named reports, with a price shown only where a reputable report gives one. No vendor publishes Trainium2 board power (the table keeps SemiAnalysis's estimate), a tensor BF16 rate for Maia 200 or per-chip power for Google's TPUs.Listed scope reviewedEvery 60 days; last complete 2026-10-15; next due 2026-12-14
Inference list pricesAll table prices re-checked against provider documentation on Oct 15, with batch prices recorded wherever a provider publishes them, OpenAI's 272K-token threshold on the GPT-6 rows, the long-context prices of GPT-5.5, GPT-5.5 Pro and GPT-5.4, and eight generally available models added (Claude Opus 5, 4.7, 4.6 and 4.5, Claude Sonnet 4.6, Gemini 3.6 Flash, Grok 4.6 and Grok 4.5). Historical benchmark-qualified prices remain archived through April 2026; this review does not re-certify model quality.Listed scope reviewedEvery 30 days; last complete 2026-10-15; next due 2026-11-14
Financials and guidanceEvery capex cell, guidance row, NVIDIA data-center quarter and guidance figure, and Oracle disclosure was checked against company releases, filings, slides or call recordings on Oct 15. Oracle's FY27 net cash outlay for capex is stated on its Q4 FY26 slides; its gross range and Amazon's 2026 figure are stated only on the calls (Amazon's against its Q2 call recording). Each guidance row carries its own source and review date.Listed scope reviewedEvery 60 days; last complete 2026-10-15; next due 2026-12-14
Cluster buildout claimsEvery site's capacity figures, status, key dates and claims were re-checked on Oct 14 against operator releases and the Epoch AI tracker; each claim keeps its own source date. Still open: Colossus 2's first-power month (tracker estimate pending the SpaceX S-1), whether HUMAIN's NVIDIA capacity is live (secondary report only) and which campuses host the Fluidstack builds.Listed scope reviewedEvery 60 days; last complete 2026-10-14; next due 2026-12-13

Coverage & gaps

What each tracked accelerator actually has behind it — and where the record is thin. Every count derives from the datasets, so this matrix cannot flatter itself.

16 chips quoted · 16 providers · 5 with forward curves · 16 with exact history

Dataset coverage per accelerator, grouped by vendor
ChipRental quotesClasses quotedForward curveExact historyBadgeSpec sheet
NVIDIA
V100 SXM2legacy4 quoteshyperscaler + specialist + marketplacenot trackedshallow — 2 dates since 2026-07-06badge availablespec sheet available
A100 SXM 80GBlegacy9 quoteshyperscaler + specialistto Aug ’27shallow — 3 dates since 2026-07-06badge availablespec sheet available
H100 SXM14 quoteshyperscaler + specialist + marketplaceto Aug ’27building — 84 dates since 2026-07-06badge availablespec sheet available
L40S7 quoteshyperscaler + specialistnot trackedshallow — 3 dates since 2026-07-06badge availablespec sheet available
H200 SXM11 quoteshyperscaler + specialist + marketplaceto Aug ’27building — 84 dates since 2026-07-06badge availablespec sheet available
B200 (HGX)10 quoteshyperscaler + specialist + marketplaceto Aug ’27building — 84 dates since 2026-07-06badge availablespec sheet available
GB200 NVL72 (per GPU)3 quoteshyperscaler + specialistnot trackedshallow — 3 dates since 2026-07-06badge availablespec sheet available
B300 (HGX Blackwell Ultra)9 quoteshyperscaler + specialist + marketplacenot trackedshallow — 20 dates since 2026-07-06badge availablespec sheet available
Rubin GPUrampingnot tracked—not trackednot trackedno badgespec sheet available
GeForce RTX 4090legacy3 quotesspecialist + marketplacenot trackedbuilding — 84 dates since 2026-07-06badge availablespec sheet available
GeForce RTX 50903 quotesspecialist + marketplaceto Aug ’27building — 84 dates since 2026-07-06badge availablespec sheet available
AMD
Instinct MI300X3 quoteshyperscaler + specialistnot trackedbuilding — 55 dates since 2026-07-06badge availablespec sheet available
Instinct MI325Xnot tracked—not trackednot trackedno badgespec sheet available
Instinct MI355X2 quoteshyperscaler + specialistnot trackedbuilding — 55 dates since 2026-07-06badge availablespec sheet available
Instinct MI455Xrampingnot tracked—not trackednot trackedno badgespec sheet available
Google
TPU v5e1 quotehyperscalernot trackedshallow — 3 dates since 2026-07-06badge availablespec sheet available
TPU v5p1 quotehyperscalernot trackedshallow — 3 dates since 2026-07-06badge availablespec sheet available
TPU v6e (Trillium)1 quotehyperscalernot trackedshallow — 3 dates since 2026-07-06badge availablespec sheet available
TPU v7 (Ironwood)not tracked—not trackednot trackedno badgespec sheet available
AWS
Trainium21 quotehyperscalernot trackedshallow — 3 dates since 2026-07-06no badgespec sheet available
Trainium3not tracked—not trackednot trackedno badgespec sheet available
Microsoft
Maia 200not tracked—not trackednot trackedno badgespec sheet available
Intel
Gaudi 3not tracked—not trackednot trackedno badgespec sheet available

GPU rental prices

Rental prices are normalized to US$ per GPU-hour (per chip-hour for TPUs/Trainium). Every row retains its billing model: on-demand provider list, capacity block, serverless, variable marketplace ask, or secondary snapshot. Multi-GPU instance prices are divided per accelerator; unlike billing models are never joined into one history series.

Providers are grouped into three classes, defined in the glossary: hyperscalers (Oracle OCI, AWS, Google Cloud and Azure), specialist clouds (RunPod, CoreWeave, Crusoe, Hyperstack, Nebius, Lambda, Together AI and Voltage Park), and marketplaces (Vast.ai and Salad), whose open asks set the marketplace floor, often on community hardware with fewer guarantees.

Hand-surveyed quotes were fetched from provider pricing pages or Vantage instance listings on 2026-10-14; 11 rows with machine-readable primary sources (Vast.ai’s marketplace search API, the feeds behind AWS’s pricing pages and Azure’s Retail Prices API) are re-fetched for the reviewed current table by a weekly full-snapshot pipeline, last on 2026-10-14. Healthy sources refresh independently. When a Vast.ai book lists too few offers to use, the chip takes its most recent marketplace-tape capture from the last 7 days, dated with that capture's own time, if it is newer than the row it replaces; otherwise, and whenever a source is unavailable, the pair retains its original price and observation date. A pair its source explicitly retires (a Vultr plan that is not deployable on demand or is no longer listed) is removed instead of retained. This does not renew the manual survey date. Values marked est come from same-week aggregator snapshots. Historical series are indicative quarterly midpoints reconstructed from list prices, launch announcements, and archived snapshots — treat them as ±15%.

The immutable price ledger samples marketplace books every four hours and machine-readable provider lists daily. Each successful observation retains its received JSON text (a Vast.ai book is now kept only as an allowlist projection without host identifiers, plus the SHA-256 of the full response), payload digest, source identity, methodology, and observation time. Partial failures become visible gaps; hand-surveyed rows are added only on real survey dates and are never copied forward. The evidence ledger renders this chain end-to-end — snapshot IDs, checksums, verified-row counts, and the pinned raw-evidence references.

Forward curves & market-implied prices

The forward-curve board is built from Kalshi event-contract ladders on GPU rental prices referenced to Ornn’s hourly index. The first point is a future exact-time weekly event when a usable weekly ladder exists — not a current spot quote. If the weekly book is unavailable, the first point is explicitly the front-month monthly-average event. Its instrument and event identity are recorded per chip; incompatible anchors are never used to calculate movement. The rest of the strip uses monthly-average events through Aug ’27. Each implied level is the strike where a ladder’s yes-probability crosses 50%, and the resting bids and asks bracket it: a bid at one strike is a floor on every lower strike’s probability and an ask a ceiling on every higher one, so the bid-only and ask-only envelopes each cross 50% somewhere. The bracket is those two crossings, each interpolated linearly between the listed strikes around it; strictly, the quotes bound the median only to the outer of those strikes. A side no quote bounds is open. That is the market’s median expectation, not an executable quote — labeled Kalshi-implied wherever it headlines. Each Kalshi compute contract settles on Ornn’s executed-trade index — not comparable with posted list prices.

How each strike is read. The level reads only usable quotes: a strike with a bid above 0¢ and an ask below 100¢ counts as two-sided, but is read at its midpoint only when no wider than 20 points with size on both sides, and a strike without such a quote only at a last trade with 24-hour volume. A weighted isotonic fit (pool-adjacent violators, each quote weighted by its tightness) keeps them monotone — it can raise a level as well as lower it, unlike a running minimum — and nothing is smoothed: each monthly value is its own ladder’s estimate. With fewer than two usable quotes, or a fit that never crosses 50% within its own strikes or crosses it outside the bracket, no quote sets the level: a closed bracket gives its midpoint, and an open one only a placeholder (its closed side, or the middle of the listed strikes when neither side is closed) that the site never shows as a price — it shows the bracket. In this snapshot 7 of 55 ladders are read from their fit of 33 usable quotes, and 34 brackets are open on at least one side. A point passes — it is identified — only with both sides of its bid/ask bracket inside the listed strikes, a bracket no wider than 20% of its median, and at least 2 two-sided strikes, 1¢/99¢ placeholders excluded, quoted between 20% and 80%; 7 of 60 points pass this snapshot, and 84 of the snapshot’s 213 two-sided strikes are 1¢/99¢ placeholders. Only identified points draw a line and a band, and only they feed moves, carry, spreads and curve shapes.

This snapshot contains 7 quality-passed, 53 thin-ladder and 0 interpolated points. The lines and bid/ask bands join only quality-passed points; gaps are hollow at their level, unplotted without one, and no headline reads a move, carry, spread or curve shape from a gap. “Quality-passed” describes the underlying ladder, not an observed rental price: every plotted value remains reconstructed and non-executable. The complete methodology key is kalshi-ladder-median-50-v2+unsmoothed-v1.

Superseded snapshots stay in a dated archive — currently 34 sessions — that powers the curve time machine. Each snapshot persists its method and exact first-point instrument identity. The first 12 legacy sessions use a different monthly methodology. 13 sessions first published under an earlier estimator were re-derived under the current one on Oct 15, 2026 from the raw ladders retained when they were captured; each records the re-derivation. 7 sessions without retained ladders keep the estimator they were published under, labeled as such. Every session is displayed with its own methodology and never compared across one. “Prior snapshot” movement requires the same event ticker and methodology, and reports the actual elapsed time rather than calling the gap 1d.

Why these markets exist

Every tracked venue, its status and each dated market-structure event have a page of their own: GPU compute futures & markets.

Price signals & reference rates

Four kinds of numbers now get called “the price of compute”. They measure different things, revise differently, and only some can be independently checked.

The four price-signal types in the AI compute market compared
SignalExemplar & recordWhat it measuresWhat it hidesRevision policyAuditabilityOur nearest series
Posted list / ask surveysThis site's quote table and its citable class aggregates (e.g. ACT.H100.SPEC-MED@primary-on-demand-v1)Rental-price methodology (surveyed )The prices providers publicly ask: on-demand list rates and open marketplace asks, normalized to USD per GPU-hour with each row's billing model retained.What anyone actually pays — negotiated commitments, private discounts, and whether posted capacity is really available at the posted price.A provider can change or delete a list price at any time; our dated observations are kept immutable in the price ledger, but the posted price itself carries no finality.Open — every quote links its source page and observation date, and verified ledger rows pin the raw payload digest to durable evidence.This is our signal: the ACT.* class aggregates (posted list/ask prices, not transactions). View our nearest series for Posted list / ask surveys →
Transaction-VWAP indicesOrnn Compute Price Index (OCPI); Silicon Data H100 / B200 rental indicesICE Futures U.S. notice (first contracts named ) · September 28 postponement notice (postponement notice )Volume-weighted prices computed by an index provider from actual rental transactions — a spot reference for what trades, not what is listed.The trade tape behind the print: constituent transactions, panel composition, and weighting are the provider's proprietary inputs, so a print cannot be independently recomputed.Set by each provider's own index methodology; we do not track or republish their correction terms here.Proprietary — index levels are licensed data. This site links the public announcements only and republishes no index values.None — this site publishes posted prices and market-implied levels, never transaction or settlement data.
Exchange settlement pricesCME Group Silicon Data H100/B200 rental-index futures (postponed — postponement notice Sep 28, 2026, pending review); ICE × Ornn GPU futures (announced — first contracts named Sep 29, 2026, pending review)September 28 postponement notice (postponement notice ) · ICE Futures U.S. notice (first contracts named )The price at which cleared futures settle: a regulated, tradable consensus at a defined timestamp, cash-settled against the underlying index.Everything off-exchange — physical availability and bespoke terms — and, until a first trade prints, everything else too.A settlement published under an exchange rulebook is final for margining — the opposite end of the spectrum from a list price a provider can edit at will.Public print, proprietary underlying — settlement values are exchange-published, but they cash-settle to licensed index levels (see the sources).None — this site publishes posted prices and market-implied levels, never transaction or settlement data.
Event-market implied levelsKalshi compute event ladders — the exact source of this site's forward curvesKalshi compute markets (monthly ladders open )Where yes-probabilities on yes/no price brackets — bid/ask midpoints no wider than 20 points and trades with 24-hour volume, bracketed by the resting bids and asks — put the market's median expectation for a future rental price: a probability-implied level, moving while the books trade.An executable rental price: implied medians are reconstructions from thin, bounded ladders — nobody rents a GPU at the implied level.Implied levels move continuously until each event resolves; our snapshots are dated, archived immutably, and compared only under an identical methodology key.Open — the ladders are public order books, and our snapshots retain strike, spread, volume, open-interest, and event-ticker evidence per point.These are our forward curves: the Kalshi-implied strip on the forward board, labeled with per-point ladder quality. View our nearest series for Event-market implied levels →

What settles where

Each trading venue’s underlying reference rate and our nearest comparable series
VenueReference rateSignal typeOur nearest comparable
KalshiOrnn hourly indexTransaction-VWAP indicesOur forward curves are reconstructed from these exact ladders — the implied strip, not the settlement index. View our nearest comparable for Kalshi →
CME GroupSilicon Data H100 / B200 rental indicesTransaction-VWAP indicesNearest comparable, not the same signal: ACT.H100.SPEC-MED@primary-on-demand-v1 and ACT.B200.SPEC-MED@primary-on-demand-v1 track posted prices for the same chips. View our nearest comparable for CME Group →
ICEOrnn Compute Price IndexTransaction-VWAP indicesNearest comparable, not the same signal: our ACT.* posted-price aggregates cover the announced contract chips (e.g. ACT.H200.SPEC-MED@primary-on-demand-v1). View our nearest comparable for ICE →

Every venue above settles to a proprietary transaction index. Our open series sit next to those rates — same chips, same unit — but they are posted-price surveys, never the settlement value.

Read this first

What our numbers are not

  • Not transaction prices. We publish posted list/ask prices and market-implied levels; no executed-trade data enters any series.
  • Not a settlement benchmark. ACT.* aggregates are versioned survey statistics (posted list/ask prices, not transactions) — nothing here is licensed for, or suitable as, a contract's reference rate.
  • Not executable quotes. Forward-curve values are probability-implied medians reconstructed from event ladders; no one will rent to you at those levels.
  • Not a republication of third-party indices. Silicon Data and Ornn index series are not republished here. The one Ornn figure we keep is each settled month's value: the month's average of Ornn's hourly index, as Kalshi publishes it for its contracts' expiration. We store it from Kalshi's data, never Ornn's, to score our archived curves.

Comparison conventions

The rules that keep unlike hardware, APIs, and estimates from becoming false equivalences.

Hardware

Dense FLOPS

Every throughput figure is dense tensor throughput. “With sparsity” figures assume structured-sparse weights; we use the vendor’s explicit dense figures because the ratio varies by chip and format. BF16/FP16, FP8, and FP4 stay separate; cost-efficiency charts use dense BF16 unless labeled otherwise.

Inference

Blended token price

The single-number price is (3 × input + output) ÷ 4, a typical 3:1 read/write mix. Batch tiers (~50% off), cached input (~90% off), long-context surcharges, and regions shift real costs. “GPT-4-class” means matching original GPT-4 on MMLU, ≈86.4.

Provenance

Estimates policy

Anything not traceable to a primary source carries an est badge: training compute, cluster power or chip counts, some street prices, and aggregator quotes. Company financials come from filings and earnings releases, with fiscal mapping disclosed alongside the charts.

Evidence & sources

Primary sources anchor the datasets; secondary research is used only where first-party disclosure is incomplete.

Filings & research

Financials and buildout

Earnings releases and SEC filings from NVIDIA, Microsoft, Alphabet, Meta, Amazon, Oracle, and CoreWeave; Epoch AI for training-compute estimates; company announcements and sector reporting for clusters; getdeploying and AIMultiple for market medians.

Evidence & release log

A concise record of the stamps driving the current build.

  1. Market-structure record refreshed

    Latest event: Kalshi — No weekly ladder open; monthly ladders open (2026-10-11). This site’s archived Oct 11 session (anchor per chip).

  2. Market snapshot refreshed

    Forward ladders and archived-session comparisons use this independent market timestamp.

  3. Last complete core survey

    Later domain reviews are tracked separately. The latest is 2026-10-15; retained inputs keep their own dates.

What counts as evidence?

A primary price page, filing, earnings release, technical datasheet, or market observation is treated as reported evidence. Reconstructions, third-party medians, and incomplete public claims are labeled inferred or est at the point of use.

Update cadence & contact

Each domain’s review target and next due date are in the dataset-status table; a partial review never moves a due date. The complete survey is due every 60 days (last: 2026-07-23, overdue since 2026-09-21; latest domain review: 2026-10-15). Spotted an error? Email data@aicomputetracker.com or use “Report a wrong price” on a quote row; material corrections are logged on the corrections page.

The site’s own text and data compilations are licensed CC BY 4.0; reuse them with the attribution “AI Compute Tracker (aicomputetracker.com), CC BY 4.0; includes data from Epoch AI (epoch.ai), CC BY 4.0”. Third-party source data — such as Kalshi market data, Vast.ai marketplace data, and providers’ list prices — remains subject to its sources’ terms.

Nothing on this site is investment advice. Trademarks belong to their owners; prices belong to the providers; mistakes belong to us. The terms of use say what you can rely on.

Glossary

The words behind every price label, defined once.

Price labels

Cheapest on-demand
The lowest on-demand list price for a chip, big and specialist clouds alike.
Typical
The median on-demand list price of the specialist clouds quoting a chip — one cloud's price when only one quotes it, and their min–max range when fewer than 3 do.
Big-cloud list price
The lowest on-demand list price among the hyperscalers quoting a chip.
Marketplace floor
The lowest marketplace ask for a chip; it holds only while that machine is free.
n
How many venues stand behind a figure, named when fewer than 3.
Floor
The lowest price in a group: one listing's price, never an average.

Venues

Specialist cloud
A cloud built to rent AI accelerators (for example RunPod, CoreWeave, Crusoe, Hyperstack).
Hyperscaler
A big general-purpose cloud (for example Oracle OCI, AWS, Google Cloud, Azure).
Marketplace
An open market of independent GPU hosts (for example Vast.ai, Salad); prices and availability vary.

Billing models

On-demand
Hourly, no commitment, at the provider's published list price — the basis of every on-demand comparison.
Capacity block
Capacity reserved for a fixed period and paid ahead; kept apart.
Serverless / per-second
Billed per second of use on a managed platform; kept apart.
Marketplace / variable availability
A marketplace ask, compared only with other marketplace asks.
Secondary snapshot
A price taken from a third-party listing, not the provider's page; billing unspecified, marked est.

Forward curves

Ladder
One Kalshi event's yes/no contracts, one per strike price.
Two-sided
A strike with a bid above 0¢ and an ask below 100¢ counts as two-sided, but is read at its midpoint only when no wider than 20 points with size on both sides, so a 1¢ bid / 99¢ ask placeholder counts as two-sided yet is never read; a point passes only with 2 non-placeholder two-sided strikes quoted 20–80%.
Implied median
The strike where a ladder’s yes-probability crosses 50%: a market estimate, not a posted or paid price.
Anchor
A forward curve's first point, labeled “Kalshi-implied”: a weekly exact-time implied median when one is usable, else the front-month average.
Tenor
A future month on the forward curve, priced by its implied median.
Carry
The change from the anchor to the furthest tenor, shown only when both pass the quality gate.