GlobeGPU Cloud GPU price index

Methodology

How a price gets onto this site — and what does not.

One number is published here: what one GPU costs for one hour. Everything below is what had to be true for a figure to earn a row.

Rows read
7,714
4,402 kept · 3,297 refused · 15 merged
Sources
5
all inside their freshness rule

The rules

One unit

Providers quote what suits them: per instance, per minute, per month, in their own currency. Those figures cannot be compared with each other, so each is converted to US dollars per GPU per hour and the original is kept beside it on the chip's page.

The conversion is arithmetic on numbers the provider published — the instance price and the GPU count — never an estimate. Where a provider does not state how many GPUs are in an instance, the offer is dropped rather than divided by a guess.

Currency

One source quotes in euros. It converts at the European Central Bank's daily reference rate for 2026-08-21 — 1 EUR = 1.1699 USD — and both the euro figure and the rate used are printed next to every converted price. ECB reference rates ↗

Reference rate published each working day at 16:00 CET. Not a dealing rate.

Same chip, or not

An exact variant is vendor, family, form factor and memory. Two providers are only compared when all four match. An H100 SXM and an H100 PCIe are both sold as "H100" and are different silicon at different prices; a 40 GB A100 and an 80 GB A100 likewise. Merging them would produce a tidier table and a false one.

Marketing prefixes are dropped for grouping only — "Tesla V100" and "V100 SXM2" are one card written two ways. Every offer keeps the provider's exact wording, shown on the chip's page, so this normalisation can be checked rather than trusted.

On demand and spot

Headline rates are on-demand: capacity you can rely on. Spot, bid and low-priority prices are a different product — capacity that can be taken back — so they never set a headline figure and are shown separately, in the provider's own term for them.

Freshness

Each source carries its own rule: 12 hours for a live marketplace, 48 for a published catalogue. Past that, the reading is shown as stale everywhere it appears. It is never silently restamped as current.

Specifications

Vendor-published figures. FP16 throughput is dense tensor throughput with no sparsity assumed; vendors often headline the sparse figure, which is twice as large. A chip with no cited vendor figure shows no throughput number and is priced all the same.

Coverage

this reading

What each feed offered, what was kept, and what was refused. A price index that drops quietly cannot tell the difference between a provider with no GPUs and a parser that stopped working.

ProviderFeedRows readKeptMergedRefusedRead
Azure Azure Retail Prices API 7,571 4,322 3,249 1 min ago
RunPod RunPod GraphQL API 48 35 13 1 min ago
Scaleway Scaleway public product catalogue 58 17 15 26 1 min ago
Vultr Vultr Plans API 24 15 9 1 min ago
Akamai Cloud Linode Types API 13 13 0 1 min ago

Why rows were refused

  • 3,249 — no gpu count in size doc
  • 17 — billing unit not a time
  • 11 — no price published
  • 9 — integrated gpu not a card
  • 6 — multi variant card cannot divide
  • 3 — fractional gpu slice
  • 2 — mig partition

The largest category is Azure meters whose VM size is not documented with a GPU count. Without the count there is no per-GPU price, only an instance price, and those cannot share a column.

Quarantined hardware

Labels this index could not place on a known card. Kept by name for a human to look at, never guessed into the nearest match.

  • PRO 6000 MIG 24GB — runpod
  • PRO 6000 MIG 48GB — runpod
  • Apple M2 — scaleway
  • Apple M2 Pro — scaleway
  • Apple M2 Pro for Asahi — scaleway
  • Apple M1 — scaleway
  • Apple M4 — scaleway
  • Apple M4 Pro — scaleway