HLDModulesFinOps
FinOps
Cloud cost tracking, forecasting, budgeting, and recommendations.
FinOps
The FinOps module provides cloud cost visibility, optimization, budgeting, and forecasting across connected enterprise accounts. Cost data is collected daily at per-resource granularity, reconciled monthly after provider billing finalization, and exposed through account-level and organization-level dashboards.
Canonical provider, resource type, category, and FinOps tool terminology is tracked in the Provider and Resource Reference.
Provider Support
Supported
AWS
Azure
Unsupported
GCP
Docker Hub
GitHub
Ubuntu- Docker
What It Does
| Capability | Detail |
|---|---|
| Cost | Ingests daily AWS and Azure cost records, normalizes them per resource, and reconciles finalized billing data monthly. |
| Forecast | Generates 12-month cost forecasts per account, region, and resource type. |
| Budget | Defines MCM-managed budget policies, evaluates actual and forecast spend, and tracks alert posture. |
| Recommendations | Captures provider-sourced right sizing, Savings Plan, and Reserved Instance opportunities. |
Use Cases
| Use Case | Outcome |
|---|---|
| Daily cost visibility | Teams can review yesterday's AWS and Azure spend by resource, region, category, and cost type. |
| Monthly billing reconciliation | Finalized provider billing data replaces provisional daily records after provider data closes. |
| Forecast planning | FinOps teams can inspect projected spend for the next 12 months. |
| Budget governance | Teams can set spend caps, thresholds, and scopes for providers, accounts, and tags. |
| Savings execution | Teams can prioritize provider recommendations by savings, effort, status, and term. |
Data Pipeline
Job Schedule
| Job | Schedule | Scope | Stored Result |
|---|---|---|---|
| Daily Cost Job | Daily | Previous day's AWS and Azure cost records | Cost records with reconciled=false. |
| Monthly Cost Job | 9th of each month | Full previous month | Cost records updated with finalized billing and reconciled=true. |
| Forecast Job | Last day of each month | Next 12 months per account, region, and resource type | Forecast rows replace the previous monthly forecast set. |
| Recommendation Job | Provider-driven schedule | AWS and Azure optimization APIs | Recommendation rows with savings, effort, term, and workflow status. |
| Budget Job | After cost and forecast updates | Active budget scopes | Budget actuals, forecast posture, threshold state, and alert status. |
Execution History
Execution history records are used to audit FinOps jobs and show operational health in the UI.
| Field | Description |
|---|---|
| Job Type | Daily Cost Job, Monthly Cost Job, Forecast Job, Recommendation Job, or Budget Job. |
| Execution Time | Time when the job started. |
| Duration | Runtime for the job. |
| Trigger Type | Scheduled or manually triggered execution. |
| Triggered By | User or system actor that started the job. |
| Status | Success, Failed, or Partial |
| Error | Failure message or partial-completion note when applicable. |
Related Pages
| Page | Description |
|---|---|
| Cost | AWS CUR and Azure Cost Details ingestion, normalization, reconciliation, and stored cost fields. |
| Forecast | AWS and Azure forecast collection, schedule, API mapping, and stored forecast fields. |
| Budget | MCM-managed budget configuration, evaluation, alerting, and stored budget fields. |
| Recommendations | Provider API sourcing, recommendation types, workflow statuses, and stored recommendation fields. |
| Provider and Resource Reference | Canonical provider, resource type, module, and tool terminology. |