Methodology and sources

Every number comes from a provider’s own public pricing page. Here is exactly how.

Sources, checked daily

The daily check

  1. Once a day a scheduled job downloads each provider’s pricing page and reads every GPU row on it.
  2. Known prices are updated. GPUs that are new on a page are added automatically. A GPU that has vanished from its provider’s page is removed after seven consecutive successful checks (so a one-day page glitch removes nothing).
  3. A price is published only if it was read cleanly, is greater than zero, and (for existing rows) is within 0.4×–3× of the previous value. Anything else is held back, never published unreviewed.
  4. If a provider’s page can’t be read, its previous prices stay and its date does not advance, so you can see it is stale.
  5. Every addition, removal and price change is logged and shown under “Recent price changes” on the home page.

The data is published as gpu-prices.json with every source URL.

How prices are normalised

Not included

Storage, egress, taxes, reserved/spot/enterprise pricing, availability, performance, and providers that don’t publish a clear price (quote-only, “contact sales” rows) or are marketplaces where individual hosts set prices. RunPod’s “Community Cloud (from)” is the lowest price its page publishes, not a guaranteed price. Nebius rows whose on-demand price is only given as “from” are skipped.

Corrections

Spotted a price that no longer matches a provider’s page? Tell us via contact with the source link and it will be fixed.