CloudTcoEstimator
Multi-CSP Total Cost of Ownership estimator. Compares AWS, Azure, GCP
What it does
Where the in-app TCO Calculator (tcoHandlers.ts) models M365 migration cost, this module models cloud-target cost across the three major CSPs so customers can pick the cheapest landing zone before they commit. This is the gap Cloudamize fills today. ENRICHED: Pure testable functions for SKU selection and cost mapping. Multi-strategy collection with graceful fallback - both paths emit same columns. Logic: 1. Read WorkloadUtilization.csv (preferred) or ComputerInventory.csv to enumerate hosts with cores + RAM. 2. For each host, pick the smallest matching general-purpose SKU on each CSP (AWS m6i, Azure D_v5, GCP n2-standard) using a configurable headroom factor (default 1.20 on cores + RAM). 3. Multiply USD/hr * 730h to get monthly compute cost per CSP per pricing tier (on-demand, 1-yr RI/CUD, 3-yr RI/CUD). 4. Add storage cost using observed/assumed disk GB * CSP $/GB-month (AWS gp3, Azure Premium SSD P-tier blended, GCP pd-balanced). 5. Add egress allowance (configurable GB/host/month, blended $/GB). 6. Roll up to portfolio totals and project across 1/3/5 years with annual price drift assumption (default 0%). Output: CloudTcoEstimator_PerHost.csv per-host x per-CSP cost rows CloudTcoEstimator_Summary.csv CSP totals + winner + savings
How the app exposes it
The module runs through the ACQI discovery orchestrator and writes its rows into a dedicated results view. From there, conflicts, dependencies, and readiness scores feed the deal-wide consolidation layer.
/discovered/cloud-tco-estimator Outputs
Each module emits a normalised CSV keyed by entity ID with readiness and risk scores, evidence-source counts, and last-seen timestamps. The exact column set varies by module — the app's results view shows the live schema.