Save your pocket and more by implementing FinOps! — David Sterz
summary
A concise FinOps playbook: implement OpenCost centrally to get per-namespace cost transparency (resolves cloud provider blind spot), follow the FinOps phases inform, optimize, operate, then automate actions. Installing Carpenter (just-in-time node provisioning) drops billable VM spend immediately; careful pod right‑sizing and cluster autoscaling raise profit by ~41% in the example. Moving CPU workloads to graviton chips cuts price and carbon by roughly 25%. The claim is practical: visibility plus targeted automations produce measurable savings while preserving performance.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 3:09What is FinOps and its importance
- 8:27Shared platform team scenario setup
- 14:27Challenges in FinOps adoption
- 18:41Inform phase and cost allocation
- 23:14Optimize phase and cost reduction
- 26:03Getting engineers to take action
- 30:19FinOps for business value and sustainability
- 32:26FinOps framework and community involvement
- 33:08Q&A session
related talks
41mFinOps and Cloud Cost Optimization
12mFinOps on AWS: Accelerated outcomes to maximize ROI
31mGetting the Most out of Every Dollar Spent in Cloud
05mFive Minute Cost-Optimisation
35mHow Did We Spend So Much? -FinOps Is Your Best Friend-
19mFinOps for business results
31mArchitecting an Optimal FinOps Platform
24mAn Introduction to FinOps