Most on-premises versus cloud comparisons are wrong in the same few ways: they compare an owned server at 100% utilization with an on-demand cloud price, leave out power, cooling, networking and staff, assume a five-year life for hardware whose useful life for frontier work may be shorter, or ignore that cloud capacity at the scale needed may simply not be available on the date needed. This course teaches a total-cost and capacity method that survives a finance review.
You start by forecasting demand in GPU-hours from real workloads: training runs, fine-tuning, inference traffic and experimentation. You then build an owned-capacity model covering capital cost, depreciation, colocation or facility cost, power at a stated PUE, network and storage, support contracts, staff and refresh, and a cloud model covering on-demand, reserved and committed pricing, capacity blocks, storage, egress and the cost of idle reservations. The break-even module shows how sensitive the answer is to utilization, power price and hardware life. The final modules turn the decision into a staged capacity plan with procurement lead times, power and space constraints, hybrid bursting and review triggers, using hypothetical worked examples throughout. All numbers in examples are illustrative; learners bring their own quotes.