Topic
FinOps
Most FinOps programmes plateau at the same place: a dashboard exists, it is broadly accurate, and nobody changes behaviour because of it. The measurement problem was solved years ago by tooling. The remaining problem is that infrastructure cost is a consequence of engineering decisions made weeks earlier by people who never see the bill, and no amount of Grafana fixes that.
The material here treats cost as an engineering signal rather than a finance artifact. Allocation models and their failure modes — why shared cost distribution destroys the credibility of a showback report faster than any other single choice. Unit economics that survive contact with a product team, meaning cost per meaningful business event rather than cost per pod. Observability spend, which is the line item that grows fastest and gets audited least. And what maturity actually looks like past the dashboard stage: forecast accuracy, commitment coverage discipline, and the ability to answer why a number moved without a three-day investigation.
Articles in FinOps
-
Right-Sizing, End to End: A Methodology That Survives Contact With Engineers
A complete right-sizing process: percentile selection, workload classification, safe rollout ordering, verification, and the organisational mechanics that make the changes stick.
-
Observability Spend Grows Superlinearly and Nobody Owns It
Controlling logging, metrics, and tracing spend: cardinality budgets, tail-based sampling, tiered retention, and OpenTelemetry Collector patterns that cut cost without losing incident signal.
-
Cost Per Pod Is Not a Unit Economic
How to build infrastructure unit economics that survive contact with product teams: choosing the denominator, handling fixed cost, tracking marginal versus average, and the traps in cost-per-request.
-
FinOps Maturity Is Measured in Decisions, Not Dashboards
What FinOps maturity looks like past the reporting stage — forecast accuracy, commitment discipline, anomaly routing, and embedding cost into the engineering workflow rather than a monthly review.
-
Your Cost Allocation Model Is a Political Document
Allocation models for Kubernetes cost: idle distribution, shared-service treatment, requests versus usage as the billing basis, and how to build a showback report engineers actually believe.
Other topics
Kubernetes Platform Engineering AI Infrastructure Cloud Security