Cloud costs, accountability and FinOps: a Nordic public‑sector perspective.

Public sector organisations in Finland and across the Nordics are often described as slow, resistant, or overly cautious – especially when it comes to cloud and FinOps.

I don’t think that’s true.

What I see instead are organisations carrying real responsibility. Legal responsibility. Public accountability. Decisions that not only affect budgets, but services, jobs and citizens. When you operate under that kind of weight, you don’t rush head‑first into every new framework that comes along.

And yet, this is exactly why FinOps resonates so strongly in the public sector once it’s properly understood.

Public sector isn’t resistant. It’s accountable.

In private companies, FinOps adoption is often pushed through incentives: KPIs, bonuses, margin pressure. In the public sector, those levers don’t exist.

Decision‑making is slower because officials are personally accountable for outcomes. Risk tolerance is low by design. Transparency isn’t just cultural – it’s legal. I see it as a responsibility.

What’s interesting is what happens when you sit down with public‑sector teams in Finland and walk through real cloud cost data.

Curiosity takes over. People don’t push back against visibility. They ask questions. They want to understand what’s happening below the surface. They want predictability. They want to know what tomorrow looks like if nothing changes.

FinOps doesn’t threaten that mindset. It supports it.

Why cloud costs feel especially uncomfortable in public organisations

Many Finnish public‑sector cloud environments share the same origin story: lift‑and‑shift migrations driven by urgency, not optimisation.

Legacy systems were moved quickly. Architectures stayed largely the same. Governance models remained rooted in on‑prem thinking. And cost visibility ended up concentrated in one place – often with a single, very stressed person in finance.

When costs are hidden, FinOps feels dangerous. There’s an unspoken fear: what if we look too closely and discover something we can’t explain or control?

So the cloud bill gets treated like a fixed cost. Something that’s assumed to be “about right”. Something that will hopefully stabilise on its own. It won’t.

Cloud doesn’t behave that way. Idle resources still cost money. Forgotten disks still cost money. Logs from systems decommissioned years ago still cost money. These costs quietly compound – until they don’t feel quiet anymore.

When cost governance becomes human

Over the past year, something has shifted – particularly in the Finnish public sector.

For the first time in many years, several institutions have faced redundancy negotiations. Suddenly, saving €1 million in cloud spend isn’t theoretical. It’s tangible. It can mean 20 jobs retained. Possibly your own.

That changes the conversation completely.

Without bonuses or financial incentives, the motivation becomes collective responsibility. FinOps stops being a “finance initiative” and becomes a way to protect services, people and long‑term stability.

In those moments, cost governance becomes human.

FinOps doesn’t require perfection

One of the most persistent myths I hear is that you need a perfectly modernised cloud environment before you can start FinOps. You don’t.

One large Finnish public institution I’ve worked with began its FinOps journey in a far‑from‑perfect state. There were legacy workloads, conservative governance and years of accumulated cloud decisions layered on top of each other. Nothing about the environment was “FinOps‑ready” on paper.

They weren’t ready for sweeping reforms. And they didn’t have to be. They started small – with visibility.

Then they introduced ownership at the application level. Not full transparency for everyone but just the right data for the right teams. Over time, accountability followed. And slowly, behaviour changed.

Their experience shows that FinOps isn’t something you wait for until the cloud is “done”. It’s something that helps you get there.

Transparency isn’t the problem people think it is

A common fear in public organisations is that cost transparency will create resistance or conflict. In practice, the opposite is often true.

Developers don’t need to see the entire cloud bill. They need to see the cost impact of their own applications. That alone creates awareness and ownership.

Once teams understand why something costs what it costs, most respond rationally. The waste becomes obvious and the trade‑offs become clearer. Decisions become easier to justify – internally and externally. FinOps introduces clarity.

Why now?

Several forces have converged to make FinOps unavoidable in Finland and the Nordics.

Cloud estates have matured and accumulated years of layered costs. AI experimentation has introduced new, unpredictable spending patterns, where a single misconfiguration can turn into a six‑figure invoice. And economic pressure has sharpened focus on efficiency in a way that simply wasn’t present a few years ago.

A different kind of cultural change

FinOps in the public sector doesn’t look like FinOps in a startup or a multinational. And it shouldn’t. Without bonuses or KPIs to drive behaviour change, as in private companies, public sector must find different motivators.

What works there is shared understanding, logical arguments and clear data. Small, defensible steps.

When people understand how cloud costs behave – and how their decisions influence them – behaviour shifts naturally because the system finally makes sense.

And for public‑sector organisations built on responsibility and transparency, that’s exactly the kind of change that lasts.

If this reflects your own organisation’s situation, now may be the right moment to take an honest look – to understand what’s there and where to start.