FinOps Domain
Understand cloud usage and cost.
Comprehend and allocate cost and usage across the organization before you act on it. This Domain is the foundation that every other Capability builds on — and where CloudMonitor lights up day one.
The first FinOps Domain answers a simple question: what is the organization spending on cloud, and who is responsible for it. Get this layer right and every later optimization compounds; get it wrong and forecasts wander, chargeback fights drag on, and engineers stop trusting the numbers. This is the FinOps principle that data should be accessible, timely, and accurate — made concrete.
The four Capabilities under this Domain — Data Ingestion, Allocation, Reporting and Analytics, and Anomaly Management — are named verbatim from the FinOps Framework. CloudMonitor implements each one as a shipped feature, not a configuration project.
Shared resources like networking and monitoring are split across consuming cost groups as part of the Allocation Capability.
Capabilities in this Domain
Four shipping Capabilities, day one.
Data Ingestion
FOCUS 1.2 export pulled daily, backfilled to install, validated on every refresh. No manual exports, no broken pipelines.
Allocation
Cost groups, virtual tags, and shared-cost splits route every dollar into the owner's view — without renaming a single Azure resource.
Reporting and Analytics
30+ pre-built reports, each tunable per audience: finance gets accruals, engineering gets unit cost, executives get the trend.
Anomaly Management
Daily detection at the resource level, with alerts routed to Teams, Slack (via webhooks), or any ITSM you already run.
Beyond the four Capabilities
AI tooling spend, in the same domain.
Developer AI tools bill outside your Azure invoice. CloudMonitor brings their token spend into the same Understand-domain view.
AI Token Usage Tracking
GitHub Copilot, OpenAI, Anthropic Claude, and Cursor — token spend, model mix, cache hit rate, and cost per developer in one view.
The foundation, in the product
What 'understand your cost' looks like on screen.
Allocation, reporting, and anomaly detection are shipped features here — not a configuration project you start after onboarding.
Reporting and analytics
The whole bill, on one dashboard.
Total spend, trend, and the biggest movers in a single view — the read every finance and engineering conversation starts from, instead of a raw export.
Allocation
Every dollar routed to an owner.
Cost groups and virtual tags map spend to the teams and projects responsible — without renaming a single Azure resource — so chargeback stops being an argument.
Anomaly management
Spikes flagged the day they appear.
Daily resource-level detection surfaces unexpected jumps and routes them to the team. CloudMonitor raises the flag; the owner decides what to do about it.
AI tooling spend
Token spend, in the same view.
GitHub Copilot, OpenAI, Claude, and Cursor spend land in the same Understand-domain view as the rest of the estate — broken down by model and token type.
Ask Finn
Turn cost and usage data into the next question.
Ask Finn explains changes, anomalies, and allocation gaps from the governed data already behind CloudMonitor reports.
For July amortized cost, what changed in Platform Engineering, which services drove it, and where is spend still unallocated?
Add the period, cost group, and selected cost basis.
Source: this page interprets the Understand Usage and Cost domain published by the FinOps Foundation, licensed under CC BY 4.0. The wording, examples, and product mapping on this page are CloudMonitor’s own.
Explore the full FinOps platform.
See how CloudMonitor implements all four FinOps Foundation Domains end-to-end.
