Quick start
A defensible comparison in seven steps
The order matters. Every extra filter should represent a real requirement, not a preference added after seeing a cheap row. That keeps the shortlist reproducible and reduces accidental apples-to-oranges comparisons.
1 · GPU and node
Start with the accelerator you can actually use
Select the GPU model, then narrow GPU variant and GPUs / node when the workload requires an exact configuration. “All variants” and “Any node size” retain different products; they do not establish equivalent memory, topology, or performance. If the accelerator is undecided, inspect benchmarks or workload calculators first.
2 · Region
Restrict the geography when it is a real constraint
Choose the required named region when latency, data residency, networking, quota, or an existing architecture makes geography material. “Global / unspecified” means the source did not map the row to a named region; it is not a promise of worldwide capacity.
3 · Market
Keep on-demand and spot economics separate
Choose on-demand or spot when the purchase model is fixed. Spot can have a lower published rate but adds interruption risk, so do not treat it as an interchangeable substitute for an on-demand workload without pricing the operational overhead.
4 · Availability
Filter only by evidence you are willing to rely on
Use available, unavailable, limited, or not evidenced as an evidence filter. “Not evidenced” is deliberately different from unavailable: it means the catalog does not currently have qualifying independent availability evidence for that row.
5 · GPU-hours
Set the same workload horizon for every row
The comparator multiplies the normalized USD/GPU-hour rate by your monthly GPU-hours. The default 160 hours is a planning scenario, not a universal month. Enter the workload horizon you expect to buy before comparing the resulting budget exposure.
6 · Sort
Use sorting to answer one question at a time
Sort by lowest or highest price, freshness, or provider. A lowest-price sort identifies a price floor inside the selected evidence boundary; it is not a recommendation and does not prove that capacity, support, networking, or workload fit are equivalent.
7 · Evidence
Open the source before the buying decision
Use the official pricing source on the shortlisted row. Where a separate availability source exists, inspect that too. Confirm the provider page, exact product context, region, market type, billing unit, GPU count, and any terms that can change the invoice.