From Königsberg to Kongsberg: The Categorical Imperative in System Architecture
In my work with European digital sovereignty, I have realized that our greatest challenge is not a lack of code, but a lack of an intellectual foundation.
In 1724, Immanuel Kant was born in Königsberg. Exactly 260 years later, I was born in Kongsberg – a town that in mining history nearly ended up with the same name. But the similarity between the two towns doesn't stop at etymology; for me, the real connection begins in how we understand the foundation of our actions and the systems we build.
In my work with European digital sovereignty, I have realized that our greatest challenge is not a lack of code, but a lack of an intellectual foundation. We have built a digital civilization on "borrowed ground," controlled by actors whose principles stand in direct opposition to what I would call a universal architectural ethics.
The Kantian Imperative for Digital Systems
Kant's most famous contribution to philosophy is the categorical imperative: "Act only according to that maxim whereby you can, at the same time, will that it should become a universal law."
If we translate this into system architecture, today's dominant model – the proprietary "vendor lock-in" model – collapses immediately. An architecture based on closed APIs, extraterritorial control, and proprietary standards can never become a universal law. It only works as long as one party has the power to exclude others. It is built on asymmetry. If all actors acted according to the same principle – to wall in their users and deny interoperability – the global digital ecosystem would cease to exist. It is a model that is logically self-contradictory and fundamentally flawed.
The Quest for Architectural Autonomy
For Kant, autonomy – the ability to give oneself laws based on reason – was the very definition of a free human being. In a digital context, this means what I call architectural autonomy: The ability an organization or a nation has to define the framework of its technological existence, without being at the mercy of third parties' political or commercial whims.
In 2026, this autonomy is a fiction for most European enterprises. When 70% of our cloud infrastructure is controlled by three American companies, we don't just have an economic problem; we have abdicated our architectural autonomy. We operate within frameworks we did not set ourselves, on infrastructure that can be deactivated from another continent.
Building for digital sovereignty is therefore not a nostalgic wish for "national solutions." It is a Kantian project. Open standards down to the root level are the only maxim that can function as a universal law for a global infrastructure, and this is the very prerequisite for acting as a free subject in a digital future.
A Necessity, Not a Preference
Most European alternatives fail because they try to build copies of the giants with fewer resources. My answer is to transcend the paradigm itself by building on principles that withstand the test of universality. We cannot solve our time's greatest IT challenge by just swapping one vendor for another; we must swap the very philosophy behind the architecture.
Digital sovereignty is not ideology. It is a commercial and national necessity – and an architectural imperative you either build upon, or ignore at your own risk.