Governance decides who in a company may take which cost decision, how that decision is recorded, and what the platform prevents on its own. This chapter describes the operating model that keeps cloud cost owned as a company grows: the policies that set the frame, the people who decide inside it, and the processes that carry a decision to the place where someone will find it later. The chapters before this one explain what there is to decide; this one explains who decides it and how the outcome stays traceable.

What this chapter covers

The chapter has three sections, and each answers one question.

The policy section answers the question of what is allowed. A cost policy says which regions, services and instance sizes a team may use without asking, which tags every resource must carry, above what size a change needs sign-off, and who may see cost data at which depth. Guardrails are the form in which the platform enforces a policy by itself: an organisation policy that refuses a region, a tag policy that rejects a misspelled cost centre, a budget action that fires at a threshold. Approval thresholds are the form in which a person signs off a decision before it happens. The section explains what the three providers offer for each, how policies are kept as code, and where a guardrail does more harm than good.

The people section answers the question of who answers for the cost. It starts from the personas of the FinOps Framework and reduces them to the responsibilities someone has to hold in any company: who answers for a team's or a product's cost, who reads the invoice and closes the month, who buys commitments, who decides a saving, and who maintains the allocation. It also covers the measures these people are held to, and what ownership looks like in a small company where one engineer and one finance person hold several roles between them. FinOps Framework 2026: what small teams should actually change maps the current framework onto a team of that size.

The process section answers the question of when cost enters the decision path. Cost is committed in architecture and purchasing decisions long before the first invoice arrives. The section describes where a cost estimate belongs in the development lifecycle, how a change with a cost effect is handled, and how a cost decision is recorded so that it can be found again at the next monthly review, the next invoice variance, or the next audit.

All three sections rest on one principle: a rule that lives only in a document does not hold. It holds when the tool enforces it, when a person sees it in their own report, and when every exception carries a name and a date. The chapter is therefore less a set of templates than a description of which control sits where, and what happens when it is missing.

Key terms

  • FinOps: the discipline whose phases and personas this chapter uses as a frame, not as an organisation chart.
  • Budget: the quantity every approval threshold is set against, because an absolute amount is too high for one team and too low for the next.
  • Tag: the smallest unit of a policy; a tag policy decides whether a resource can be assigned to an owner at all.
  • Cost allocation: the rule by which cost is assigned to an owner; governance protects it from eroding with every new account.
  • Allocation coverage: the share of cost that has an owner, and the measure that shows whether the policies are working.
  • Showback and chargeback: the two routes by which a cost owner gets to see their numbers, and the point at which ownership stops being abstract.

Neighbouring chapters

The chapter before this one, Optimisation and savings, explains what is decided: which saving is possible, what it costs and what it returns. This chapter explains who decides it, who approves it and where the decision is recorded. The chapter after it, FinOps for AI, applies the same operating model to spend that grows faster and is harder to predict than classic infrastructure, with the same roles and the same thresholds.

Two earlier chapters supply the foundations. FinOps and cloud cost management holds the framework whose phases, principles and personas the operating model here implements. Allocation and ownership holds the allocation that this chapter's policies protect: without a rule for which cost belongs to whom, a cost owner has nothing to own. The overview of all chapters is in the handbook.