Procurement workflow

GPU cloud procurement checklist

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.

  • 54 review checks across nine decision areas
  • Pricing and availability remain separate evidence categories
  • Security and legal approval stay with the responsible human owner

How to use it

Separate evidence, assumptions, and approvals

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

What the market currently shows

Source URL, observed rate, timestamp, region, purchase model, history, benchmark evidence, and qualifying availability signals.

Assumptions

What your workload model needs

Throughput, utilization, scaling, data volume, interruption recovery, time horizon, and non-compute cost estimates.

Approval

What a responsible owner must decide

Security, privacy, compliance, contractual risk, support expectations, budget ownership, and acceptable concentration risk.

Checklist section 1 of 9

1 · Workload definition

Define the useful work before comparing infrastructure. If the workload target is vague, every downstream price comparison becomes easier to manipulate.

1 · Workload definition

Checklist section 2 of 9

2 · Exact GPU product and topology

A GPU family name is not enough to prove equivalence. Preserve the hardware details that can change fit, throughput, or scaling.

2 · Exact GPU product and topology

Checklist section 3 of 9

3 · Pricing and billing

Normalize the compute rate, then add the material commercial rules instead of hiding them inside an unexplained multiplier.

3 · Pricing and billing

Checklist section 4 of 9

4 · Availability and capacity evidence

Do not turn a price listing into a stock claim. Capacity evidence needs its own source, scope, and timestamp.

4 · Availability and capacity evidence

Checklist section 5 of 9

5 · Storage, data and networking

Cheap compute can be a false economy if data movement or storage becomes the dominant operational cost or performance bottleneck.

5 · Storage, data and networking

Checklist section 6 of 9

6 · Reliability and operations

The procurement decision includes the work required to keep the workload running, not only the price of the accelerator.

6 · Reliability and operations

Checklist section 7 of 9

7 · Security, privacy and compliance

Treat this section as an escalation boundary: the public pricing dataset cannot answer security or legal requirements for your organization.

7 · Security, privacy and compliance

Checklist section 8 of 9

8 · Contract, support and commercial risk

A low rate is not a complete commercial offer. Record the terms that determine what happens when the workload, bill, or relationship goes wrong.

8 · Contract, support and commercial risk

Checklist section 9 of 9

9 · Decision evidence and sign-off

A good infrastructure decision can be reviewed later. Preserve the inputs that came from evidence and the assumptions that came from your team.

9 · Decision evidence and sign-off

Final decision record

Write the recommendation so another person can challenge it

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.

Selected option

Provider, exact GPU/node, region, purchase model, expected scale, and source-backed rate.

Why it wins

Cost per completed workload, technical fit, availability evidence, operational fit, and material commercial constraints.

What could invalidate it

Price movement, capacity loss, workload change, throughput miss, contract change, security requirement, or a better evidenced alternative.

Keep a reviewable record

Connect the checklist to the decision and evidence files

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

Retain the decision JSON

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

Keep the exact request and returned response

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

Export the matching Assurance JSON

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

Replay both dated dossiers

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.