Compare the full
GPU commitment.
Put two reserved GPU quotes on the same footing. Separate full-term expenses from cash due at signing, surface missing costs, and check whether the infrastructure actually matches.
Illustrative example. These invented figures demonstrate the calculator. They are not market prices, supplier offers, or available capacity. Editing them does not turn them into a verified quote.
Use USD throughout. Leave an unknown fee as “Not specified”; choose “Included / no extra charge” only when confirmed. The 730-hour month is an editable planning assumption, not a calendar-month or provider billing rule.
Enter your quote details, or try the illustrative example, to build your decision sheet.
A comparison is only as complete as its terms.
Term expenses
GPU count × reserved hours × GPU-hour rate, plus one-time fees and monthly extras. Prepaid compute is already part of this amount. A refundable deposit ties up cash but is not counted as an expense.
Cash due at signing
The chosen compute payment, one-time fees due at start, any recurring fees payable in advance, and the refundable deposit. “First month” is capped at the full term for shorter reservations. An advance payment is not added to term expenses again.
What still needs diligence
Equal prices do not mean equal delivery. Confirm allocation control, exact SKU, contiguous fabric, site, start/end times, support, acceptance, and remedies. Taxes, financing, currency changes, overages, and exit charges are outside this calculation unless included in your entered fees.
Per-GPU-hour cost divides term expenses by all reserved GPU-hours. Utilization scenarios divide by useful GPU-hours instead; they are sensitivity calculations, not performance forecasts. Unknown costs remain unresolved, so a known subtotal is not a complete quote or a spending ceiling.
Get a matched cluster shortlist.
Bring the workload, GPU count, region, start window, and term. Omega Gradient helps compare suitable capacity and the evidence behind it.