Skip to the card

Card 140 of 9742026-10-01 issue

Observed arrival · 2026-10-01

CostTrace asks what the deploy did to the bill

costtrace.dev Visit website
Editorial interest 80/100 Selection signal · not a rating of the site

An open-source tool that compares cloud-billing data with deploys and pull requests to trace changes in actual spend.

Landing page captured for the 2026-10-01 issue.
For
FinOps teams and developers tracking cloud spend per deploy
Worth noticing
Its sample separates a September spend increase into usage, new resources, rate, and period-length changes.

Field notes

The documented workflow reads FOCUS-format billing exports, compares periods, splits changes into usage, rate, and new or removed resources, then aligns them with deploy metadata. In the sample, a September increase of $3,082 is divided into +$1,928 usage, +$1,016 new resources, +$511 rate, and −$373 period length. Another example connects a database cost rise to an application-code change despite no infrastructure diff, while explicitly avoiding a claim of causation.

Observed signals

Read the marks

Editorial observations of this landing page, not a rating.

○OpenPublic substance visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use

One card from the complete issue

Pink Dolphin Slippers

676,985 arrived 1,000 judged 974 catalogued Enter the complete issue
costtrace.dev

Landing page observed 2026-10-01. The live site may have changed.