⏱️ Lectura: 9 min
The Netherlands has decided that its next government desktop won’t be bought closed: it will be built in public, block by block, and anyone can review the code. That’s the project behind DAWO (Digitally Autonomous WOrkplace), a community that brings together the Dutch government, the tech industry, and civil society around a shared goal: a digital workplace that can be inspected, audited, and replaced piece by piece.
📑 En este artículo
The project doesn’t sell a closed product. It splits the problem into blocks (AI, operating system, cloud, and collaboration) that combine with each other and that, according to the official site, allow “every part can be inspected and replaced.” That architecture is DAWO’s central bet against a problem Europe has been discussing for years: dependence on a handful of foreign providers to operate the public sector’s digital infrastructure.
TL;DR
- DAWO brings together Dutch government, industry, and civil society to build an autonomous digital workplace.
- The architecture is divided into four replaceable blocks: AI, operating system, cloud, and collaboration.
- The project’s operating system is called DAWO-NixOS and aims for a reproducible, inspectable workplace.
- Five goals guide the project: digital autonomy, collaboration, security, innovation, and verifiability.
- Calendar, news, blog, and forum are public and live on the community’s member portal.
- Posting on the forum requires an account, though reading it is open to anyone.
- Joining is possible through conversations, code, documentation, pilots, or events, with no single formal path to entry.
What happened with DAWO
The DAWO site presents an already-operating community, not an isolated announcement. It publishes a complete blueprint with four block categories, a component catalog for each category, and a member portal where an events calendar, news, blog, and forum coexist. The slogan the site repeats sums up the intent: “Not for the community. With the community.” Government, industry, and civil society don’t fund an external provider: they write the same blueprint together.
The five goals the community declares organize the rest of the project. Digital autonomy seeks to strengthen the Netherlands’ ability to operate its own infrastructure. Collaboration aims to improve knowledge exchange between governments and society. Security covers data protection. Innovation pushes for more efficient ways of working. And verifiability, the fifth goal, is perhaps the project’s most specific one. It seeks to make government IT systems easier to inspect, not just to use.
Context and history of digital sovereignty
The idea that a government builds its own technology stack instead of buying it pre-packaged isn’t new. It’s part of a broader debate known as digital sovereignty, which gained momentum in Europe as more public services came to depend on infrastructure operated outside the continent. DAWO didn’t invent that debate, but it proposes a concrete answer: instead of negotiating audit clauses with a single provider, it publishes the complete blueprint and lets anyone review it.
The choice of NixOS as the foundation for the operating system block, named DAWO-NixOS on the site, doesn’t seem accidental. NixOS is a Linux distribution that describes the entire system configuration as code and rebuilds that system reproducibly from that description. For a government that needs to be able to audit exactly what runs on each machine, that property (reproducibility from a declarative configuration) matters more than any desktop feature.
Technical details: DAWO’s four blocks
DAWO doesn’t publish a single piece of software: it publishes a catalog for each category and, within each category, independent components that can be swapped out. The table below summarizes what each block solves according to the official site’s documentation.
| Block | What it solves | Published technology base |
|---|---|---|
| AI | Open, verifiable AI components for the workplace | Proprietary catalog of AI components |
| Operating system | Reproducible, auditable workplace | DAWO-NixOS and installation blocks |
| Cloud | Autonomous, verifiable cloud infrastructure | Cloud infrastructure blocks |
| Collaboration | Communication, documents, and joint work | Open collaboration solutions |
The common thread across the four blocks is that none of them is presented as a monolithic solution. The site itself states it literally: “Not one single product, but separate building blocks that work together. Every part can be inspected and replaced.” That criterion runs through the entire project. If a cloud component stops being suitable, it gets replaced without touching the collaboration block; if a better AI alternative appears, it slots in without rewriting the operating system.
💭 Key point: verifiability isn’t just another block, it’s the criterion that runs through the other four. Each component is published so a third party can inspect it, not just so it works.
flowchart TD
G["Government"] --> COM["DAWO Community"]
I["Industry"] --> COM
S["Civil society"] --> COM
COM --> AI["AI Block"]
COM --> OS["DAWO-NixOS Block"]
COM --> CL["Cloud Block"]
COM --> CB["Collaboration Block"]
AI --> WP["Autonomous digital workplace"]
OS --> WP
CL --> WP
CB --> WPHow to start participating in DAWO
No account is needed to read. The events calendar, news, blog, and forum are public and live on the member portal linked at dawo.community. Posting on the forum does require registering, and the community invites participation in five ways: conversations, code, documentation, pilots, and events.
The site doesn’t yet publish a public step-by-step installation manual for DAWO-NixOS, but it does make clear that this block relies on NixOS. Anyone who wants to understand firsthand what a “reproducible workplace” means can try the same idea with a standard Nix flake. This is an illustrative example of Nix’s reproducibility philosophy, not DAWO’s official module:
{
description = "Reproducible base environment, DAWO style";
inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
outputs = { self, nixpkgs }: {
devShells.x86_64-linux.default =
nixpkgs.legacyPackages.x86_64-linux.mkShell {
packages = with nixpkgs.legacyPackages.x86_64-linux; [
git
firefox
];
};
};
}
With Nix installed and flakes enabled, nix develop rebuilds that exact environment on any Linux or macOS machine from the same file. That’s the property DAWO-NixOS brings to the full workplace: the configuration, not a disk image, is the source of truth.
A step closer to a real workplace would be declaring the entire system instead of just a development environment:
# configuration.nix (illustrative example, not DAWO's official module)
{ config, pkgs, ... }:
{
imports = [ ./hardware-configuration.nix ];
environment.systemPackages = with pkgs; [
firefox
libreoffice
git
];
system.stateVersion = "25.05";
}
After sudo nixos-rebuild switch, you can confirm exactly what changed in the system with nix store diff-closures /run/current-system ./result. That comparison is, essentially, the verifiability DAWO promises at the workplace level, applied here to a personal laptop instead of a full government deployment.
Impact and analysis
The replaceable-blocks model solves a real problem. When a government depends on a single provider, migrating away from that provider carries a very high cost. If cloud, operating system, collaboration, and AI are independent pieces, changing one doesn’t force a rebuild of the other three. That separation is, fundamentally, the same logic behind Europe’s digital sovereignty debate: reducing the exit cost before you need it.
The trade-off is real, and the Nix ecosystem itself knows it well. The learning curve of a declarative system like NixOS is steeper than that of a traditional distribution. Migrating an entire fleet of desktops to a DAWO-NixOS model requires training support teams in a different paradigm: declaring the system’s state instead of installing it by hand, something that doesn’t happen overnight in a large public administration.
⚠️ Heads up: DAWO’s official site doesn’t publish adoption figures, budget, or a deployment timeline. What exists today is the blueprint, the component catalog, and the community that maintains it, not a large-scale migration report.
Verifiable isn’t the same as already verified, and that distinction matters. Publishing a component as open source makes it possible to audit, but the audit itself requires that someone (government, industry, or an independent researcher) actually carries it out. DAWO opens the door through its forum and member portal; the review work remains human.
What’s next for DAWO
The path the site itself lays out is the catalog: each block category (AI, operating system, cloud, collaboration) links to a component page under constant update. The logical next step for a government team or an interested company is to read that catalog, join an event on the public calendar, and if a component proves useful today, replicate it or open a discussion on the forum.
📖 Summary on Telegram: View summary
Try it today: go to dawo.community, open the catalog for the block that interests you most, and see what component is already published.
Frequently Asked Questions
What is DAWO?
DAWO (Digitally Autonomous WOrkplace) is an open community in which the Dutch government, the tech industry, and civil society build a digital workplace for public administration together, as described by the official site dawo.community.
Is DAWO a single software product?
No. The site itself clarifies this literally: “Not one single product, but separate building blocks that work together. Every part can be inspected and replaced.” It’s an architecture of independent blocks, not a closed suite.
What building blocks does DAWO publish?
Four categories: AI, operating system (DAWO-NixOS), cloud, and collaboration. Each one links to its own component catalog on the official site.
Who can join the community?
Anyone can read the calendar, news, blog, and forum from the member portal. Posting on the forum does require creating an account.
What does verifiability mean for DAWO?
It’s one of the project’s five declared goals. It seeks to make government IT systems easier to inspect and verify, not just to operate.
How can you participate without being part of the Dutch government?
The site invites participation through conversations, code, documentation, pilots, and events, without explicitly restricting those paths to a single country or sector.
References
- DAWO Community: the project’s official site, with the complete blueprint and component catalogs for each block.
- NixOS: the open source project the DAWO-NixOS operating system block relies on.
- Digital sovereignty (Wikipedia): general context on the digital sovereignty debate that motivates initiatives like DAWO.
📱 Like this content? Follow @programacion on Telegram for daily tech content in Spanish: quick summaries, fresh content every day.
Imagen destacada: Foto de Fotis Fotopoulos en Unsplash
0 Comments