Nothing exotic: - A NAT gateway was added - An RDS replica count increased - No alarms fired - No dashboards changed
The PR would have merged like any other infra change.
We built a small tool that runs cost checks directly in PRs: - Shows a before → after cost estimate - Flags high-risk patterns (unbounded loops, chatty APIs, over-provisioned infra) - Optionally blocks merges on policy thresholds
We put together a public demo repo where you can open a PR and see the cost feedback:
https://github.com/CloudVerse-Pte-Ltd/devx-cost-regression-demo
Curious how others handle cost regressions at code-review time.
cdeshwal•2w ago
They’re small PRs that: - Add always-on resources - Increase replica counts - Introduce N+1 API calls or polling loops
By the time dashboards show it, the code is already in prod.
Happy to answer questions on how the estimates are calculated or what patterns we flag.