Your cloud bill, explained.

For the questions it answers, yes: every answer lists the sources it used, and each observation it cites opens that month on your Spend page. The monthly report is built to match your vendor's own bill, wherever that vendor bills a figure we can read. Where it differs, that is a bug and we treat it as one.

For what it cannot answer, like what next quarter will cost or a vendor you have not connected, it says so rather than hallucinating a number to be helpful.

The vendor's, wherever the vendor bills a figure we can read; that is what the monthly report reconciles to. Where a vendor publishes metered usage and no money, the figure is ours: their units against their published price list. That is an estimate, not a bill, and the agent says which one you are looking at.

We would rather say so than imply a precision we do not have.

The citation pills mean you can usually catch it inside thirty seconds: the agent's claim sits next to the sources it read. And every public report ends by asking readers to verify important facts, so a CFO reading the forwarded link is not being told the number is gospel.

If a number was materially wrong, email us. We read it.

In Azure Key Vault, whichever vendor you connect; we hold a reference, not the secret itself. We ask for the narrowest credential each vendor issues, and for almost all of them that is scoped read-only to billing: no resource visibility, no ability to modify anything. Where a vendor issues nothing narrower than an organisation-wide key, the connect form says so before you create one, and we call exactly one endpoint with it.

Rotating or revoking takes one click and one minute. We never email you to ask for a secret. We never paste a secret into chat.

Yes, from the account page. Your credentials are purged immediately; the rest of your data follows the staged-deletion schedule in our privacy notice. There is no retention clause to wait out, and nobody asks whether you are sure.

Because your CFO does not ask "what is my month-over-month variance by service?" They ask "why did production cost more last week?" A dashboard pushes the work of answering onto you; the agent answers directly. The report is the artifact that survives the conversation, but the conversation is the product.

We considered one, then watched ourselves never open it for three months. So we cut it.

SaaS teams of around thirty people, where a CTO or engineering lead owns the cloud bill and finance wants it explained. The founder was that CTO, and spent about four hours a month writing the cost story for finance by hand. Most teams like this pay for no cost tool at all, because every option is sized for a FinOps team they do not have.

If you run a large FinOps practice or want deep cost tooling, an enterprise platform will suit you better, and our comparison page says which.

The reasoning step uses a foundation model, yes, with no access to the public internet, your other documents, or any data outside the cloud cost surface you connect. Every tool call is logged and shown in the answer. If a model swap improves accuracy we will do it; if it changes the voice we will not.

A monthly report for the month that just closed: the numbers are written in the first days of the month and the agent's narrative follows by the fifth to seventh. In between, the agent reads your spend every morning and re-reads the last five days each evening as figures settle, and emails you when a settled day breaks its own 28-day pattern, never on a provisional number.

Yes. Map resources to the parts of your business they run, "Production SaaS" rather than a resource-group id, and set a monthly budget per business context. Crossings notify you at fifty and eighty percent; at ninety-five, finance is emailed too.