CoreFinOps Docs
On this page

CoreFinOps Documentation

Migration economics and continuous AWS optimization, grounded in financial evidence.

CoreFinOps is the financial control plane for AWS migration and post-migration value realization. It connects what an application costs before migration, what it costs while both estates operate, what must be retired, and what value was actually achieved.

Get startedExplore Migration Economics

The five questions CoreFinOps helps you answer

  • What do we own and what does it cost? Build an application/workload portfolio from legacy records, AWS inventory and authoritative cost data.
  • What should move and when? Assess candidate strategies, readiness, target run rates, transition costs and waves.
  • What is the migration really costing? Monitor planned and actual dual-run, cutover dates and surviving source commitments.
  • What should be optimized next? Review AWS-native recommendations, cost change findings and prioritized opportunities.
  • What value has actually been proven? Carry an action from approval through customer implementation, evidence and verified outcomes.

The financial lifecycle

Legacy estate → Assessment → Readiness → Economics → Waves
             → Dual run → Cutover → Financial decommission
             → AWS optimization → Approved action → Verified value
CoreFinOps traces the full financial journey from legacy estate to verified value.

Security

CoreFinOps is not an autonomous cloud remediation product. It reads supported AWS cost/configuration evidence and helps users make and govern decisions. Actions on customer AWS resources remain customer-controlled.

Explore the documentation

Getting Started

Establish your workspace, connect read-only AWS access, configure cost exports and import legacy costs.

Get started

Spend Intelligence

Understand cost measures, allocation, unallocated spend, Explorer and data freshness.

Explore Spend Intelligence

Migration Management

Build a defensible business case, sequence waves and remove stranded legacy cost.

Explore Migration

Optimization & Outcomes

Evaluate opportunities, assign actions and verify value with evidence.

Explore Optimization

Governance & Reporting

Preserve accountability through budgets, policies, exports and audit.

Explore Governance

Reference & Trust

Roles, security model, financial semantics and AWS coverage explained.

Explore Reference

A note about financial trust

An estimated savings opportunity is not realized savings. A technical cutover is not financial decommission. A report generated today does not mean its AWS billing evidence was collected today. Where evidence is missing, CoreFinOps should say so rather than display fabricated numbers.

Important

Estimated opportunities, approved actions, customer-attested implementation and independently measured billing change are different states. Do not add them into one generic “savings” headline.

Start here

  1. 1

    How CoreFinOps Works

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

  2. 2

    Connect an AWS Account

    Set up the customer-controlled read-only cross-account role.

  3. 3

    Configure AWS Cost Exports

    Configure CUR 2.0 / Data Export so billing facts are available.

  4. 4

    Import a Legacy Estate

    Bring application, workload and source cost records into the portfolio.

  5. 5

    Interpret Your First Dashboard

    Read Overview and Value Ledger without confusing missing data with zero.