How GPU Tracker calculates the numbers you see
GPU Tracker compares live cloud GPU listings, then adds context most pricing pages omit: storage and egress assumptions, billed-when-stopped behavior, spot volatility signals, and availability quality. This page explains what is measured, how often it updates, and where estimates can differ from your final invoice.
Data Sources
Refresh Frequency
Prices and inventory are refreshed on a scheduled pipeline every 6 hours. Provider APIs and marketplace listings may change faster than that, so treat the data as a high-quality comparison snapshot, not a guaranteed quote.
Always confirm the final provider invoice and checkout page before provisioning.
True Monthly Cost (TMC)
True Monthly Cost is an estimate designed to answer: “What will this workload likely cost over a month?” It starts with compute spend and layers in assumptions such as storage, egress, minimum billing increments, and billed-when-stopped behaviors when applicable.
TMC is intentionally conservative compared with raw $/hr comparisons. The goal is decision quality, not optimistic marketing math.
For exact assumptions, use the in-product TMC panel and adjust workload hours, storage, and egress to match your project.
Availability & Risk Signals
Availability and interruption risk summarize listing quality and runtime reliability signals, especially for spot / marketplace capacity. These are indicators, not SLAs.
A low price can still be a poor choice if your job is long-running, stateful, or expensive to restart. GPU Tracker highlights this tradeoff so you can compare price against survival probability.
What this page is for
This methodology page is the source of truth for how comparisons, pricing estimates, and risk signals are generated. If you cite GPU Tracker in procurement docs or internal reviews, link this page so teammates understand the assumptions behind the numbers.