Know why your AWS bill changed. And which PR caused it.

A weekly digest showing what changed in your AWS bill, the deploy or resource change it lines up with, the evidence, and the fix.

Reserve the founding price See how it works →

We're building this now. Reserving is free — no card, no charge.

aws-costs
CB
CostBlame APP Mon 9:02 AM

AWS spend +$1,180 (+19%) vs last week. One change explains most of it:

CloudWatch Logs ingestion — /ecs/orders-api +$940
Ingestion~4× higher since Tue 14:20
Driven byorders-api deploy, 6 min earlier
Confidence: high — no other deploys to this service in the window.
Likely cause: debug logging enabled in a3f9c1 (PR #412).
View diff on GitHub Fix: LOG_LEVEL=info + retention policy (~$900/mo saved)
NAT Gateway egress — eu-west-1 +$240
Statusunattributed
No matching resource or deploy event — we don't guess.
Sound familiar?

Right now, nobody finds out until the invoice lands.

01

The bill jumps overnight

A $400 spike shows up three weeks later, buried in a line item nobody's watching.

02

Cost Explorer shows the "what," not the "why"

It can tell you NAT Gateway traffic doubled. It can't tell you which deploy did it.

03

Someone loses half a day

Cross-referencing CloudTrail with git log to find the commit behind the spend.

How it works

Two read-only connections. One correlated answer.

1Spot the jump
AWS billing
Per-resource, read-only role
GitHub deploys
Commit timestamps only
CloudTrail
Resource-level change events
2Match the cause
Diff & correlate
The cost spike lines up with a CloudTrail event and a deploy.
cost commits Mon → Sun
3Show the evidence
Weekly Slack digest
Confidence, evidence, and the fix

"Don't we already have Cost Explorer? Or a Copilot plugin for this?"

Hover or tap a tool to see what it misses.

Write code Merge Live traffic Bill
Code copilot
reads the code
Reviews your code before you merge.Misses: real traffic and the actual bill.
Cost Explorer / Q
when asked
Shows your bill when you go and look.Misses: it won't alert you or name the commit.
Watches your bill every night.Names the PR behind any jump, in Slack.
CostBlame
traces the bill back to the PR

Surprise costs start when real traffic hits. Neither tool watches that stretch for you.

We don't guess

Every alert shows its evidence and a confidence level.

If there's no clear link between a cost change and a deploy or resource event, we list it as unattributed instead of guessing.

Coming later: NAT/egress attribution, cross-AZ costs, commitment expiry tracking.

Read-only by design

We don't need write access to tell you this.

✓

Read-only IAM role, nothing more. We can't launch, modify, or delete a single resource in your account.

✓

The setup template is public, so you can read every permission before you deploy it.

✓

Your billing export stays in your own S3 bucket. We read it; we don't keep a copy.

✓

Disconnect any time by deleting the role. We delete what we've stored.

Simple pricing

Pay for the "why," not for a seat.

Pays for itself if it catches one $50/mo leak.

Free audit
$0

A one-time report on your top cost changes and their fixes.

  • One-time report
  • Top cost changes, explained
  • Suggested fixes
Join the waitlist
Starter
$49/mo

AWS bills up to $10k/mo.

  • Weekly digest
  • PR correlation
  • Slack + email
Join the waitlist
Growth
$149/mo

AWS bills up to $50k/mo.

  • Everything in Starter
  • Multiple accounts
  • Daily alerts
Join the waitlist

We're building this right now. Be first to know when it ships.

Leave your email to reserve the founding price. No card, no charge, and no spam. We'll only email you when it's ready.

Good questions

Before you hand over access

What AWS access do you actually need?

Read-only billing data, CloudTrail, and resource metadata — via a role you create yourself from our public CloudFormation template. We can't write to your account.

What do I need to set up?

The read-only role, plus Cost and Usage Report (CUR) 2.0 with resource IDs enabled on your account. We'll walk you through turning it on — your cost history with CostBlame starts from that day.

Is it always right about the cause?

No. It shows what changed at the same time and how strong the link is. If there's no clear link, it says so.

Which clouds do you support?

AWS only, for now. GCP and Azure are next, once the AWS beta is out.

When does this actually launch?

We're building it right now. Everyone who reserved gets an email the day it's ready, with the founding price.

Do I have to pay anything now?

No. Reserving is free and needs no card. If you don't like it at launch, you just don't sign up.

What counts as AWS spend?

Your monthly AWS bill before credits.

What if I go over my limit?

We'll tell you before anything changes. No surprise charges.

Why no free plan?

The free audit shows what we'd find. Paid plans catch new issues every week.