Database TCO monthly.

Database hosting costs stack across three components: storage (0.08-0.12/GB/month for SSD), IOPS capacity (0.05-0.15 per 1,000 IOPS for 30 days), and compute instance cost (server ram + CPU). Managed databases (RDS, Cloud SQL, Aurora) add 20-40% premium over raw VM + database for convenience and automation.

500GB storage × 0.115 = 57.50. 3,000 IOPS × 0.05 per 1,000 × 2.6M seconds/month = 390. 250 compute instance. Total 697/month, 8,364 annually. For most apps, compute is the biggest line item. High-IOPS workloads (real-time apps, gaming) can see IOPS dominate.

Cost-cutting levers: reserved instances (save 30-60%), right-size instances (don't over-provision), use tiered storage (hot/warm/cold), enable compression (saves 50-70% storage for text-heavy data). Most databases are over-provisioned by 30-50% when first launched; review quarterly to catch overspend.

Quick example

With storage of 500 and storage cost per gb of 0.12 (plus iops per second of 3,000 and iops cost per 1,000/sec/mo of 0.05), the result is 312.00. Change any figure and watch the output shift — it's often more useful to see the pattern than to memorise the formula.

Which inputs matter most

You enter Storage (GB), Storage Cost per GB (£/mo), IOPS per Second, IOPS Cost per 1,000/sec/mo (£), and Compute RAM (GB). Frequency and unit price pull the total in different directions. The biggest surprise for most people is how small recurring amounts compound into large annual figures — that's where this calculation earns its keep.

What's happening under the hood

Total = (storage × rate) + (IOPS/1000 × rate × seconds in month) + compute cost. The formula is listed in full below. If the number looks off, you can retrace the calculation by hand — that's the point of showing the working.

What to do with a low result

A disappointing result is information, not a judgement. Pick the single input that dragged the figure down most and focus the next quarter on that one factor. Breadth-first improvement rarely works; depth-first on the worst input usually does.

What this doesn't capture

The score is a composite of the inputs you provide. Life context — job security, family obligations, health, housing — doesn't appear in the math but shapes the real picture. Use the number as a prompt, not a verdict.