induwara.lk
induwara.lkAI · Infrastructure

GPU Buy vs Rent Break-Even Calculator

Should you buy a GPU or rent one from the cloud? Enter your workload and this tool computes the break-even in months, the break-even in active GPU-hours, and the effective cost per GPU-hour of owning vs renting — for the RTX 4090, RTX 5090, A100 and H100. No signup, sources cited.

By Induwara AshinsanaUpdated Jul 15, 2026
Buy vs rent break-evenGPU cost comparison
Reference rates · 2026

Hobby fine-tunes & small-model inference; cheapest to own. Every field below is editable — override any figure with your own quote.

$

MSRP of the GPU itself.

$

PSU, CPU, RAM, chassis share.

$

On-demand/community rate you'd pay to rent.

$

EIA US avg ≈ $0.13; CEB block rates vary.

W

Board power at full load, in watts.

≈1.1 home, ≈1.4–1.6 datacenter.

$

Rack/colo fee if any. Use 0 for a home rig.

mo

How long you expect to keep using it.

50%

Share of wall-clock the GPU is actually busy.

VerdictBuy

Buying pays off after ~16.0 months at 50% utilization — within your 24.0-month horizon.

Break-even
16 mo
Verified two ways ✓
Break-even hours
5,854 h
Active GPU-hours to pay back capex
Effective owned $/hr
$0.3154
Capex amortised over your horizon + power
Effective rent $/hr
$0.44
Flat cloud rate you'd keep paying

Own vs rent — cost breakdown

Line itemOwnRent (cloud)
Upfront capex$2,199.00
Running cost / month$23.49$160.60
Cumulative at 6 mo$2,339.93$963.60
Cumulative at 12 mo$2,480.85$1,927.20
Cumulative at 24 mo$2,762.71$3,854.40
Cumulative at 36 mo$3,044.56$5,781.60

Green = cheaper option at that point. Capex is counted once, up front; the cloud column is pure pay-as-you-go.

Cumulative cost over time

0$3,372.600mo5mo11mo16mo21mo

Own (capex + running)Rent (cloud) Break-even ≈ 16 months

Preset MSRPs, cloud rates and TDPs are illustrative references (NVIDIA, Lambda, RunPod, Vast.ai, AWS; electricity from U.S. EIA, PUE from Uptime Institute) — override any field with your own quote. Capex is treated as sunk: resale value, financing interest and spot-price volatility are out of scope. Full sources are listed below the calculator.

How it works

The calculator compares two ways to get GPU time. Owning means you pay the hardware price once (capex), then only electricity and any hosting fee each month. Renting means no capex, but you pay a flat cloud rate for every GPU-hour you use. Because the cloud bill scales with usage while your electricity cost per hour is far lower, heavy users eventually recover the purchase price — the moment that happens is the break-even.

Every month is treated as 730 hours (8,760 ÷ 12). The math is fully deterministic:

  1. Power cost per active hour= TDP(kW) × PUE × electricity rate. PUE (Power Usage Effectiveness) grosses the card's draw up for cooling — about 1.1 for a home rig, 1.4–1.6 in a data centre (Uptime Institute). A 450 W card at PUE 1.1 and $0.13/kWh costs ≈ $0.064/hr.
  2. Monthly active hours = utilization% × 730. Utilization is the share of wall-clock the GPU is genuinely busy.
  3. Owned running cost / month = power cost per hour × monthly active hours + fixed hosting. Capex is excluded here — it is paid once, up front.
  4. Cloud cost / month = cloud rate × monthly active hours, using published on-demand/community rates (Lambda, RunPod, Vast.ai, AWS).
  5. Monthly saving from owning = cloud cost − owned running cost. If this is zero or negative, owning never gets cheaper and the tool says rent — no division by zero.
  6. Break-even months = capex ÷ monthly saving, where capex = purchase price + extra rig cost. Multiply by monthly active hours for the break-even in GPU-hours.
  7. Effective owned $/hr over an horizon of M months = capex ÷ (active hours × M) + power cost per hour + hosting ÷ active hours. At the break-even month this equals the cloud rate exactly — the tool verifies the break-even a second way by intersecting the two cumulative-cost curves, so the number is checked, not just asserted.
  8. Verdict: if the monthly saving is zero or less, rent. Otherwise, if break-even lands within your ownership horizon (default 24 months), buy; if it lands beyond, rent.

Version 1 keeps the model honest and conservative: the purchase price is treated as sunk (no resale credit), the purchase is assumed to be cash (no financing interest), and cloud pricing uses steady on-demand rates rather than volatile spot bids. That means a "buy" verdict is a floor — resale value would only improve it.

Worked examples

RTX 4090 · home rig · 50% utilization

Buy
  1. Capex: $1,599 card + $600 rig = $2,199
  2. Power/hr: 0.45 kW × 1.1 PUE × $0.13 = $0.06435
  3. Active hours/mo: 50% × 730 = 365
  4. Cloud/mo: $0.44 × 365 = $160.60
  5. Owned running/mo: $0.06435 × 365 = $23.49
  6. Saving/mo: $160.60 − $23.49 = $137.11
  7. Break-even: $2,199 ÷ $137.11 = 16.0 months → within 24 → BUY

H100 80GB PCIe · colo · 15% utilization

Rent
  1. Capex: $27,000 card + $5,000 rig = $32,000
  2. Power/hr: 0.35 kW × 1.4 PUE × $0.13 = $0.0637
  3. Active hours/mo: 15% × 730 = 109.5
  4. Cloud/mo: $2.99 × 109.5 = $327.41
  5. Owned running/mo: $0.0637 × 109.5 + $200 colo = $206.98
  6. Saving/mo: $327.41 − $206.98 = $120.43
  7. Break-even: $32,000 ÷ $120.43 = 265.7 months (~22 yr) → RENT

Same H100 at 90% utilization (edge: utilization flips it)

Buy
  1. Active hours/mo: 90% × 730 = 657
  2. Cloud/mo: $2.99 × 657 = $1,964.43
  3. Owned running/mo: $0.0637 × 657 + $200 colo = $241.85
  4. Saving/mo: $1,964.43 − $241.85 = $1,722.58
  5. Break-even: $32,000 ÷ $1,722.58 = 18.6 months → within 24 → BUY
  6. Same hardware, same rates — only utilization changed the verdict.

Frequently asked questions

Sources & references

Preset prices, cloud rates and TDPs were last re-checked against these sources on 2026-07-15. They are illustrative references, not a live feed — every field is editable so you can drop in a current quote. This is a cost break-even, not a performance benchmark: it does not claim a rented GPU matches an owned one in speed.

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a bug, edge case, or want to suggest an improvement?

Email me at [email protected] — most fixes ship within 24 hours.