Product
What CloudMonitor is, what it does, and how it works.
What runs in our tenancy, and what runs in yours?
By default we deploy CloudMonitor into a Fabric workspace on capacity you own, in your own Microsoft Fabric tenant. CloudMonitor-hosted stays available if you would rather we ran that capacity.
Azure Cost Management writes your raw FOCUS export to a storage account you own, and it stays there. CloudMonitor reads it through a OneLake shortcut and does the ingest, cleansing and modeling in our own Fabric tenancy, in the Azure and Microsoft Fabric region you choose during onboarding. That much is the same in both arrangements. Where the finished data comes to rest is what your choice settles: in your own Fabric tenant we write the modeled cost tables into a lakehouse in your workspace, on your capacity, and deploy the semantic model and the CloudMonitor app there on top of them. Under CloudMonitor-hosted, those stay in the workspace we run for you inside our tenancy.
Your license price is set by your annual Azure Consumption Revenue. In your own Fabric tenant, the capacity your reports, semantic model and CloudMonitor app run on sits on your own Fabric bill. Under CloudMonitor-hosted we run that capacity for you. CloudMonitor's ingest, cleansing and modeling run on Fabric capacity in our own tenancy in both arrangements.
Architecture and data flow sets out where each layer runs in both arrangements.
Azure Cost Management writes your raw FOCUS export to a storage account you own, and it stays there. CloudMonitor reads it through a OneLake shortcut and does the ingest, cleansing and modeling in our own Fabric tenancy, in the Azure and Microsoft Fabric region you choose during onboarding. That much is the same in both arrangements. Where the finished data comes to rest is what your choice settles: in your own Fabric tenant we write the modeled cost tables into a lakehouse in your workspace, on your capacity, and deploy the semantic model and the CloudMonitor app there on top of them. Under CloudMonitor-hosted, those stay in the workspace we run for you inside our tenancy.
Your license price is set by your annual Azure Consumption Revenue. In your own Fabric tenant, the capacity your reports, semantic model and CloudMonitor app run on sits on your own Fabric bill. Under CloudMonitor-hosted we run that capacity for you. CloudMonitor's ingest, cleansing and modeling run on Fabric capacity in our own tenancy in both arrangements.
Architecture and data flow sets out where each layer runs in both arrangements.
What does CloudMonitor do?
CloudMonitor is an Azure-native FinOps platform. It reads your Azure billing via FOCUS, pre-builds the reports your finance and engineering teams need in a Microsoft Fabric app, and runs an optimization engine that surfaces savings recommendations.
Which Clouds and SaaS products does CloudMonitor support?
For hyperscaler billing, CloudMonitor supports Microsoft Azure and AWS. It also tracks AI and SaaS tools your teams already run: Microsoft 365 when the optional module is enabled, OpenAI, Anthropic Claude, and GitHub Copilot. Google Cloud and Cursor are planned, not connected sources today.
How do you measure whether our AI spend is worth it?
CloudMonitor cannot prove AI ROI from cost data alone. It measures Azure cost and live GitHub Copilot usage; other provider views use examples until their APIs connect. ROI also needs a business outcome, the financial benefit linked to AI, total investment cost, and a credible baseline. Unit Economics can track the cost per business measure; ROI still needs attributable benefit data from the business. See FinOps for AI and ROI.
What does agentic FinOps mean in practice?
Each agent is scoped to a cost group and a governance policy. The output is always a recommendation, ticket, or runbook — your team or your existing automation makes the change. CloudMonitor itself is read-only.
What can we rebrand for customers?
Reseller mode replaces the CloudMonitor workspace logo with the partner's logo. A small Powered by CloudMonitor mark remains. Screen names, menus, documentation, and support links also keep the CloudMonitor name, so this is a branded workspace rather than a completely unbranded product. See what branding changes before presenting it to a customer.
How does the savings calculator work out its estimate?
The estimate combines core Azure spend, AI usage, and Fabric capacity. Core Azure spend uses CloudMonitor's published savings baseline, from 10% at $60K annual spend to 20% at $3M, then adjusts for your optimization stage, estate complexity, and infrastructure mix. The AI section models model right-sizing, Batch API routing, and existing provisioned-throughput right-sizing. The Fabric section uses current Azure prices for SKU right-sizing, one-year reservations, and explicit pause schedules for a separate non-production capacity. Every rate appears in the methodology section with its source and last-verified date. The result is always a range.
Do I have to enter my details to see a savings number?
No. The headline savings range, the pillar breakdown, and the license comparison are free to use with no form. Your work email and company name unlock the full report: the lever-by-lever breakdown with the formula behind each number, an audit of every assumption you kept or changed, and a PDF you can share internally.
How accurate is the savings estimate?
It is an estimate built from your inputs and published rates, not from your billing data. Treat it as a range, not a promise. Mature FinOps teams see smaller numbers by design because less optimization headroom remains. Connect CloudMonitor to measure spend and opportunities from your billing data. Eligibility, workload requirements, and the actions your team approves still determine realized savings.
Does the estimate cover AI and Microsoft Fabric costs?
Yes. The AI section models Azure OpenAI token spend through model mix, Batch API routing, and existing provisioned-throughput right-sizing. Prompt-caching dollars are excluded until a model version and current cache-read and cache-write rates are selected. The Fabric section models SKU right-sizing, reservations, and pause schedules for a separate pay-as-you-go non-production capacity. AI harness costs and OneLake storage are also excluded and listed beside the methodology.