Blog
Notes on cloud cost operations.
Posts about the FinOps metrics worth caring about, what CloudQuell ships, and how teams move from reactive cost surprises to a real operating cadence.
Connect Claude, Cursor, or any AI agent to your AWS cost data over MCP
CloudQuell runs a hosted MCP server that exposes your cost data as 43 tools over OAuth. Point Claude, Claude Code, or Cursor at it and ask your AWS bill questions in plain language — no API keys to manage, no CSV exports, the same plan entitlements as the portal.
Most AWS cost anomaly alerts are noise. Alert on the ones that matter.
A single global threshold on total spend fires on every weekday-versus-weekend wiggle and teaches your team to ignore it. Per-service baselines, first-time-spend detection, and one-click scoped alert rules are how you get signal instead.
Put an owner on every AWS dollar: tag coverage, cost centers, and allocation rules
Chargeback fails when the bill does not sum to teams. The fix is a coverage metric that tells you how much is unallocated, allocation rules for shared and untagged cost, and a cost-center hierarchy that rolls up to the whole bill.
Why we don't charge a percentage of your cloud spend
A vendor billing 2–3% of your cloud bill earns more when your bill grows — the opposite of what a cost tool should be paid to do. CloudQuell charges a flat monthly fee. Here is the incentive math, and what it costs at scale.
Introducing Effective Coverage %: the FinOps metric that combines coverage and utilization
Commitment utilization on its own lies. Coverage on its own lies. The honest answer requires combining them. Here is the metric, the formula, and how to read it.