The month-end AWS number, before the month ends.
Where spend will land, what moved it and what nobody owns, stated in money across every account in the organization.
What it answers
The questions that come to you, and where each answer lives.
- Will this month land higher than last?
Pace sets this month's complete days against the same number of days last month, and the forecast projects the month end from the rate those days actually ran at.
Costs
- Has anything actually got more expensive?
Run rate sets what one day costs now against what one day cost last month, so a longer month cannot pass for a price rise.
Costs
- Who is this spend charged to?
Every taggable resource is scored against the tags you declared, and the spend no owner can be charged for is priced, account by account.
Cost Attribution
- Which commitments need a decision?
Every Savings Plan and Reserved Instance term still running, soonest first, with the monthly spend that returns to on-demand rates when it ends.
Costs · Commitments
- Can I read it in our own currency?
Amounts render in the currency you choose at the ECB daily reference rate, and the rate and its date sit beside them. What AWS billed stays in US dollars underneath.
Every page
Where it starts
The pages you will open first.
Costs
Run rate, pace against the window before it, and the services and accounts carrying the movement.
64%of this month's rise is one account
Cost Explorer
Cost Attribution
You declare the tags that count. Every taggable resource is scored against them, and what is left unowned is priced.
68%of taggable resources have an owner
Config · Cost Explorer
AI Spend
Bedrock on the bill and Claude bought direct from Anthropic, summed across all four token types.
$21,904over 30 days, both channels
Two billing channels
Deployed into your AWS account, and read-only.
- Read-only
- Your AWS account, your Region
- Encrypted at rest in your account
- Revocable in one action
To lower the compute line itself, with no commitment to buy, see Cloud Saver.
Also in Solutions
Point it at your organization and see the first answer the same afternoon.
30 minutes of one engineer · your AWS data stays in your account