Azure GCP AWS

An agent that reads your cloud bill and writes you a report a CFO can read.

Cloud Costs, Translated for Humans. Connect Azure, GCP, or AWS in five minutes. The agent observes your spend across providers, surfaces what changed, and on the first of every month hands you a report you can forward straight to finance.

Read-only access Credentials in Azure Key Vault Cancel any time
Acme Inc. · Cloud Spend
APRIL 2026 · ISSUED 2026-04-30
r/8f2c1 · v3
Production spend rose +18.2% in April, almost entirely from one weekend scaling event.
Total · April
$12,847.32+18.2%
Forecast May
$11,920.00−7.2%
Agent · observation
vm-prod-04 scaled 8 → 32 cores at 03:14 UTC after a failed deploy and didn't scale back for 36 hours. Strip that event and the bill behaved.
Generated by hellocloudwatch Page 1 / 4
Public report · /r/8f2c1
How it works · 01

You ask in plain English.
The agent shows its work.

There is no dashboard to learn. You type the question your CFO just asked. The agent queries your Azure invoice, joins it against the deploy log, and writes back in finance English with the numbers in mono and the citations inline. You can see exactly which line items the answer rests on — and you can still call it wrong.

01 · Reasoning, visible
Every answer ships with the tool calls it ran — query scopes, join keys, line-item IDs. You can audit it in 30 seconds.
02 · Citations, inline
Numbers are pills you can click. They open to the exact invoice row or deploy event the agent leaned on.
03 · No personality
The agent has voice, not a name. It says "I read" and "I joined." It does not say "Hi, I'm here to help!"
04 · Honest about uncertainty
When a number is partial, normalized, or contested, the agent says so on the surface of the answer — not in a footnote.
Thread · mon 09:42 utc
The CFO is asking about last week's Azure spike. What do I tell her?
Reasoning · 5 steps
azure.cost.query(scope=prod, range=2026-04-19..2026-04-26)
join(deploys.log, window=±2h, on=service)
resource.timeline(vm-prod-04, range=2026-04-22)
context.lookup(name="Production Application")
summarize_for_human()
One event explains the week. vm-prod-04 in rg-prod-app scaled from 832 cores at 03:14 UTC Tue Apr 22, six minutes after the failed deploy dep-7c41a. Autoscaler did not scale back until Wed 15:40 — so the runaway ran for roughly 36 hours and added $758.40 to Production. R&D and Shared Services held to their 90-day medians within ±2%.
azure.invoice · line 1,847 deploys · dep-7c41a autoscale-events · 03:14
Variance · production · 03:14 utc apr 22
Apr 22 00:00 03:14 spike Apr 22 24:00
Can you tell her what we'll do about it?
Reasoning · 3 steps
context.read("Production Application")
history.lookup(similar_events, range=180d)
policy.suggest(scope="autoscale.vm-prod-04")
Three steps, in order of effort: cap vm-prod-04 at 16 cores (the runaway trigger does not need 32); add a circuit-breaker on checkout-worker retries; and decommission vm-rnd-12 — averaged <10% utilization all month, saves ~$340/mo. I can draft the email to the CFO if helpful.
utilization.metrics · 30d rg-rnd-pool · resource list
Draft the email to Maya …
How it works · 02

On the first of every month, a report your CFO can actually read.

One page. Headline up top, KPI strip below, a daily-spend chart, the breakdown by cloud account or business context, and the material observations the agent flagged this month. You forward the link. Your CFO reads it. The footer says, plainly, please verify important facts as the agent can make mistakes.

hellocloudwatch.com/r/8f2c1
Acme Inc. · Cloud Spend
APRIL 2026 · ISSUED 2026-04-30 09:00 UTC
REPORT ID
r/8f2c1 · v3

Production spend rose +18.2% in April, almost entirely from one weekend scaling event.

R&D and Shared Services held to their trailing 90-day medians within ±2%. The full month-over-month delta of +$1,980 traces almost entirely to one resource scaling 8 → 32 cores at 03:14 UTC on Tue Apr 22 and not scaling back for ~36 hours.

Agent · observation
Generated by agent
I read the April invoice from Azure prod (2,847 line items) and joined it with the deploy log. The headline is one event: a runaway autoscale on vm-prod-04 following a failed deploy. Strip that out and your bill behaved — every other context tracked its 90-day median.
Total · April
$12,847.32+18.2%
Forecast May
$11,920.00−7.2%
vs 90-day avg
$10,920.10+17.7%
Days closed
30 / 30final
Daily spend · April
↳ APR 22 · weekend spike
APR 01APR 08APR 15APR 22APR 30
Variance · production · 03:14 utc apr 22
vm-prod-04 in rg-prod-app (Azure prod) scaled from 832 cores, adding $758 to Production. Autoscaler trigger: 12-minute backlog spike on checkout-worker following failed deploy dep-7c41a. Did not scale back until Wed 15:40.
Generated Apr 30 · 09:00 UTC by hellocloudwatch · April 2026 closing report Please verify important facts as the agent can make mistakes.
Open the full sample report Or watch the agent build it ↑
The honest section

What it doesn't do.

You are not in the market for another "platform." Here is what we are deliberately not building — so you can decide before you connect anything.

  • 01
    No data pipeline.
    There is nothing to set up. The agent reads your cloud invoice on demand. No ingest queue, no ETL, no scheduled jobs we can break for you.
  • 02
    No dashboard.
    You won't find a chart-builder, a saved-view library, or a "metrics catalog." The home of the product is a conversation and a report. That is on purpose.
  • 03
    Read-only.
    We never modify your cloud. The agent cannot resize a VM, kill a deploy, or change an IAM policy. It writes prose; you write the change.
  • 04
    No "intelligent" anything.
    The agent has voice, not personality. It does not have a name. It does not greet you. It tells you what it did, in mono, with citations.
Setup · five minutes

How the agent gets in.

A Service Principal with the read-only Cost Management role. That is the entire scope. We never see resource configuration. We cannot see secrets. We cannot make changes. Credentials live in Azure Key Vault — never in our database.

STEP 01
2 min
Create the Service Principal
In the Azure portal, register a new app and generate a client secret. We give you the exact CLI snippet if you prefer terminal.
az ad sp create-for-rbac --name hcw-reader
STEP 02
2 min
Grant read-only Cost Management
Assign the built-in Cost Management Reader role at the subscription scope. Nothing else. We refuse Contributor and Owner roles.
role: Cost Management Reader
scope: /subscriptions/8f2c…
STEP 03
1 min
Paste tenant + client ID
Drop the values into the connection form. We store the secret in Azure Key Vault under your tenant's HSM. You can rotate or revoke at any time.
tenant_id: 4a812d09-…
client_id: 8f2c1a3b-…
vault: azure.keyvault.hsm
Encryption
At rest in Azure Key Vault HSM; in transit via TLS 1.3.
Audit log
Every agent action is logged with the exact tool call and arguments.
Cancellation
One click. Your data and credentials are purged within 24 hours.
Pricing

Two plans. Cancel any time. No card to start.

Starter is for one product, one cloud subscription, one CFO who wants one report a month. Pro is for a small platform team running a few subscriptions — across Azure, GCP, AWS, or any mix — who want chat without rate limits. That is the whole shelf.

Starter
$49 / month

One product. One Azure subscription. One monthly report.

  • Up to 3 connected Azure subscriptions
  • Daily + weekly agent observations
  • Monthly report with shareable link
  • Unlimited read-only viewers
  • 5 editor seats
  • Standard cost ceiling
Pro
$149 / month

A small platform team. Up to ten subscriptions. Chat without rate limits.

  • Up to 10 connected Azure subscriptions
  • Daily + weekly agent observations
  • Higher cost ceiling for deeper agent analysis
  • Monthly report with draft review + inline business-context correction
  • Unlimited read-only viewers
  • 25 editor seats
14-day trial, no credit card. Connect Azure, GCP, or AWS and ask one question. If the answer is not useful, walk away — no follow-up email.
Start the trial

Annual billing knocks two months off either plan. No usage tiers. No "Contact us" plan.

FAQ

The questions a skeptical CTO actually asks.

No softballs. If you have a different one, write to us — a person reads every note.

For the questions it answers, yes — because every answer cites the line items it leaned on, and you can audit those in a click. We hand you a report at the end of each month that reconciles to your cloud invoice to the cent. If it does not, that is a bug and we treat it as one.

For the questions it cannot answer (forecasting next quarter; comparing vendors we have not connected to), the agent says so. It does not hallucinate a number to be helpful.

The bill is already on its way.

Connect your cloud now and the first observation lands in your inbox by Friday. No card, no demo call, no email follow-up if you walk away.