Cloud TCO Calculator
Total a cloud platform's recurring and one-off cost over a period.
What this calculator does
An explicit component model: each component is named and entered by the user, extended over the months covered, with one-off costs added once. Components left at zero are excluded and reported as excluded.
Inputs and what they mean
- Currency
- — Amounts are shown in the currency you pick. No exchange rate is applied..
- Months covered
- — number value.
- Compute cost per month
- — number value.
- Storage cost per month (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Network and data transfer per month (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Software licences per month (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Support plan per month (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Staff and operations per month (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- One-off migration cost (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- One-off training cost (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Price as of (optional)
- — The date you took these prices. It is shown with the result so the figure is never read as a current vendor price..
- Price source (optional)
- — Where the prices came from. Shown with the result..
How to use it
- Enter your own figures — the calculator never fills in a rate, price or benchmark for you.
- Press Calculate to see the result.
- Read the formula, variables, assumptions and source below the result before you rely on it.
Formula
TCO = (Sum of recurring monthly components × Months) + Sum of one-off components
Worked example
Three years of a platform
Every component is one you enter; anything left at zero is excluded and shown as excluded.
Reading the result
The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.
Limitations and assumptions
Results depend entirely on the figures you enter and are rounded for display. They are for general information and education, not professional advice.
Reference: The Linux Foundation — Workload optimisation — FinOps Framework
Last reviewed:
Common questions
Formula, source and verification
Recurring components are summed and extended over the months covered, then one-off costs are added.
The question it answers: What is the total cost of this platform over the next few years, recurring and one-off?
The formula
TCO = (Sum of recurring monthly components × Months) + Sum of one-off components
- m — Months covered
- (month). Length of the period.
- R — Recurring components
- (currency). Compute, storage, network, licences, support and staff per month; every one but compute is optional.
- O — One-off components
- (currency). Optional migration and training costs.
Units: Currency; months.
What kind of calculation this is
Business input model. The answer depends on business figures only you can supply, such as your own costs, rates or volumes. No market or benchmark values are assumed for you.
Method
An explicit component model: each component is named and entered by the user, extended over the months covered, with one-off costs added once. Components left at zero are excluded and reported as excluded.
Assumptions built into the result
- Mathematical: Every price is the one the user entered, in the currency they chose; no exchange rate is applied.
- Mathematical: Usage and prices cover the same period.
- Mathematical: Recurring components are treated as level across the period.
Figures this calculator will never guess for you
- No provider price, instance rate, storage rate or transfer rate is built in.
- No typical discount, saving or industry average is suggested.
- No staffing, support or licence cost is inserted on the user's behalf.
Limitations
- The result is only as current as the prices entered; a price taken months ago is not a current vendor price.
- Arithmetic over the figures entered — it cannot tell whether the usage or the rate card behind them is right.
- Level monthly costs; growth, inflation and discounting are not modelled.
- Not a discounted cash flow — no present value is taken.
Source and version
- Standard or reference
- FinOps Framework — workload optimisation — FinOps Foundation (FinOps Framework capability: workload optimisation — cloud resource cost is the metered quantity of a resource multiplied by the rate on the organisation's own rate card.)
- Published source
- The Linux Foundation — FinOps Framework
- Formula version
- Version 1
- Verification
- Reviewed against the cited source on
- How much weight the source carries
- Standards or government
- Applies to
- Currency
- Amounts stay in the currency you choose; no exchange rate is applied.
Related tools
Work out the hourly rate to charge a client so that target margin is met after overhead and non-billable time.
Find the true hourly cost of an employee once benefits, payroll cost and overhead are included.
Size a software application from its data and transaction functions before estimating effort or cost.
Estimate development effort, schedule and average team size for a software project of a known size.
Express cloud spend as a cost per customer, per transaction or per other business unit.
Set the rate used to apply manufacturing overhead to jobs for the coming period.