Know what a change actually takes off your Netlify invoice.
CostAssured connects read-only to your Netlify team and shows what is driving cost, what can safely change, and what each change returns against your plan allowances. We never write to your account.
CostAssured for Netlify is on its way
The engine is provider neutral: commitment-aware savings, safety classification and generated remediation already run today. Netlify is on the roadmap, and the waitlist gets the first invitation when scans open.
Where Netlify spend drifts
None of this is carelessness. It is what accumulates when usage grows faster than governance, and it is what CostAssured reads for, without writing anything.
Build minutes spent on branches nobody reviews
Every push to every branch can trigger a full build. Previews for stale branches burn minutes that were meant for the work you actually ship.
Bandwidth above the allowance
Uncached assets and heavy media push transfer past what your plan includes, and overage bills in blocks. Most of the excess is fixable at the asset level.
Form submissions, spam included
Form volume above the included level bills per submission, and spam counts towards it. A spam filter change can be worth real money.
Maximise value, eliminate accidental waste
You chose this platform on purpose and you pay for it on purpose. CostAssured finds the gap between what you meant to buy and what you are actually paying for, then prices every change both ways.
Read-only by design
CostAssured connects with read-only credentials and never writes to your account, on any plan. Every change stays in your hands.
Two numbers on every finding
Every saving is shown as a gross figure and an invoice-impacting figure, each with its basis: your confirmed contract rate, or the rate this account is actually billed.
Safety before savings
Findings are classified against a dependency graph. A resource referenced by an alerting, SLO or detection asset is never treated as low risk, and CostAssured will not recommend removing it.
Remediation you apply yourself
Every finding carries generated remediation artefacts: Terraform, a runbook or configuration JSON, each with a rollback. Generated, never executed.
We store usage metadata and configuration inventory, never telemetry or application content.