GPU Cloud Quote Comparison Checklist

• Accelerator fields name what is being priced, so a buyer is not comparing an H100 SXM cluster against a single L40S box.
• Commercial fields name what the buyer commits to, including minimum spend, term length, change rights, and the rate paid for capacity used outside the commitment.
• Capacity and reliability fields expose access terms that determine whether the quoted hours can actually be delivered when the workload needs them.
• Quote-quality fields make the comparison auditable: who quoted, on what date, and with what assumptions about region and configuration.

• Quote A is cheaper on rate but binds capacity and region; the commitment is only a saving if utilization stays above the break-even monthly hours.
• Quote B is more flexible but spot risk and lower networking can slow or restart a 128-GPU job, raising effective completed-workload cost.
• A side-by-side row that says "$4 vs $5" hides everything that actually differs; the eleven-field row does not.
• Numbers in the example are illustrative; a real comparison requires verified quote text and a date for each row.

Example figures are illustrative calculations, not current quoted market prices.

• A rate is only a market signal when the eleven fields beside it are recorded; a number without context is noise.
• Average quotes across providers say little if the underlying capacity, term, and region differ.
• Spread between commitment rates and on-demand rates communicates how providers value certainty of demand.
• Quote date and region are required so older or distant quotes are not mistaken for current local market conditions.

Market read: comparable quote records turn private deals into public structure. Without the rubric, every quote is a one-off; with it, a buyer reads a market.

• 1. GPU generation: chip model, board form factor (SXM, PCIe), memory capacity, and connectivity (NVLink, InfiniBand). H100 SXM is not the same offering as H100 PCIe.
• 2. Hourly and effective monthly cost: published rate per GPU-hour and the implied monthly cost at full utilization, plus a row at the expected utilization the buyer can sustain.
• 3. Minimum commitment: term length, minimum monthly spend, prepay structure, and whether unused capacity can be reclaimed or sold back.
• 4. Region and latency: physical region, available zones, end-user latency budget, and whether the buyer can change region during the term.
• 5. Capacity and quota: connected cluster size available now, lead time for the required block, soft quotas, and what triggers a manual approval.
• 6. Networking: interconnect type and bandwidth between GPUs in a node and between nodes, plus any topology constraints on a multi-node job.
• 7. Storage and egress: included high-speed storage, metered overflow, and per-GB egress charges for moving model weights, data, and checkpoints out of the region.
• 8. SLA and support: availability target, remedies if missed, support tier included, response-time commitment, and named escalation path.
• 9. Interruption risk: spot or interruptible eligibility, expected eviction rate by region, checkpointing assumptions, and the contract treatment of forced interrupts.
• 10. Flexibility: rights to pause, change GPU type, change quantity, extend or shorten the term, transfer capacity to another project, and renegotiate before renewal.
• 11. Quote source and date: the named source contact, quote document or page URL, the effective date, and any expiry on the quoted terms.

Decision check: a quote can only be chosen when the eleven-field row is filled in and the gaps named. An empty field is a question, not a permission.