CostFinch Request a free scan

Estate estimator

What is probably sitting in your database bill?

Four questions. You get a range for each of the six focus areas the audit covers, and the reason each one applies to an estate shaped like yours. Every number below is modelled from published AWS pricing deltas and typical estate patterns — not one of them is a measurement of your estate. The page is honest about that in detail, because that distinction is the entire product.

Runs entirely in your browser · no email, no upload, nothing sent anywhere

Your estate

All services, before credits. A rough figure is fine — the output is a range anyway.

$30,000 / month
$2k$200k
AWS accounts in the organization

More accounts means more places non-production quietly accumulates.

Do dev / staging / QA databases run 24×7?

Including read replicas and anything left over from a migration.

Reservations or Savings Plans on databases?

RIs, reserved nodes, or a Savings Plan covering database compute.

Which of these do you run?

Breadth drives what share of the bill is database spend, and which findings can apply at all.

Estimated addressable database waste

—
per month, modelled range

Areas overlap — an instance you switch off at night cannot also be right-sized for those same hours. The total above applies a flat 15% overlap haircut to the sum of the lines. A real audit resolves overlap exactly, per resource, because it knows which resource each finding lands on.

Read this before you believe any number on this page

These are population ranges derived from published AWS pricing deltas (gp2→gp3, Graviton, RI and Savings Plan discount bands, Extended Support surcharges) and from patterns that recur across estates of a given shape. Not one of them is a measurement of anything you own. The model has never seen your account.

The audit replaces every line above with a measured number: p95 of hourly maxima over 60 days of CloudWatch data, memory headroom and connection counts verified, reservation gaps computed on reservable compute only, and every rate priced against the live AWS Price List. Where a rate cannot be verified, the report prints TBD instead of a saving.

That gap — between a plausible range and a defensible number — is the entire reason this practice exists. A cost dashboard showing you something like the figures above, and calling them savings, is the exact problem the audit was built to fix. So don't take this page into a finance review. Take the audit.