See every dollar

One cost surface for AWS and GCP

Cost and usage across clouds — trends, native forecasting, unblended or amortized metrics, daily/monthly granularity, and tax/credit exclusion by default, with explicit date ranges.

Cost lives in two consoles with different models, currencies of truth, and no shared view. Rolling AWS and GCP into one honest trend is a spreadsheet chore that’s always out of date.

What you get

Built to do the work, not just show it

AWS + GCP together

Collect cost + usage from both and read them through one consistent surface.

Native forecasting

Cost forecasts with an 80% interval, per account, from the cloud’s own forecast API.

Metric + granularity control

Switch unblended vs amortized and daily vs monthly; exclude tax/credits/refunds by default.

Explicit ranges

Pick MTD, a preset, or a calendar range — clamped correctly for timezone-ahead viewers.

How it works

From signal to result

1

Connect

Add your AWS accounts and GCP projects.

2

Collect

Per-account collectors normalize cost + usage.

3

Analyze

Read trends, forecast, and per-account breakdowns.

Why it’s different
  • Tax, credits, refunds, and bundled discounts are excluded by default (opt back in).
  • Forecasting uses the cloud’s native GetCostForecast with a confidence interval.
  • Cost is re-keyed per account so a portfolio view and per-account view both work.

Questions

Unblended or amortized?

Both — toggle the metric, and switch daily vs monthly granularity to match how you report.

Does the trend include tax and credits?

No by default, so the number reflects real usage; you can opt to include them.

Related capabilities

Ship savings, not slides

See your cloud bill drop in 30 days.