How CoreFinOps Works

Understand the workload-first migration-to-value operating model.

CoreFinOps starts with an application → workload → resource hierarchy. AWS account and service dimensions remain available, but the financial decision is tied to business ownership and workload lifecycle.

Stage 1 — Establish the estate

Import application, workload, asset and source-cost records. Connect supported AWS accounts using a customer-controlled read-only role. Resource discovery gives current AWS context; cost exports give billing evidence. Importing a legacy estate and connecting AWS are separate operations.

Stage 2 — Establish financial truth

CUR 2.0 / AWS Data Export facts are normalized with explicit currencies and cost measures. Allocation rules map defensible resource costs to business context. Missing ownership remains UNALLOCATED, not force-distributed.

Stage 3 — Make migration decisions

Assess strategy, record blockers, calculate target and transition economics, and assign workloads to waves. Maintain the original system recommendation even when an authorized user overrides it. Economics is a reproducible decision model, not a guarantee of future bills.

Stage 4 — Control the transition

Dual-run measures overlap while source and target are active. Cutover records the technical transition; decommission independently establishes whether source infrastructure and its recurring financial obligations were removed. Remaining obligations can generate stranded-cost findings.

Important

Cutover is not financial decommission. A workload can be technically migrated while a data-center lease, legacy license, reserved capacity or support contract continues billing.

Stage 5 — Optimize and prove outcomes

Read-only AWS recommendations and internal findings become actionable opportunities. An owner can propose an action, obtain approval, confirm externally performed work and submit evidence. The Value Ledger separates estimated, attested and measured outcomes according to available evidence.

What CoreFinOps never assumes

The platform does not infer historical tags from today's labels, combine currencies without an approved FX model, claim a recommendation was automatically implemented, or replace actual bills with a forecast.

Security

The V1 customer IAM role is read-only. CoreFinOps never stops, deletes or modifies AWS infrastructure, purchases commitments, or performs any write operation in your AWS account.

Legacy estate → Assessment → Readiness → Economics → Waves
             → Dual run → Cutover → Financial decommission
             → AWS optimization → Approved action → Verified value

Five stages from legacy estate import through verified value outcomes.