Nizho Documentation

Nizho, documented as it actually is.

This is a Developer Preview. These pages describe what runs today, what we are still validating, and what does not exist yet. Where a claim cannot be demonstrated, it is labelled rather than softened.

Configured Experimental Not yet

What is Nizho?

Nizho is an independent Linux desktop built on the Fedora bootc immutable image foundation. System image files are read-only at runtime. Updates are staged atomically and a retained deployment can be selected for rollback; this does not guarantee a successful boot or restore personal files. On top of that foundation it adds two system services of its own, nizhod for privacy enforcement and nizho-pulse for reliability monitoring, and ships a KDE Plasma desktop.

The premise is narrow on purpose. Privacy settings that a careful user would configure by hand are applied by default and re-checked while the system runs. The system can describe its own state, and it can be returned to a known-good one.

Why not just Fedora KDE?

Nizho
= proven Linux foundation
+ opinionated privacy enforcement
+ reliability layer
+ recoverable system
+ Nizho-specific desktop experience
+ transparent verification

Nizho packages privacy defaults and periodic checks with a desktop status surface. Settings can fail or conflict with local configuration; the project records these limits and tests each image.

What Nizho is not

  • It is not anonymity software. It does not route your traffic, and it cannot make you untrackable.
  • It is not a hardened security distribution or a replacement for threat-model-specific tooling.
  • It is not production ready. The graphical installer is VM-tested only and not published, and there is no hardware compatibility guarantee.
  • It is not a Linux fork. The kernel, drivers and desktop come from upstream.

Getting started

There is no installer ISO to download yet; one can be built from source with scripts/make-iso.sh. Three routes work today. Start with the virtual machine unless you are testing hardware support on purpose.

Run in a VM Recommended

QEMU/KVM with 4 GB of RAM and 40 GB of disk. Use only a disposable image file and no physical disk passthrough. Test rollback and personal-data preservation inside that guest.

qemu-system-x86_64 \
  -enable-kvm -m 4096 -smp 4 \
  -bios /usr/share/OVMF/OVMF_CODE.fd \
  -drive file=nizho-preview.qcow2,if=virtio

Boot from USB Preview testing

For development testing only. Real-hardware testing has begun, but the set of validated machines is small. Wi-Fi firmware, discrete GPUs, suspend/resume and display scaling are all known to vary. Assume you may need a wired connection and a second machine to read logs.

sudo dd if=nizho-preview.raw of=/dev/sdX \
  bs=4M status=progress conv=fsync &&
  sudo sgdisk -e /dev/sdX &&
  sudo sgdisk -v /dev/sdX && sync

Select only a disposable external test stick by model, serial and size; unmount its partitions first. Never select the internal Linux/Windows disk. dd erases the whole selected stick. sgdisk -e moves the backup GPT to its physical end when the image is smaller; stop if writing or verification fails.

Build from source Contributors

The image is a container build. The build recipe and resulting image can be inspected; building locally also lets you test source changes.

git clone https://github.com/nizho-os/nizho
cd nizho
podman build -t nizho:dev .
bootc-image-builder --type qcow2 nizho:dev

First run

A graphical first-run setup is being developed and validated. In the current preview, expect to confirm some settings from a terminal. nizhod attempts to apply privacy settings during startup; check its current status for failures.

What we prove, and what we don’t

Configured means a checked setting is in place, not that you are protected. These rows describe expected mechanisms, not live checks of your machine. Missing or stale observations remain unknown; every candidate needs fresh image tests.

MechanismWhat it does, and what it doesn’tState

Nizho reduces what your local machine leaks by default. It does not make you anonymous, untrackable, or immune to attack.

How Nizho works

Seven layers. The lower five are upstream Linux infrastructure; Nizho owns the two in the middle and the experience above them.

You
 ↓
Nizho Desktop            KDE Plasma session
 ↓
Applications + Sandbox   Firefox · bubblewrap
 ↓
nizhod + nizho-pulse     the Nizho layer
 ↓
Fedora bootc + composefs read-only root
 ↓
Linux kernel             upstream Fedora
 ↓
Hardware                 x86_64 · UEFI
The homepage shows what each layer does for you.

nizhod, the privacy service

A system service that applies a fixed privacy state at boot and re-checks it while the machine runs. If something resets a setting, nizhod puts it back and records that it did.

Its state can be read from the system bus. This is the output from a Nizho test image in a VM on 11 November 2026:

$ busctl get-property org.nizho.nizhod /org/nizho/nizhod \
    org.nizho.nizhod DnsStatus Firewall BrowserSandbox
s "Encrypted"
b true
s "Persistent"

What this does not do: it does not hide your IP address from sites you visit, and DNS-over-TLS moves your resolution to Quad9 rather than making it unobservable.

nizho-pulse, the reliability layer

Local reliability monitoring and prediction. Currently focused on telemetry, detection, prediction and verification; recovery actions remain constrained and experimental. Nothing is sent off the device.

  • Telemetry: disk, memory, thermals, service failures, journal patterns, collected locally.
  • Detection: degradation surfaced with the signal that triggered it.
  • Prediction: early warning ahead of failure. Thresholds are still being calibrated.
  • Verification: confirming the system is in the state it reports.
  • Autonomous recovery: not shipped. nizho-pulse recommends; you decide.

Updates and rollback

The OS is delivered as a container-native image. An update fetches a new image and stages it for the next boot; updates never restart the computer on their own. After you restart into it, greenboot runs start-up checks. If they fail, or the new version fails before the desktop starts (a kernel panic or an early-boot error), the computer restarts, and after three failed boots it goes back to the previous version by itself. Nizho adds two fixes to greenboot 0.16.4: upstream never recorded which version to go back to, because the unit that records it was not stopped at shutdown; and GRUB’s boot counter is armed as soon as an update is staged, so an early failure restarts and falls back instead of waiting at a recovery screen.

Tested in a VM on 11 October 2026, on an ArkaOS build (the project Nizho began as): a deliberately broken update went back after three failed boots with nobody touching the computer, an update that could not start went back within about 30 seconds, a healthy update stayed installed across restarts, an update that failed to apply at shutdown left the current version in place instead of rolling it back, bootc rollback still went back by hand, and the test files in /home and /var were unchanged. This was tested in a VM, not on real hardware, and these cases have not yet been repeated on a Nizho image.

$ bootc upgrade          # stage the next image
$ systemctl reboot       # boot into it
$ bootc rollback         # go back to the previous version at the next boot

Project status

Nizho is in Developer Preview. It is suitable for a VM, for reading, and for contributing. It is not suitable as your only machine.

Questions