Earlier this week, I was invited to deliver a keynote in Germany before roughly thirty municipal mayors of a rural district. We were not there to debate abstract futures or speculate about artificial minds. We were discussing an immediate, deeply practical emergency: how local town halls are already struggling under an unmanageable wave of citizen appeals, planning objections, and official inquiries - and why AI agents represent the real revolutionary step in how we respond.

In that room, the mayors understood the dynamic with remarkable clarity. Today, any citizen with an ordinary web browser can use basic generative tools to formulate a ten-page, procedurally airtight legal objection to a municipal zoning decision in thirty seconds flat. What once required a specialist lawyer and two weeks of billable work now costs twenty cents of consumer compute.

On the other side of the municipal counter, civil servants are drowning in the deluge. Yet when local administrations explore even the most modest tools to summarize documents or assist staff - such as Microsoft Copilot - they frequently encounter institutional paralysis. Local councils debate for months and vote against deployment, hoping instead for an ideal, sovereign European alternative that does not yet exist.

The citizens are fighting with algorithmic fighter jets. The administration is being denied a bicycle.

The intention behind this hesitation is honourable: to maintain control, protect privacy, and preserve administrative autonomy. But looking across the broader landscape of European enterprise and public administration, we have to ask an increasingly uncomfortable question: are we pursuing a model of safety that cannot deliver on its promise, while quietly forfeiting the single greatest productivity shift of our time?

The uncomfortable reality of data security

I suspect you will not like where this reasoning leads. Truth be told, I do not like it either. None of us want to see personal or corporate information exposed. The desire to keep sensitive records close, under local custody and behind our own walls, is completely natural.

Yet the fact that neither of us likes this reality does not alter the fact that at the very moment you are reading these lines, the next major data breach is already taking place. It could not be prevented. And it will not be the last.

How long do we want to pretend that running local models is synonymous with data protection - and simultaneously synonymous with state-of-the-art capability? In all likelihood, the exact opposite is true.

Yes, a local model processes inference on your own hardware. But does that mean your local infrastructure is genuinely secure? Does it mean an unauthorized third party cannot penetrate your perimeter, elevate privileges, and exfiltrate your data? Countless incidents demonstrate that physical custody of a server offers very little protection against modern intrusion.

Consider the recent events in our own public administrations. In September 2026, the ransomware group Rhysida dumped 1.44 million files - roughly 5.8 terabytes of sensitive administrative records from the State of Berlin - onto the public dark web, including identity documents, personnel files, internal salary listings, and emergency blueprints, as reported by Der Spiegel. In Vienna, an unauthorized intrusion into the municipal documentation platform reported by Kurier compromised tens of thousands of internal documents affecting thousands of citizens and municipal employees.

Consider the trajectory: we failed to protect citizen data in the past, we are failing catastrophically to protect it in the present, and we will be infinitely less capable of protecting it in the future.

In the past, legacy architectures and bureaucratic inertia left public networks riddled with unpatched vulnerabilities. In the present, criminal syndicates casually extract terabytes of sensitive records from capital cities while authorities look on helplessly. But the future will make today's vulnerabilities look trivial. As offensive AI agents become ubiquitous, malicious actors will deploy autonomous systems that probe network perimeters, chain zero-day vulnerabilities, and exploit administrative misconfigurations at machine speed, twenty-four hours a day. If an underfunded municipal IT team running an on-premise server cannot defend against a conventional ransomware gang today, how do they expect to withstand an autonomous swarm of offensive AI agents tomorrow?

Believing that a self-hosted server in a municipal basement or corporate back room is safer than a hyperscaler facility with multi-billion-dollar automated defenses is an assumption we urgently need to question.

The capability gap: Between paper benchmarks and real work

Now consider the other side of the equation: capability.

Advocates of local deployment routinely suggest that open-weight models have solved the problem. It is true that open models are making extraordinary strides, particularly on static paper benchmarks. But anyone who has worked with them in production environments knows how sobering the reality can be unless one makes massive capital investments in specialized hardware.

My MacBook Pro M5 Max with 128 GB of RAM is a magnificent piece of engineering. It is a delight for experimenting with small models - especially if you want to warm your lap on a chilly evening. But in terms of raw reasoning speed, contextual fidelity, and agentic reliability, it remains miles away from what frontier models from OpenAI or Anthropic routinely deliver.

And suppose a small or medium-sized enterprise decides to take the local route. Suppose you invest hundreds of thousands of euros in dedicated GPU racks and specialized engineering talent to deploy a local alternative. Does that investment actually translate into the productivity gains your global peers are experiencing?

The Strategic Dilemma
Comparing the Integrated Agent Model with the Air-Gapped Approach
Trade-Off Analysis
Operational Dimension The Connected Agent Model The Air-Gapped Local Model Core Dilemma
Application Reach Integration
Native connections to Email, Calendar, Drive, CRM, Slack Isolated sandbox; manual data imports or custom scripts Fluid Workflows Cross-boundary
Reasoning Power Frontier
Frontier reasoning capable of multi-step autonomous planning Quantized or smaller models constrained by local compute Capability Gap Lower reliability
Capital Expenditure Investment
Predictable operational subscription / token usage Significant upfront hardware purchases, power, and maintenance Heavy CapEx Hardware depreciation
Operational Reality Autonomy
Asynchronous delegation: software executes complete outcomes Prompt-and-wait: human remains the manual bridge between apps Order of Magnitude Hours saved vs minutes

The structural paradox of isolation

The true wave of the AI revolution is not about better conversational chatbots. In the United States, platforms like Meta's Muse and OpenAI's Dots demonstrate where the paradigm is heading: software that moves beyond the answer box to become an active, persistent proxy.

These agents do not merely suggest draft replies; they autonomously coordinate appointments across calendars, reconcile invoices across bookkeeping systems, file claims, and resolve discrepancies across enterprise tools. In consumer applications, they already assist individuals in negotiating dispute letters or handling travel compensation claims. In enterprise environments, they handle operations that once required hours of human data transfer.

They do not improve productivity by 10 or 20 percent. They improve productivity by an order of magnitude - by thousands of percent - because they eliminate the human being as the slow, friction-laden bus between disconnected software applications.

Crucially, AI agents do not generate extreme productivity gains because a human remains in the loop at every microscopic step. They generate extreme productivity gains precisely when they can take shortcuts - when they can execute multi-step workflows without a person sitting in the middle. That is what makes our current mindset so paradoxical: anyone who wants productivity must be willing to delegate.

Imagine standing behind an employee, watching over their shoulder at every single keystroke, micromanaging every mouse movement, and insisting on approving every line before they hit save. It sounds absurd and paranoid, doesn't it? Yet why is that precisely the mental model we have adopted for artificial intelligence - and what we have mistakenly come to label "AI literacy"?

The very assumption that AI requires specialized "operator skills" reveals how fundamentally we misunderstand what this technology actually is. (And I write this with some irony, as someone who has authored an entire book series on "AI competence".) This is not about learning the technical knobs and buttons of an expert tool like Photoshop or SAP. It is about communication.

How do you explain to an AI agent what you need so that it delivers the outcome you intended? Exactly the same way you have always briefed your employees, colleagues, or external agencies. If your briefing was sloppy and ambiguous, the agency delivered something completely different from what you wanted. If your brief was precise, contextualized, and outcome-focused, you received excellence. The exact same law governs AI agents. What we need is not classical software-operator training; it is clarity of thought and the managerial courage to delegate.

And here lies the inescapable dilemma: an AI agent is only as capable as the systems it is permitted to connect, and only as fast as the autonomy it is granted.

Its leverage does not come from generating prose in isolation. It comes from bridging the gap between your inbox, your customer records, your documents, and your execution tools. The moment you decide to install a model locally in the hope of walling it off from the outside world, or insist on human micro-approvals at every internal turn, you sever the very mechanisms that make agentic work possible.

You cannot air-gap a system to guarantee isolation and simultaneously expect it to deliver the productivity leaps of an integrated agent. The two objectives are structurally in tension. One inherently limits the other.

The questions Europe must ask itself

If this analysis holds, European businesses and public institutions are currently on a path that risks delivering the disadvantages of both worlds:

We accept severe self-limitation in our technological capabilities, burdening our enterprises with expensive compromise architectures that cannot match global benchmarks. And we do so in service of an ideal of absolute data security that our own recurring leaks prove we are not achieving.

We need to ask ourselves several searching questions:

How long can our economy remain competitive if our tools remain isolated? When competitors abroad can download an agent, connect it securely across their workflow stack, and automate complex tasks overnight, how will our Mittelstand compete by maintaining bespoke, disconnected islands?

What are we telling the citizens whose data is already compromised? If our defensive posture cannot prevent major administrative breaches in our largest cities, is the answer really to insist on even more paperwork and slower adoption of modern defenses?

What does true digital sovereignty look like? Does sovereignty mean keeping an underpowered computer in our own basement - or does it mean ensuring that our public servants and enterprises have access to the most capable, resilient, and well-defended tools on earth?

Do I have the definitive answer for Europe or European enterprises? No, and I do not pretend to. We are standing before a profound, genuine dilemma.

The question is whether we can survive global competition while trapped in this dilemma if we act like Sisyphus - pouring virtually all our regulatory energy, political capital, and engineering talent into an objective that may simply be unachievable: absolute, leak-proof data security in a hyper-connected world.

And while our entire public focus remains consumed by that Sisyphean struggle, almost no one notices our greatest collective blind spot: that to this day, we have no real answers, no remedies, and no practical support for the millions of citizens whose personal data has already been dumped onto the dark web.

Strategic Takeaways

Navigating the Local Model Dilemma

  1. Recognize that custody does not equal security. Hosting an AI model on local infrastructure does not inherently protect your data from intrusion. True resilience requires active, modern threat defense, not merely geographical proximity to the hardware.
  2. Weigh the integration cost before choosing isolation. The primary productivity leap of AI agents comes from connecting across applications. An air-gapped model preserves containment, but at the cost of the workflow automation that defines the agentic era.
  3. Acknowledge the capability threshold. Small, localized models can be useful for targeted tasks, but multi-step autonomous reasoning still demands frontier capability. Budgeting for local hardware must be balanced against the opportunity cost of inferior cognitive performance.
  4. Equip public administration to match civic capability. When citizens can generate complex procedural filings at zero marginal cost, administrations cannot afford to ban modern assistive software while waiting for perfect solutions. Practical capability must match the scale of the challenge.
06

That's my take.