Dashboard

Wring keeps a complete, normalized history of your AWS costs and refreshes it automatically every day — no exports, no spreadsheets, no waiting for the end of the month.

What you see

• Spend over time — daily granularity, across all connected accounts, so a jump on Tuesday is visible on Wednesday, not on the next invoice
• Per service — which AWS services drive your bill, and how that mix shifts over time
• Per account — every linked account individually and consolidated, so team- or project-level accounts stay comparable
• Credits and refunds — shown separately from real usage, so the numbers you compare month over month aren't distorted by one-off credits
• Any time period — pick a preset such as Last Month or Year to Date, or choose a custom range of up to 366 days, and switch the chart between daily, weekly and monthly bars. The totals stay the same whichever breakdown you pick.

How the sync works

Once an account is active, Wring reads its cost and usage data from the AWS Cost Explorer API every day and stores a normalized history:

1. Daily sync — each day, the most recent days are fetched again. AWS finalizes usage with a delay of up to a few days, so re-fetching corrects late-arriving usage automatically.
2. History backfill — right after connecting, historical data fills in progressively so your dashboard has context from day one.
3. Everything downstream uses the same data — savings, what Ask Werner answers, and your invoice are all computed from this one synced history. Dashboard and invoice can't drift apart, because they share a source.

Where the numbers come from

All figures are based on your account's own AWS cost and usage data, read via the read-only role you granted during onboarding. Wring never estimates your base spend — it reads what AWS reports. If your AWS console and Wring briefly disagree, it's timing: AWS itself revises recent days, and the daily sync catches up automatically.

Good to know

• Cost insights work with read-only access alone — you don't need to move your billing to use them.
• New accounts added later join the same dashboard automatically once their stack is active.