The hardware sits two hours from the Hungarian border. The jurisdiction does not travel with it.

What the article says

Portfolio's piece draws on Politico's reporting. Construction at Kronstorf started in spring 2026. On power the article gives one figure, and gives it conditionally, as do we: the first phase already carries a significant energy demand, a possible expansion could triple it, and the site would then reach 7 percent of Austria's current electricity consumption, more than every household in the two-million-person capital combined. The company promises around 100 new jobs.

Local opposition, led by IT professional Harald Müllner and ecologist Christina Gruber, objects to farmland rezoning, heavy water use, cooling from the Enns, and a regulatory gap: a wind turbine needs a strict environmental impact assessment, while a data centre of this size is exempt under current Austrian law. Google's head of communications points to solar panels and a river ecosystem fund; the protesters call that greenwashing and now aim to block the second, expansion phase. The article also gives the other side: the Austrian government and the EU want bureaucratic obstacles removed so that Europe does not fall behind the US and China.

One argument is about ownership: an American company takes the sites with the best infrastructure while the profits go to the US. The article reports it as the activists' view and leaves it there. We pick it up.

"Runs in an EU region" hides three separate questions

When a vendor tells you your data runs in an EU region, it is talking about three different things at once.

The first is geography: which country the server stands in. That decides latency, and whose planning, energy and water law applies to the building. For Kronstorf, that is Austria, and almost the whole debate in the article is about this.

The second is ownership: who owns the hardware and where the revenue goes. In Kronstorf, a US company. This is the protesters' argument, in economic terms.

The third is jurisdiction: which country's authorities can compel the owner to hand over the data stored on it. Under the US CLOUD Act of 2018, US authorities can request data from a US-based provider even when that data is stored in the EU. A US company's Austrian data centre is therefore in Europe geographically, and not necessarily legally. The article does not cover this layer; it is our addition.

The Kronstorf debate asks the first two. Nobody in the article asks the third. Yet for a Hungarian company handling contracts, patient records or financial data, only the third is about its own data. The farmland and the Enns are Austria's business. The jurisdiction question is yours as well.

Proximity is a point in Kronstorf's favour, and we should say so

The headline leans on the site's closeness to the Hungarian border. The project is in Austria, no Hungarian authority has a say in it, and two hours is driving time, which means nothing operationally. In network terms it means the opposite of what the headline implies. Kronstorf is closer to Budapest than Frankfurt or Amsterdam, where the big vendors' European regions typically run today, so a service delivered from there would give a Hungarian customer shorter round trips. If Google ever serves Hungarian customers from Kronstorf, geography is an argument for it.

One caveat. The article does not say what service will run at Kronstorf, and the capacity may never become a region Hungarian companies can buy. The point is therefore broader than Kronstorf: geography is the one question where a US hyperscaler's Austrian site could beat its existing regions. On the other two, the answer is the same as in Frankfurt or Virginia.

What we think, including the parts that cut against us

Four things we would rather say ourselves.

The first is self-interest. We sell exactly what the third question measures: operated private AI on EU hardware, under EU law, so an article like this is commercially convenient for us. That is why the geography section comes first, and why we say plainly that the three questions matter only for confidential data. For a public website, marketing material or a test database, a US hyperscaler's Austrian region is a perfectly good place, and for many Hungarian companies the right call.

The second is the environment. Most of the article's debate is about water and power. That objection applies to all compute, ours included: our GPUs draw power too, just less of it because there are far fewer of us, which is not an environmental advantage. A vendor with a few racks cannot credibly claim a lighter footprint than a hyperscale data centre, so we do not borrow the argument. We covered water and energy in August, on the planned AI campus near Paks; this piece is about ownership and jurisdiction only.

The third is the 7 percent. The article uses the conditional and ties the figure to a possible expansion; it gives no number for the first phase now under construction. Quoting it as a fact is inaccurate, and the first careful reader will check. We kept the article's wording.

The fourth is sourcing. Portfolio's piece rests on Politico's reporting and the activists' case; Google's response in it is limited to environmental mitigation. We did not open Google's own announcement, so we make no claim about what exactly is being built at Kronstorf or for whom. We build on one fact, the owner's identity, and that is not in dispute.

Where we stand

Our answers to the three questions. Where does the hardware stand? On our European hardware for the ATAILA Cloud edition, in your own data centre for Enterprise; the editions page sets out the difference. Who owns it? A business registered in Hungary in the first case, details in the imprint; you in the second. Whose law? EU infrastructure and an EU operator, with no US data processor on the path. The CLOUD Act reaches US-based providers, and we are not one; our GDPR guide spells this out. What you build on the platform is yours, and if you leave you take the code, the database and the files, as written on our ownership page.

That answer is not flawless either. Our GPUs come from an American manufacturer, and our open-weight models come from US and Chinese developers. Our answer is complete on the three questions and partial on the supply chain. The article's logic applies to us as well.

We agree with Portfolio's diagnosis: at Kronstorf, a US company is building on EU soil, and the locals are entitled to argue about it. We move the conclusion one layer over. When a vendor says "EU region", ask one question: which country's authority can compel the owner to hand over the data? If the answer is not European, geography will not help.