The Two Numbers Most FinOps Teams Confuse — or Ignore
Most FinOps teams track one number when they need two, and that single blind spot turns cost governance into a cleanup exercise instead of a control system.
Notes from the team building the autopilot.
Post-mortems. Benchmarks. The kind of FinOps detail you actually need before you run the migration. One post a week, no fluff.
The Hidden Invoice in Your Platform Engineering Budget
Platform engineering teams are paying $180,000 per year in duplicate tooling costs without a line item that names it (ZopDev, "The IDP Tax"). That cost has a name: the IDP tax. It accumulates because…
The Productivity Paradox at the Heart of Most IDPs
Most IDPs ship as friction-reducers and land as a new category of sprint tax. The promise is a self-service portal that abstracts infrastructure complexity. The reality, in production, is a platform…
The Alert Fatigue Trap: Why PagerDuty Alone Isn't Enough
Reactive alerting pipelines fail not because the tools are broken, but because the model is wrong. PagerDuty does exactly what it was designed to do: notify a human when a threshold is crossed. The…
Cloud Budgets Belong to Accounts, Not Resources
A budget only works when it lands on something a person can own. Most cloud budgets do not. They sit on a single resource or a resource group, objects that no team fully owns and no engineer checks…
The Fork Decision: Why Teams Are Reconsidering Terraform
HashiCorp's August 2023 license change from MPL-2.0 to the Business Source License forced every team running Terraform in production to make a governance decision they had not budgeted for. The BSL…
The Deployment That Looked Like Savings
Cost-cutting deployments fail SLOs not because engineers are careless, but because infrastructure assumptions are invisible until load exposes them.
AWS Databricks FinOps: Flagging Idle Isn't Stopping It
A flagged idle Databricks cluster keeps billing until something stops it. ZopNight now governs AWS Databricks end to end: discover, cost, recommend, and stop.
The Optimization Illusion: Why Cloud Savings Don't Last
Cloud cost optimizations expire. Not because engineers lose discipline, but because the infrastructure beneath every savings decision keeps moving. New services launch, teams grow, deployment…
The IDP Bill: $180k/Year in Hidden Platform Toil
Most engineering organizations budget precisely for building an Internal Developer Platform and budget nothing for operating one. The build cost is visible: headcount, tooling licenses, sprint…
The FinOps Honeymoon Period: Big Wins, Short-Lived
Every FinOps initiative follows the same arc: a burst of recoverable savings in the first weeks, then a structural decay that accelerates past month 3 (ZopDev, "Why FinOps Savings Decay Faster After…
AWS Bedrock Is an Estate, Not an API: FinOps for GenAI
AWS Bedrock cost is not token spend. It is an estate of agents, models, provisioned throughput, and jobs, each billed differently and easy to miss.
Get the weekly in your inbox.
One post a week. Sundays. No "10 ways to think about cloud" listicles, just the engineering and FinOps notes we'd want to read.