Dutch Government Builds Microsoft Alternative on NixOS
The Dutch government is building an alternative to Microsoft for its public sector IT, based on NixOS. The project, called DAWO (Digital Autonomy Working Object), aims to reduce the Netherlands' dependence on foreign tech giants and reclaim control over government infrastructure[1].
The story reached 169 points on Hacker News with 70 comments in its first few hours, sparking discussion about sovereignty, open source in government, and the practical challenges of replacing entrenched Microsoft ecosystems[2].
What is DAWO?
DAWO is a community-driven initiative that brings public values and technology together. The project pursues five primary goals[1]:
- Digital autonomy: Strengthening the digital independence of the Netherlands
- Collaboration: Improving knowledge sharing between governments and society
- Security: Safeguarding security and data protection
- Innovation: Encouraging more efficient ways of working
- Verifiability: Making government IT systems easier to inspect and verify
Why NixOS?
NixOS is a Linux distribution built around the Nix package manager, which uses a declarative configuration model. The entire system state, from packages to services to users, is defined in a single configuration file. This makes systems reproducible, rollbacks trivial, and changes auditable, all properties that matter enormously for government infrastructure where transparency and accountability are legal requirements[2].
For a government looking to verify exactly what software is running on its machines and guarantee that no undocumented changes have been made, NixOS offers something Windows fundamentally cannot: a declarative, reproducible system state that can be version-controlled and independently audited[2].
The Microsoft problem
The HN discussion highlighted growing frustration with Microsoft's direction. Commenters pointed to recent Microsoft patents describing camera and microphone monitoring to block programs while showing ads, with users earning credits by watching ads to unlock their own software. Others complained about changes to user agreements for paid services that add tracking and advertising, where declining means losing access but still getting charged[2].
For governments, the concerns go beyond user experience. Dependence on a single foreign vendor for critical infrastructure creates national security risks. Microsoft's recent security failures, from nation-state email breaches to faulty updates that crashed millions of systems, have made the case for alternatives increasingly concrete[2].
Self-hosted and sovereign
The DAWO project self-hosts its code on code.overheid.nl, the Dutch government's own code hosting platform, with a subset mirrored on Codeberg. This aligns with the project's sovereignty goals: the government controls its own infrastructure, its own code hosting, and its own development workflow, rather than depending on GitHub or another foreign platform[2].
The HN discussion noted that this approach mirrors a broader trend. Governments and organizations are increasingly questioning whether critical infrastructure should depend on services controlled by foreign corporations subject to foreign laws. The Netherlands is not the first to ask this question, but the choice of NixOS as a foundation is technically interesting. It suggests a focus on reproducibility and auditability rather than just cost savings[2].
Why it matters
Government adoption of open source infrastructure has historically been slow, hindered by vendor lock-in, lack of internal expertise, and the comfort of familiar tools. The DAWO project represents a meaningful step toward digital sovereignty, not just in principle but in practice. If successful, it could serve as a template for other European governments looking to reduce dependence on foreign tech vendors[1].
The choice of NixOS is particularly noteworthy. It is not the easiest Linux distribution to deploy, but its declarative model offers guarantees about system state that no conventional distribution can match. For a government where verifiability is a legal requirement, that tradeoff makes sense[2].
Sources
[1] DAWO: "Working together on digital autonomy"
[2] Hacker News discussion (169 points, 70 comments)