Urgent.News

What's breaking now, across thousands of outlets.

Tech

Dutch government turns to NixOS for a sovereign desktop

DAWO combines a Linux-based client with open source tools for cloud, communications, and collaborative work

Dutch government turns to NixOS for a sovereign desktop

The Dutch government has taken an interest in developing a free and open-source software (FOSS) operating system for public administration, including a desktop environment. This initiative, known as the DAWO Project, aims to create a digital workplace that is self-sufficient and less reliant on external systems. The project, also referred to as "Digital Autonomous Government Work Environment," is being spearheaded by the Ministry of the Interior and Kingdom Relations.

DAWO combines various components, such as the operating system, cloud infrastructure, AI, communications, and collaborative tools, allowing for flexibility and customization.

The DAWO Project received official backing in July when the Dutch government's Interdepartmental Committee on Government Operations (ICBR) commissioned three government IT providers, DICTU, SSC-ICT, and DUO, to develop a standardized, more sovereign digital workplace. The core components of the blueprint are based on projects like MijnBureau, a self-hosted workplace suite composed of Nextcloud, Collabora, Element, and OpenProject.

MijnBureau developers are also working with France's La Suite and aligning their efforts with Germany's openDesk. The latter is noteworthy as it is being adopted by the International Criminal Court (ICC) due to US sanctions against ICC officials.

OpenDesk plays a pivotal role in the Mecklenburg-Vorpommern region of Germany and Switzerland, as reported earlier this month. In the Netherlands, the project has gained traction with eight municipalities participating in trials, although this represents a small fraction of the country's hundreds of municipalities. The project's source code is published through the BZK's government-hosted Forgejo instance, with additional repositories available on Codeberg for external contributors.

The project's choice of NixOS as the client operating system has been driven by its unique features, such as an open-source model, declarative configuration, and reproducible deployments. NixOS, founded by Dutch developers Eelco Dolstra and Armijn Hemel, is not controlled by a commercial vendor, making it an attractive option for managing large fleets of machines.

However, the Nix community has faced controversy in the past, including a 2023 incident where US autonomous weapons vendor Anduril was removed from NixOS sponsorship due to concerns raised by contributors. This controversy has led to a broader debate over project governance and the potential issues that can arise from restricting certain users.

Nonetheless, government interest in FOSS initiatives brings financial support and momentum, driving innovation and collaboration within the free software ecosystem.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at theregister.com →

More in Tech

Detect a website's tech stack in bulk with Python (a Wappalyzer-style lookup)

I built this actor; it's a paid tool on Apify with a free trial credit. "What is this site built with?" is easy to answer for one site with a browser extension.

  • Website Tech Stack Detector tool detects tech stacks in bulk using Python
  • Tool performs HTTP requests, DNS lookups, TLS handshakes for analysis
  • Output JSON includes tech stack details with confidence scores and evidence

MCP Transports That Still Matter: stdio vs Streamable HTTP (and Why SSE Is a Trap)

Attributed Chinese → English compile (not original authorship) Original title: MCP Server 开发入门:手把手写一个能跑的 Server,三种协议怎么选 Author: 晚安code URL: https://juejin.cn/post/7673880140422955046 Date: 2026-08-15…

  • MCP protocol separates model interface from byte movement
  • Avoid deprecated Streamable HTTP Server-Sent Events (SSE)
  • Stdio default for local hosts, Streamable HTTP for remote deployments

I stopped logging in every run and my automation stopped getting flagged

Fresh logins are what get you flagged. Reusing a saved session is what keeps the bot alive. I found this out after 41 accounts: the ones I re-logged into every run died first.

  • Persisting sessions reduces failure rate from 1 in 4 to 1 in 30 runs
  • Capture and reuse session after manual login until it expires
  • Maintain session vitality with light touch requests, not full re-logins

More from Monday 28 September →