Evidence
What the market currently shows
Source URL, observed rate, timestamp, region, purchase model, history, benchmark evidence, and qualifying availability signals.
Procurement workflow
Use this checklist before turning a GPU cloud shortlist into committed spend. It connects workload fit, exact hardware, source-backed pricing, capacity evidence, networking, operations, security, contracts, and decision provenance so the cheapest visible rate does not become the entire procurement process.
How to use it
SaaS Sentinel can supply market pricing, historical observations, provider breadth, benchmark evidence, and some availability signals. Your team supplies workload measurements, security requirements, contractual constraints, and final approval. Do not allow a missing data field in one layer to be silently invented by another.
Evidence
Source URL, observed rate, timestamp, region, purchase model, history, benchmark evidence, and qualifying availability signals.
Assumptions
Throughput, utilization, scaling, data volume, interruption recovery, time horizon, and non-compute cost estimates.
Approval
Security, privacy, compliance, contractual risk, support expectations, budget ownership, and acceptable concentration risk.
Checklist section 1 of 9
Define the useful work before comparing infrastructure. If the workload target is vague, every downstream price comparison becomes easier to manipulate.
Checklist section 2 of 9
A GPU family name is not enough to prove equivalence. Preserve the hardware details that can change fit, throughput, or scaling.
Checklist section 3 of 9
Normalize the compute rate, then add the material commercial rules instead of hiding them inside an unexplained multiplier.
Checklist section 4 of 9
Do not turn a price listing into a stock claim. Capacity evidence needs its own source, scope, and timestamp.
Checklist section 5 of 9
Cheap compute can be a false economy if data movement or storage becomes the dominant operational cost or performance bottleneck.
Checklist section 6 of 9
The procurement decision includes the work required to keep the workload running, not only the price of the accelerator.
Checklist section 7 of 9
Treat this section as an escalation boundary: the public pricing dataset cannot answer security or legal requirements for your organization.
Checklist section 8 of 9
A low rate is not a complete commercial offer. Record the terms that determine what happens when the workload, bill, or relationship goes wrong.
Checklist section 9 of 9
A good infrastructure decision can be reviewed later. Preserve the inputs that came from evidence and the assumptions that came from your team.
Final decision record
A procurement record should explain what was selected, what evidence was current at the time, which assumptions drive the result, what alternative was considered, and what change would cause the team to revisit the decision.
Provider, exact GPU/node, region, purchase model, expected scale, and source-backed rate.
Cost per completed workload, technical fit, availability evidence, operational fit, and material commercial constraints.
Price movement, capacity loss, workload change, throughput miss, contract change, security requirement, or a better evidenced alternative.
Keep a reviewable record
These tools can help preserve the recommendation and its unresolved checks. Use only the steps you need; completing them is not a condition forrequesting independent review. Checking a box here does not supply evidence or grant security, legal, or procurement approval.
1 · Shortlist
Enter the workload and hard requirements in the Decision Room, inspect sources, exclusions, and unknowns, then export the decision JSON. Keep published pricing separate from proof of capacity and preserve the assumptions you tested with the workload calculators.
2 · Provider evidence, when needed
After completing the workload brief, select one candidate andexport its evidence request. Retain the original request JSON. A provider can use it in theguided response tool; Markdown or a response template alone cannot replace it. Inspect the request before choosing to share it. If the brief contains details you cannot disclose, revise the brief and regenerate the matching request; keep the generated JSON intact. The site does not send it.
Review the returned responselocally with both the original request JSON and completed response JSON. Inspect scope, expiry, and missing evidence, then export the reviewed Assurance handoff. A ready result does not authenticate the provider or approve the purchase.
3 · Cost and risk
Import the decision JSON into the Assurance Room, then optionally import the reviewed provider handoff. Inspect proposed costs and gates before applying them. Record total-cost assumptions, evidence, unresolved risks, and responsible human sign-offs; retain the resulting Assurance JSON.
4 · Revalidation
Import the matching decision and Assurance JSON files into theDecision Monitor to compare the record with the current public catalog. Review material changes, expired evidence, and sign-offs needing renewal. This runs when you open and use the tool; it does not schedule private monitoring, store your dossiers durably, or send alerts.
Imported files and edits stay in the local tool tab. Export the files you need before closing it and store them under your own controls. Exports can contain commercial or confidential details: inspect them before sharing. Keep the exact JSON intact for validated handoffs; revise the brief and regenerate a request when its scope cannot be disclosed. A redacted Markdown copy or printout can support human discussion.