Start here

Use GPU cloud data as a decision system

Turn workload requirements and source-backed market evidence into a shortlist, a buyer-owned decision record, and a review of costs and risks. This guide shows which tools and files connect each step, and where human verification remains necessary.

  • Choose by completed workload cost, not GPU-hour alone
  • Keep published price and live capacity as separate claims
  • Verify assumptions before moving from shortlist to purchase

Seven-step workflow

From a vague GPU requirement to a defensible cloud decision

Start with the workload, then preserve the evidence and assumptions behind the choice. Use the steps that fit your decision; you can request an independent review without completing the tools. Imported files and edits stay in the local tool tab. Export what you need before closing it and retain the matching JSON files. Inspect every export before sharing; use a redacted human-readable copy for discussion and keep machine-readable JSON intact for the validated handoffs.

Step 01

Define the workload and hard requirements

Record the workload, budget, region, memory, topology, interruption tolerance, and evidence requirements in the Decision Room. Use measured throughput where available; a benchmark for another workload is not a performance guarantee.

Define a workload brief →

Step 02

Build and retain an evidence-backed shortlist

Run the Decision Room against comparable published offers. Inspect sources, exclusions, unknowns, and revalidation triggers, then download the decision JSON for later imports. Published price and deployment eligibility do not prove live capacity.

Build a decision dossier →

Step 03

Challenge the workload economics

Use inference, training, batch, or cloud-vs-owned calculators to test throughput, utilization, scaling, and interruption assumptions. Keep storage, egress, support, taxes, and operational costs explicit; the normalized GPU rate is only part of total cost.

Choose a workload calculator →

Step 04

Ask for evidence tied to one candidate

After building a shortlist and completing the workload brief, select a candidate and export its provider evidence request. Retain the exact request JSON and inspect it before deciding to share it with that provider. If the brief includes details you cannot disclose, revise it and regenerate a matching request; keep the generated JSON intact. The site does not send requests. Guided response authoring needs this exact JSON, not only the Markdown or response template.

Create a scoped evidence request →

Open guided provider response →

Step 05

Review returned evidence against the original request

Import the retained request JSON and completed response JSON into the Decision Room buyer review. Inspect scope mismatches, expiry, unanswered questions, and commercial gaps. Export the reviewed Assurance handoff when useful; a ready result does not authenticate the provider or approve the purchase.

Review a returned response →

Step 06

Resolve total cost, risk, and human sign-offs

Import the decision JSON into the Assurance Room, then optionally import the reviewed provider handoff. Inspect proposals before applying them, document costs and evidence, resolve risk gates, and record the responsible human sign-offs. Export the matching Assurance JSON; contract, security, and procurement authority remain with your team.

Complete decision assurance →

Step 07

Revalidate the dated decision

Import the matching Decision Room and Assurance JSON dossiers into the Decision Monitor and replay them against the current public catalog. Inspect material changes, expired evidence, and sign-offs needing review. This is a local check when you run it: it does not schedule private monitoring or send alerts.

Revalidate a decision →

Deep-dive library

Understand the concepts behind the tools

The workflow tells you what to do. These guides explain the parts that most often create bad comparisons: ambiguous terminology, unsupported capacity assumptions, purchase-model risk, and procurement decisions that omit material evidence.

Product guide

How to use the GPU cloud pricing comparator

Filter comparable offers by GPU, provider, region, market and availability, model one GPU-hour horizon, verify the evidence, and share a reviewable comparison without turning the cheapest row into an automatic recommendation.

Use the pricing comparator guide →

History

How to read GPU cloud price history

Interpret retained observations, low/median/high snapshot ranges, real rate moves, evidence-only refreshes and price dispersion without mistaking a descriptive audit trail for a forecast.

Read the price history guide →

Market index

How to read the GPU Cloud Price Index

Interpret provider-balanced current medians, provider P25–P75 dispersion, raw ranges and fixed-cohort movement without confusing a published-price market signal with transaction pricing or capacity.

Read the Price Index guide →

Reference

GPU cloud glossary

Understand the pricing, availability, hardware, networking, and workload terms that change whether two GPU cloud offers are actually comparable.

Open the glossary →

Evidence

GPU availability evidence

Learn why a published price is not a capacity guarantee, how freshness and region scope matter, and how SaaS Sentinel keeps unknown availability explicit.

Read the availability guide →

Purchase model

Spot vs on-demand GPU

Compare interruptible and on-demand capacity using checkpointing, restart cost, deadlines, parallelism, operational maturity, and cost per completed workload.

Compare spot and on-demand →

Procurement

GPU cloud procurement checklist

Turn workload, hardware, pricing, availability, networking, operations, security, and contract evidence into a reviewable procurement record before committing spend.

Open the procurement checklist →

Integration

GPU pricing API and data feeds

Use the versioned read-only API, change feed, public status endpoint, source hashes, and OpenAPI contract when a repeatable integration is stronger than copying values from the interface.

Open API documentation →

Choose the right tool

What each SaaS Sentinel surface is designed to answer

The tools deliberately overlap enough to let you move from market discovery to a specific cost decision, but they are not interchangeable. Use the surface that matches the question you are trying to answer.

Decision record

Decision Room

Filter by workload requirements, challenge the shortlist, and retain the decision JSON. The same room creates candidate-specific evidence requests and reviews returned responses against the original request JSON.

Build and retain a shortlist →

Provider evidence

Guided provider response

Use the exact original request JSON to author a typed response locally. Evidence and commercial terms remain attributable claims for the buyer to verify; contract-valid export does not establish identity, authority, or purchase approval.

Prepare a scoped response →

Costs and approvals

Assurance Room

Import a decision JSON, assess fully-loaded costs and downside scenarios, and resolve evidence gates with responsible human sign-offs. A reviewed provider handoff can supply proposals for inspection; it does not silently approve costs or risks.

Review TCO and risk →

Decision revalidation

Decision Monitor

Import matching decision and Assurance JSON files to check the dated record against the current catalog. This local replay distinguishes material changes from drift and identifies evidence or approvals to revisit. It does not deliver messages or run in the background.

Check a retained decision →

Market discovery

GPU cloud pricing

Use the global catalog when you need to discover which providers and regions publish a comparable rate for a GPU. Filter before interpreting the minimum price, and keep market type and evidence status visible while building the shortlist.

Open the pricing catalog →

Provider choice

Provider and GPU comparisons

Use comparison pages after you know the GPU family and need to understand meaningful price gaps across providers. These pages are strongest when the compared offers share the same decision intent rather than merely containing similar keywords.

Browse provider comparisons →

Performance evidence

Benchmarks

Use the benchmark layer when an hourly rate alone cannot tell you how quickly a workload completes. Benchmark evidence is kept separate from pricing evidence so a result is not silently generalized to a different workload, configuration, or provider.

Inspect verified benchmarks →

Workload economics

Calculator hub

Choose inference, training, batch, or cloud-vs-owned TCO from the decision you need to make. Each calculator keeps source-backed market rates separate from the workload assumptions you control.

Choose a calculator →

Timing

Price history and market index

Use history to understand whether the current rate is isolated or part of a broader move. Use the provider-balanced index for market direction rather than treating the cheapest single listing as a proxy for the entire GPU cloud market.

Open price history →

Monitoring

GPU price alerts

Use the global and model-level feeds when you want the research loop to continue after the initial decision. Alerts surface verified price changes; they do not claim that a listed GPU is currently provisionable unless separate availability evidence supports that claim.

Open price alerts →

Read the evidence correctly

Four distinctions that prevent expensive mistakes

Most bad GPU cloud comparisons are not caused by arithmetic. They come from treating different kinds of evidence as if they proved the same thing.

Published price is not live capacity

A fresh price can be real while the GPU is unavailable in your required region. SaaS Sentinel therefore reports availability evidence separately and refuses to infer capacity from price alone.

Same GPU family is not always the same product

PCIe, SXM, NVL, VRAM variants, GPU count, interconnect, CPU, RAM, and the surrounding node can matter. Verify the actual configuration before treating two hourly rates as substitutes.

Spot and on-demand answer different risk questions

Spot can lower compute cost but adds interruption risk. Compare the price advantage against checkpointing, restart cost, deadline sensitivity, and the workload's tolerance for eviction.

Compute price is not always total infrastructure cost

Storage, egress, support, minimum billing, taxes, reserved commitments, and engineering overhead may sit outside the normalized GPU rate. Treat them as explicit scenario assumptions, not hidden constants.

Example playbooks

Three ways different teams can use the same data

ML engineering

Choose infrastructure for a training run

Start from a compatible benchmark or your own measured throughput, calculate expected runtime, compare fresh provider rates for the required GPU, verify region and availability evidence, then test whether a cheaper spot option still wins after interruption risk.

Inference platform

Reduce cost per unit of useful output

Shortlist GPUs by technical fit, feed measured tokens-per-second or request throughput into the inference calculator, model utilization realistically, and compare unit economics rather than assuming the lowest GPU-hour produces the lowest serving cost.

FinOps / procurement

Challenge a recurring GPU cloud bill

Compare the current provider against the market range, inspect regional and purchase-model spreads, review historical movement, then run cloud-versus-owned TCO for sustained demand. Preserve source links and assumptions so the recommendation can be reviewed rather than presented as a black box.

Boundary conditions

What the tools should not make you believe

SaaS Sentinel is built to make uncertainty visible. A useful decision system should tell you where evidence stops instead of turning every missing field into a confident recommendation.

A listed rate does not guarantee stock, quota, account approval, or successful provisioning.

A benchmark from one exact workload is not proof of identical performance on another model or software stack.

A normalized GPU-hour does not automatically include storage, egress, taxes, support, or operational labor.

A current cheapest offer is a market observation, not a sponsored ranking or a guarantee that it is the best technical fit.