Glossary
The practice of treating cloud cost as an ongoing engineering decision rather than a monthly invoice that lands in accounting.
FinOps assumes that the people deciding architecture can also see what it costs. That sounds obvious and is not the case in many organizations: the invoice goes to procurement, the decision is made in the team.
At its core are three recurring steps: make it visible who owns which cost, assess the biggest levers, and measure the effect after the change.
How you notice it
Frequently asked
With attribution, not with saving. As long as it is unclear which cost belongs to which team and application, every measure stays a management topic. Once attribution exists, teams decide themselves, because they can see the effect of their architecture.