Skip to content
Calcrivo

Cloud TCO Calculator

Compare a fully loaded cloud bill against on-premises capex, power, cooling, rack space and staff on one monthly basis.

Inputs

USD/month
USD/month
USD/month
USD/month

Databases, operating systems and third-party software billed separately from compute.

% of spend

Enterprise support is a percentage of usage, commonly 3–10%.

FTE
USD/year
USD
months
USD
years

Most estates depreciate servers over 3–5 years and refresh at the end.

kW
ratio

On-premises rooms typically run 1.5–2.0; hyperscalers run 1.1–1.6.

USD/kWh
USD/month
% of capex per year
FTE

Cloud Monthly TCO

$105,470.56

On-Premises Monthly TCO

$125,701.40

Monthly Advantage to Cloud

$20,230.84

Advantage as a Share of On-Premises

16.1%

Cloud Annual TCO

$1,265,646.67

On-Premises Annual TCO

$1,508,416.80

Provider Support Charge

$4,165.00

Which Model Wins

Cloud is cheaper on this model

Step by step

  1. Values used

    Cloud compute spend = 42,000 USD/month; Cloud storage spend = 8,000 USD/month; Cloud network and egress spend = 3,500 USD/month; Licensing carried into the cloud = 6,000 USD/month; Provider support charge = 7 % of spend; Cloud platform engineers = 2.50 FTE; Fully loaded cost per engineer = 150,000 USD/year; One-off migration cost to amortise = 380,000 USD; Amortisation period = 36 months; On-premises hardware capex = 1,800,000 USD; Depreciation and refresh cycle = 4 years; Sustained power draw = 45 kW; Data-centre PUE = 1.70 ratio; Electricity price = 0.1200 USD/kWh; Rack space, cross-connects and facilities = 4,500 USD/month; Hardware maintenance and support = 18 % of capex per year; On-premises infrastructure engineers = 4 FTE

  2. Cloud TCO

    cloud = usage + usage × support% + FTE cost ÷ 12 + migration ÷ amortisation months; on-premises = capex ÷ (years × 12) + kW × PUE × 730 × electricity price + maintenance ÷ 12 + facilities + FTE cost ÷ 12.

  3. Cloud Monthly TCO

    = 105,470.56

  4. On-Premises Monthly TCO

    = 125,701.40

  5. Monthly Advantage to Cloud

    = 20,230.84

  6. Advantage as a Share of On-Premises

    = 16.1

  7. Cloud Annual TCO

    = 1,265,646.67

  8. On-Premises Annual TCO

    = 1,508,416.80

How it works

The cloud side adds the meters you see on the invoice plus the two that never appear on it: the people who run the platform and the migration you already paid for, spread over the months it serves. The on-premises side converts capex into a monthly depreciation charge and adds the facility costs that make hardware run — power multiplied by PUE, maintenance as a percentage of capex, rack space and staff. A comparison that puts a cloud invoice next to a hardware purchase order is meaningless, because one is a monthly operating cost and the other is a multi-year asset. Normalising both to a fully loaded monthly figure is the only fair basis, and these figures are planning estimates rather than accounting or tax advice.

Formula

Cloud TCO

cloud = usage + usage × support% + FTE cost ÷ 12 + migration ÷ amortisation months; on-premises = capex ÷ (years × 12) + kW × PUE × 730 × electricity price + maintenance ÷ 12 + facilities + FTE cost ÷ 12.

730
Hours in an average billed month
PUE
Power usage effectiveness — total facility power divided by IT power
amortisation
Spreading the one-off migration cost across the months it benefits

Frequently Asked Questions

How is Cloud TCO calculated?

cloud = usage + usage × support% + FTE cost ÷ 12 + migration ÷ amortisation months; on-premises = capex ÷ (years × 12) + kW × PUE × 730 × electricity price + maintenance ÷ 12 + facilities + FTE cost ÷ 12. The cloud side adds the meters you see on the invoice plus the two that never appear on it: the people who run the platform and the migration you already paid for, spread over the months it serves. The on-premises side converts capex into a monthly depreciation charge and adds the facility costs that make hardware run — power multiplied by PUE, maintenance as a percentage of capex, rack space and staff.

Why does Cloud TCO matter?

A comparison that puts a cloud invoice next to a hardware purchase order is meaningless, because one is a monthly operating cost and the other is a multi-year asset. Normalising both to a fully loaded monthly figure is the only fair basis, and these figures are planning estimates rather than accounting or tax advice.

What values do I need to enter?

This calculator takes 17 inputs: Cloud compute spend, Cloud storage spend, Cloud network and egress spend, Licensing carried into the cloud, Provider support charge, Cloud platform engineers, Fully loaded cost per engineer, One-off migration cost to amortise, Amortisation period, On-premises hardware capex, Depreciation and refresh cycle, Sustained power draw, Data-centre PUE, Electricity price, Rack space, cross-connects and facilities, Hardware maintenance and support, On-premises infrastructure engineers. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Why multiply power by PUE?

PUE captures everything the facility burns beyond the servers themselves — cooling, UPS losses, lighting and distribution. At a PUE of 1.7 every kilowatt of IT load draws 1.7 kilowatts from the grid, so ignoring it understates the on-premises electricity bill by about 40%.

You might also need