GPU pricing / Commercial investigation

H100 Quote Checklist: What to Ask Before Choosing GPU Cloud

Short answer: An H100 quote is worth comparing only after the provider exposes the GPU shape, minimum rental window, storage, data transfer, capacity model, retry risk, and support terms.

Decision rule
  • Pick the quote with the best useful GPU-hour economics, not the lowest visible H100 hourly rate.
  • Verify current provider pricing directly before buying or migrating.

RunPlacement quiz

Pressure-test this workload

Pick the quote with the best useful GPU-hour economics, not the lowest visible H100 hourly rate.

Uses workload type, budget, GPU need, data movement, priority, and ops tolerance.
Use the quiz

Right fit

  • You have at least one H100, A100, L40S, or similar accelerator quote.
  • The advertised hourly rate looks cheap, but the total job cost is unclear.
  • The workload may be affected by queue time, failed jobs, storage, or egress.

Quick checks

  • Ask whether persistent storage, snapshots, and data transfer are included.
  • Ask what happens when capacity is unavailable at the required start time.
  • Ask whether failed jobs, retries, and checkpoint restores create extra billable hours.
  • Ask which support tier owns provisioning or incident response.

Rough math

  • Useful GPU-hour cost = listed GPU hourly rate / expected utilization.
  • Estimated training run = GPU rate x GPU count x runtime + storage + transfer + retry allowance.
  • Monthly inference cost = baseline GPU hours + burst hours + storage + observability + support.

Red flags

  • The quote shows GPU price but not storage or network terms.
  • The provider cannot explain capacity availability for your region or window.
  • The workload requires managed operations but the quote assumes self-service infrastructure.

What to do next

  • Collect one real quote or bill line.
  • Use the GPU cloud quote checklist to normalize the fields.
  • Run the placement quiz once the workload shape and data path are known.

Related resources

Use a worksheet before making the call

These supporting pages turn the decision into fields a buyer, engineer, or founder can actually compare.

GPU pricingGPU Cloud Quote ChecklistChecklist / 7 sections / sourced

A practical checklist and visual worksheet for comparing GPU cloud quotes beyond the advertised hourly rate.

 Workload placementWorkload Placement WorksheetChecklist / 7 sections / sourced

A practical worksheet and decision map for deciding where a workload should run before provider choice hardens.

Related decisions

Keep narrowing the placement question

Follow the adjacent pages when the first answer exposes a deeper cost driver or operating constraint.

GPU pricingGPU Cloud Idle Cost: How to Price Wasted Accelerator TimeCost estimation

GPU cloud idle cost is the gap between paid accelerator time and useful workload progress. It matters most for training retries, batch queues, and inference fleets with low baseline utilization.

 GPU pricingRunPod vs Lambda GPU Cloud: How to Compare the FitProvider comparison

RunPod vs Lambda is less about one universal winner and more about workload fit. Compare GPU availability, storage behavior, operational model, support needs, and total job cost for your actual workload.

 GPU pricingCoreWeave vs AWS GPU Cloud: When Specialized GPU Cloud FitsProvider comparison

CoreWeave vs AWS is a category decision first. Specialized GPU cloud can fit GPU-heavy work, while AWS can fit teams that need broader cloud services, existing controls, or tighter integration with current infrastructure.

Framework

Use the underlying decision model

These framework pages define the terms and formulas behind this specific decision.

GPU pricingUseful GPU-Hour Frameworkuseful GPU-hour

Useful GPU-hour cost is the better comparison unit when GPU providers differ in utilization, queueing, reliability, storage behavior, or operational model.

 Workload placementWorkload Placement Frameworkworkload placement

Choose workload placement by matching the workload's cost driver, data movement, performance needs, operational tolerance, and commitment horizon to the right infrastructure category.

FAQ

What is the biggest H100 quote mistake?

The biggest mistake is comparing hourly rates before checking utilization, data movement, storage, capacity reliability, and operational responsibility.

Is the cheapest H100 cloud usually the best choice?

Not automatically. The cheapest quote can lose if it creates queue delays, failed runs, data transfer surprises, or support work the team cannot absorb.

What should I ask before signing a GPU cloud quote?

Ask what is included in the GPU rate, how storage and transfer are billed, how capacity is reserved, and whether failed jobs create extra billable time.

Sources

RunPlacement quiz

Pressure-test this workload

Pick the quote with the best useful GPU-hour economics, not the lowest visible H100 hourly rate.

Uses workload type, budget, GPU need, data movement, priority, and ops tolerance.
Use the quiz