Skip to content
BENIBIX Learn

FinOps and Cloud Bills

Level 4 · Running and paying

Why cloud bills grow faster than anyone thinks, and how to get coders and finance to share them. Who sees the bill, who pays it, and one format for all.

Course contentsLesson 10 of 11

After this lesson you can

  • Say what FinOps is for
  • Tell showback from chargeback
  • Explain why a shared bill format helps

11 mincovers 4 glossary entries

Worth reading first: Cloud Instances and Images

Who spends the money, and who sees the bill

FinOps is a way to run cloud spending as a team sport. Coders, finance and managers look at the same bill, often each week. They share the job of keeping it in check. It exists because in the cloud, anyone who can start a server can spend money. The bill comes a month later.

In a data centre, buying a server took weeks and a signature. In the cloud it takes a click. So costs spread across dozens of teams, and nobody feels the total until it lands on one desk.

FinOps runs in a loop of three steps. Inform: show each team what it spends. Optimize: cut waste and buy smarter. Operate: make it a habit, with goals and owners. Then the loop starts again.

Showing each team its share starts with labels. Each server and disk is tagged with the team that owns it. Showback then sends each team a report of its share, while one central budget still pays the whole bill.

Chargeback goes a step further. Each team's share comes out of that team's own budget. People watch spending far more closely when it is their money, but it takes clean labels to be fair.

Firms that use several clouds get bills in several formats, with different names for the same thing. FOCUS is a shared format for cloud bills. Bills from different clouds then line up, column by column, in one sheet.

The mistake is to make FinOps one person's job. A single analyst can find waste, but only the engineers who started those servers can turn them off. The habit has to live in the teams that spend.

The same bill, split the same way. Showback sends a report, and chargeback sends the cost.

Worked example

A test server nobody owned

A software firm's cloud bill rises 30% in three months. No team thinks it is theirs.

They tag every server by team. A weekly report then finds 14 large test servers left running since a project ended. Turning them off saves 9,000 euros a month.

The words for this lesson4

Check yourself

How is showback different from chargeback, when you split a cloud bill by team?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.