Know about Cloud Bill Doctor AI Intelligence™
Everything you need to know before you start: what it does, who it is for, how to get your cost export from Azure, AWS or Google Cloud, and what you get.
What it does
Cloud Bill Doctor AI Intelligence reads your Azure, AWS or Google Cloud cost export and tells you where the money is wasted and what each fix saves a month. It shows the bill and its month-end forecast, why it changed, cost spikes and growing services, and diagnoses the waste: orphaned disks, unused public IPs, old snapshots, dev / test servers running 24×7, servers that should be on a commitment discount, and untagged spend.
The problem it solves: cloud bills have thousands of lines and grow quietly. A server is deleted but its disks stay. A test server runs all weekend. Last year's snapshots are still billed. A pipeline runs away for two days. Each line is small; together they are often 20–30% of the bill — and the cloud console does not add them up for you.
Who it is for
| Who | What they load | What they get |
|---|---|---|
| CTO / IT head | The monthly cost export | Saving found, the forecast, why the bill changed — in one page |
| DevOps / cloud engineer | Daily or hourly export | The exact disks, IPs, snapshots and servers to fix, with resource IDs |
| FinOps / finance | Exports for every subscription or account | Spend by service, account, group and region; untagged spend; spikes |
| Managed-service provider | Clients' exports | A cost review for each client, with an Excel workbook and a Word diagnosis |
| Startup founder | The bill from the console | "Where is my cloud money going?" answered in plain words |
How to get your cost export
lineItem/…) and CUR 2.0 (line_item_…) columns both work.Tips: 30–45 days gives the best diagnosis (snapshots, spikes and growth need 28+ days). Hourly or daily exports both work. Large export? Up to 100 MB per file — or export a shorter period. Have last month in a separate file? Add it with ➕ Add last month's export. FOCUS-format exports are read too.
What you get
Downloads: a Cloud Bill Workbook (Excel) with every item and resource ID, spend tables, spikes, growth and untagged spend — and a one-page Bill Diagnosis (Word) for management.
How each check works — and its limits
| Check | Azure | AWS | Google Cloud |
|---|---|---|---|
| Orphaned disk | No server in its resource group, or its name matches no server there | No server in its account + region (the AWS bill does not link a volume to its server — check "Available" volumes in EC2) | No server in its project, or its name matches no server there |
| Unused public IP | No server or load balancer in its resource group | Billed as "IdleAddress" | Billed as "Static Ip Charge" |
| Old snapshot | Billed every day for 30+ days — check it against your backup policy | ||
| Dev / test 24×7 | Server tagged or named dev / test / qa / uat / staging, running round the clock including weekends. A schedule (8 am – 8 pm, weekdays) saves about 64%. | ||
| Commitment discount | Reserved instance / savings plan, ~35% | Reserved Instance / Savings Plan, ~35% | Committed use discount, ~25% (sustained-use discounts already apply) |
⚠️ Savings are estimates from the bill alone. Always check a disk, IP or snapshot before deleting it, and check commitment prices in your cloud's pricing calculator before buying.
How it works — in 5 steps
Your data stays with you
🔒 Your bill is read and diagnosed inside your browser. It is never uploaded to QuantumData servers. Cloud links go directly from your browser to your own storage — QuantumData never sees the link or the bill. Only sign-in, your licence and payment use our secure service.
🤖 The AI that learns also runs inside your browser; your "intended" answers and your "what changed" history are kept on your browser only.
✨ Ask AI is optional. Before anything is sent you see the exact summary — service names, monthly totals, counts and savings — and tick "I agree". Resource names and IDs, subscription / account / project names and tags are never sent, and nothing is stored.