Google's €13B Finland bet runs on a 22-year nuclear PPA

Google committed at least €13 billion to Finnish data centers and signed a 22-year nuclear power agreement to run them. The September 9 announcement covers four sites across 2027 and 2028 — Hamina, Kajaani, Muhos and Vaala. It is Google's largest single investment in Europe. The number worth your attention is not €13 billion. It is 22 years.

What actually happened

The spend runs over two years, 2027 and 2028, across four Finnish municipalities. Hamina has been a Google site since 2009 and is one of the company's 43 cloud regions. Alphabet president and CIO Ruth Porat framed it as building "on more than 15 years of sustained investment."

The energy side is the structural part. Google signed a 22-year power purchase agreement with Fortum tied to a life extension of the Loviisa nuclear plant, which supplies roughly 10% of Finland's electricity. Per Data Center Dynamics, offtake starts smaller in 2028 and rises to as much as 50% of Loviisa's capacity from 2030 through 2049. There is also a memorandum of understanding to explore new generation capacity, including potential new reactors at the site.

Google's release puts the construction-phase GDP contribution at an average €3.6 billion a year and cites 7,000 annual jobs once operational. Those are the company's own projections in its own announcement — useful for scale, not for forecasting.

Why a 22-year power contract matters for your business

Here is the translation. Your AI vendor's cost base is shifting from a variable expense it can pass through to you into a fixed obligation it has already signed. Contracts that end in 2049 do not get renegotiated because inference demand dipped in Q3. They get paid, and the payments have to come from somewhere.

That cuts two ways, and both are worth planning around. Capacity in Europe stops being the scarce thing — a hyperscaler that locks a nuclear baseload for two decades is not going to be capacity-constrained in that region, which is good news if you have EU data residency requirements and have been fighting for quota. But the cheap-tokens phase is being financed by capital that now expects a return on a twenty-year schedule. Prices that only ever go down are not consistent with that balance sheet.

What we tell clients, unchanged by this news but sharpened by it:

Keep contract terms short while vendor cost structures are getting long. A twelve-month AI commitment signed today is a bet on pricing you cannot see. Annual beats multi-year until the market settles.

Measure your cost per completed task, not per token. Token prices move for reasons that have nothing to do with you. What you can control is how many calls a workflow takes to finish, and that number is yours to reduce.

Keep a second provider wired and tested. Not as a plan, as a code path you have actually run in the last month. Regional capacity announcements change where you can run something; they do not change who owns the switch.

We build automation with the model provider behind an interface, cost instrumented per workflow rather than per call, and a fallback path that gets exercised — so a vendor's twenty-year balance sheet decision stays their problem.

Sources: Google Cloud Press Corner, Data Center Dynamics.