Cloud Repatriation Economics Engine
rack2cloud — Cloud Cost Governance
Architectural Economics
Cloud Cost Governance Toolkit

Cloud Repatriation
Economics Engine

Evaluate whether a workload should still live in cloud — across economics, elasticity efficiency, operational separation, and infrastructure persistence.

✓ Input-driven. No telemetry required.
✓ Operationally neutral. Cloud-favorable is a valid output.
✓ Runs entirely in your browser.
Pillar 01
Economic Viability
Pillar 02
Elasticity Efficiency
Pillar 03
Operational Separation
Pillar 04
Infrastructure Persistence
01 Cloud Spend Baseline
▶
Combined compute, storage, egress
8%
Expected annual escalation including commitment increases
02 On-Premises Capital Estimate
▶
Full stack — servers, storage, networking
Labor, tooling, cutover — one-time, non-recurring
2.5 Workload Persistence Profile
▶
03 Stranded Capacity Risk
▶
65%
Steady-state utilization of repatriated infrastructure
How reliable is the workload utilization forecast
04 Ongoing Operational Costs
▶
Power, colo / DC space, maintenance contracts, FTE delta
Estimated egress that exits with workload. Run CCA first →
Retained SaaS, DR, burst — defaults to 0
05 Cloud Dependency Residue
▶
Drives Cloud Dependency Residue level and Economic Separation Achievability
06 Timing & Lock-In
▶
Platform coupling, stateful dependencies, cutover window tolerance

Architecture Review

The engine surfaces the signal. A structured review maps it to your renewal window, workload profile, and governance posture — and identifies the sequence of actions that close the separation gap.

Work With The Architect →