Skip to main content

The Apeldoorn Illusion: A Post-Mortem of Dutch Digital Sovereignty

·790 words
Ronny Roethof
Author
Ronny Roethof
A security-minded sysadmin who fights corporate BS with open source weapons and sarcasm
Table of Contents

The Dutch government has developed a new strategy for managing critical infrastructure, which I personally call the digital fuckups. The recent decision to hand the core of the Netherlands’ VAT collection system to the American firm Fast Enterprises is not a strategic partnership. It is a structural collapse of governance, driven by high workload pressure and profound, “unconscious incompetence” at the highest levels of the state.

The Fable of the Physical Server
#

State Secretary Eelco Eerenberg keeps reassuring Parliament: “The servers are in Apeldoorn.” Technically true, operationally meaningless. This is 20th-century thinking: a server is a box you can lock in a room. In the 21st century, power lives in the management layer, in proprietary code, automated pipelines, and remote administrative access—all governed by the US Cloud Act.

When the Dutch government claims security because the data sits in Apeldoorn, they are performing compliance theater. If the management layer is American, the system is American. If the update keys are in Washington, the system is in Washington. If Fast Enterprises decides tomorrow that Dutch fiscal logic isn’t worth maintaining, the servers in Apeldoorn are just expensive paperweights.

The Psychology of Unconscious Incompetence
#

Why does this keep happening? There’s a recurring theme: a fundamental lack of IT literacy among decision-makers. This is unconscious incompetence. Leaders treat IT like water: you turn the tap, and the VAT comes out. They do not understand that software is a living liability needing constant, autonomous control. Outsourcing the “thinking” parts of your tax system to a foreign entity is renting your sovereignty.

This incompetence is worsened by the “Productivity vs. Security” paradox. The Belastingdienst is under immense pressure: legacy systems rotting, staff overworked, and political promises demanding instant results. The “quick fix” of an American package looks like salvation. In enterprise terms, it’s a trap. Choosing Fast over Resilient trades long-term national security for a short-term political win.

The Architecture of Dependency
#

Experts like Bert Hubert and Marcel van Kooten have been sounding alarms. The Dutch government claims “control of all data traffic.” Modern software is opaque; you cannot check the traffic of a proprietary black box to know if a backdoor exists or a kill-switch is embedded in a mandatory update.

Every tax law change now requires American permission. The Netherlands has privatized legislative execution. If the US leverages this dependency during a trade dispute, the Netherlands has zero leverage. We handed over the keys to the front door, back door, and safe.

Operational Neglect and Skill Erosion
#

By outsourcing, the government ensures no Dutch civil servant will ever truly understand the VAT system at a code level. We are training a generation of contract managers powerless when the vendor stops performing. This is operational neglect on a grand scale.

Compliance vs. Resilience Gap
#

The government says: “We are compliant.” Compliance is not security. You can be ISO-compliant and still be completely vulnerable. Resilience is independent recovery. If Fast Enterprises disappears, the Netherlands cannot recover. No internal team can take over the codebase. No European alternative is ready.

Political Smokescreen
#

Barbara Kathmann’s motion shows the divide: those who understand the stakes vs. those who want the problem gone. “This question is not one-dimensional,” says Eerenberg. It is one-dimensional: ownership. Either you own your core systems, or you don’t.

Lessons from the Public Discourse
#

Public reaction has been intense and varied. Some comments highlight corruption concerns, dependency on US Big Tech, and lost internal expertise. The debate spans multiple platforms:

Conclusion: Reclaiming the Spine
#

The Ministry of Finance must admit they were out-negotiated because they didn’t understand the technology. They need lawyers, exit fees, and a European or internal alternative. Slower, more expensive, harder, but the only way to secure sovereignty. Rushed fixes like the QR-vaccination system show the dangers.

Bottom line: Physical presence in Apeldoorn is a red herring. If you don’t own the management, the code, and the lifecycle, you are not a partner. You are a tenant at the mercy of a landlord three thousand miles away. Stop the theater. Build a digital spine that belongs to us.

Author’s Note
#

This continues my ongoing series on systemic failures in enterprise environments. For analysis on workload pressure, operational neglect, and the strategic security paradox, see:

  • “Burnout in Cybersecurity: The Crisis We’re Still Ignoring” (roethof.net)
  • “The Dutch Kill Switch: Kyndryl, Solvinity, and the Sovereignty Mirage” (roethof.net)
  • “The Sleep-Deprived Sysadmin: A Personal Journey Through Burnout and Recovery” (roethof.net)

Related

The Digital Trump Moment: The Bill for Our Collective Negligence Is Due
·1080 words
The Dutch Government's New Vision on Digital Autonomy: Promises, Contradictions, and the Same Old Dependencies
·684 words
Inception-Level Evasion: When Your EDR Can’t See the Linux VM Hiding in Windows
·1114 words