kodebeat / themes / cloud-cost

What moved your cloud bill last month?

The invoice is one number. These tools show what changed, who changed it, and what is safe to switch off.

Find it, price it, stop it

Measurement first, then the smallest safe intervention. Anything not publicly released is marked.

Find it, and price it

The bill is a sum; the cause is a change. These attribute the movement, hunt the resources that cost money while doing nothing, and put a figure on the manual work that never appears on an invoice at all.

a ranked diff of two Cost Explorer periods cost-diff zombie resources, with confidence scores idle-hunter CI and pipeline toil, priced in euros toil-audit

Stop it

Halting spend is easy; halting it reversibly, with a recorded path back, is the part that makes it usable.

cuts ingress and drains compute, recording the restore path aws-killswitch

The papers

Every paper carries the methodology behind any number it emits, and what the tool deliberately does not do. Pick them up from the catalogue.

  • Knowing what changed your cloud bill, and whya ranked diff of two Cost Explorer periods
  • Stopping an AWS account's spend without losing anythinga reversible spend killswitch with a recorded restore path
  • Finding cloud resources that cost money and do nothinga zombie-resource scanner with confidence scores
  • Pricing CI toil in euros so it can compete for budgeta CI/CD toil analyser that prices the waste in euros

Cost and carbon are the same measurement taken twice. Cutting one usually cuts the other.

A question about any of this?

Ask about any tool or paper on this page in one message, and get one reply. The tools are open source and the papers are free.

Ask a question

Ask a question

One message, no follow-up sequence.

Your address is used to reply to this message and nothing else.