The Finopscraft Blog
Engineering-first writing on cloud cost forecasting, waste detection, and FinOps practice for engineering teams.
The Hidden Cost of Orphaned Cloud Resources
Unattached EBS volumes, forgotten snapshots, and idle load balancers. Most teams don't realise how much these accumulate until the bill arrives.
Multi-Cloud Cost Attribution: Tag Strategies That Actually Work
Consistent tagging across AWS, GCP, and Azure is the unglamorous prerequisite for real per-team cost visibility. Here's what we've seen work.
Engineering the FinOps Feedback Loop
Finance sees the bill. Engineering writes the code. The feedback loop between them is usually a monthly spreadsheet. It shouldn't be.
RDS Overprovisioning: The Silent Budget Killer
Teams provision RDS instances for peak load and forget them. Six months later, that db.r6g.xlarge is running at 4% CPU. We flag it automatically.
Slack Alerts for Cloud Spend: What to Send and What Not To
Too many cost alerts and engineers learn to ignore them. Too few and anomalies compound silently. This is our threshold design for Slack cost notifications.
Forecasting Seasonal Spikes in Cloud Spend
Black Friday traffic. Q4 batch processing. End-of-quarter reporting jobs. Seasonal patterns in cloud spend are predictable, if you have the right model.
AWS Cost Explorer vs Custom Forecasting: When to Build Your Own
AWS Cost Explorer gives you last-month's actuals and a straight-line extrapolation. Here's when that's enough, and when it isn't.
Idle EC2: A Taxonomy of Waste
Not all idle EC2 is the same. Dev environments, forgotten blue-green deployments, and load-balanced standby instances each need a different remediation path.
How We Built the First Version of Finopscraft in 60 Days
What we shipped first, what we cut, and what we got wrong building a cloud-cost forecasting tool as a two-person team.