Resolve the key procurement questions.
What if our GPU demand changes during the term?
The offer is a 36-month minimum commitment. The page does not state reduction, cancellation or ramp-down rights. Get those terms written into the agreement before you sign.
How do we verify capacity and delivery?
Ask for a dated, region-specific quote. It should name the GPU model and count, the configuration, and the provisioning date. We do not publish live inventory or a standard lead time.
What is included, and when are we billed?
Payment cadence and inclusions are set per deployment. Ask the quote to itemize compute, networking, storage, egress, support, setup fees, invoice timing and any minimums.
What SLA and support will we receive?
SLA and support are deployment-specific. Require the uptime target, response model, support coverage and remedies to be stated in the contract.
Can we keep our existing cloud for burst demand?
Yes. Commit only the predictable baseline. Keep cloud for spikes, experiments and workloads you cannot forecast.
Still deciding? Read how to approach the commitment question and how to split baseload from burst.