Ideas from the OptCloud team
Practical FinOps guidance grounded in industry research, not vendor folklore.
What the State of FinOps 2025 actually tells us
The FinOps Foundation surveyed organizations responsible for more than $69B in cloud spend. Here is what changed, and what practitioners should do next.
5 rightsizing patterns that actually reduce cloud waste
Industry research still puts typical cloud overspend around 30–35%. These five rightsizing patterns are where mature FinOps teams start, and where native cloud tools already help.
Kubernetes cost allocation without the pain
Cloud tools see nodes. Kubernetes tools see namespaces and pods. You need both, plus a clear showback-to-chargeback path.
Savings Plans vs Reserved Instances: a modern decision framework
AWS still offers both. Savings Plans are the default for flexible compute; Reserved Instances still win for specific, stable baselines, and for services SPs do not cover cleanly.
Tagging governance: the FinOps foundation most teams skip
You cannot allocate, showback, or route anomalies without ownership metadata. Enforce tags at provisioning, or FinOps stays stuck in Crawl.
Managing AI spend inside a FinOps practice
AI tracking jumped to 63% of organizations in the State of FinOps 2025. Most teams still need basic visibility before optimization.