(EDIT: I used AI to build this!)
Hello everyone!
I’ve been using Qubes for a while but haven’t posted here before (maybe years ago?). I love the QubesOS-Xen-VM isolation architecture.
I’ve been experimenting with building my own OS inspired by Qubes, it’s called AirlockOS.
I’ve managed to reuse a lot of the Qubes management stack, including qrexec and its policy model. The setup is still: dom0, sys-net, sys-firewall, etc.
My high-level goals were to:
-
reduce development costs (easier recovery from mistakes, and if it builds it should work, etc.)
-
reduce troubleshooting and configuration costs for users
So I’ve gone with these features:
-
NixOS by default in every VM (dom0, …).
-
Nix full-system rollback and generations.
-
Global shared Nix store with per-VM closures so each VM’s software surface is minimal (using EROFS).
-
Rust everywhere. AirlockOS apps/services are written in Rust. Instead of writing Nixlang for system integration, I created Rusix library (Rust compiled down to nixlang) so that I could configure everything in Rust too. Then I can share types between the configuration code and the app code. Trying to use strong opaque types and Verus as much as I can.
-
Latest GNOME in sys-gui (Qubes GUI transport) with workspaces as VM boundaries.
Experimental fun:
-
Small Hermit VMs (code caps resource allocation so sys-clipboard 16 MiB RAM??, etc.)
-
Isolated, confined local AI agent assistant VM that can suggest system changes to sys-ctrl, which handles user review and approval/rejection.
The whole thing is super experimental! It runs off USB right now.
Anyway, it’s been a lot of fun so far. I hope to make this my daily driver soon so that I can keep working on it as part of my routine.
There’s a short desktop demo (https://youtu.be/h528TDh-PLU), some architecture documentation ( Overview | Airlock OS ), and the source ( GitHub - airlockos-org/airlockos: A Xen-based desktop OS built with Rust, Qubes, and Nix. · GitHub ).
(EDIT: I used AI to build this!)