Open code. Strong copyleft. Zero lock-in.

BalonixOS alongside Jev and balo-immune v2 uses GPL-3.0 so system improvements stay free. Separate standalone tools on subdomains use MPL-2.0.

Always reversible

Any mood change, setting, or system update rolls back cleanly whenever you need it.

Completely local

Semantic file search, instant translation, and smart helpers stay right on your machine.

Calm focus

Side struts, natural depth, and colors drawn from your wallpaper keep your workspace effortlessly clear.

100 % open

No mandatory accounts, zero trackers, zero ads — a workspace that truly belongs to you.

01

GPL-3.0 Core OS

02

MPL-2.0 Standalone Repos

03

Boot-time Rollbacks

GPL-3.0 protects the full operating system

Distributed forks of BalonixOS or its core engines must share code improvements openly under GPL-3.0 — aligning cleanly with Niri, Astal, Matugen, and Lanzaboote.

MPL-2.0 for separate standalone repos

SpatialWire, ClickClick, and Niri Canvas live in dedicated repositories and subdomains under MPL-2.0 — keeping modified files open while remaining easy to adopt.

Zero telemetry in OS and web

No accounts, no ads, no third-party CDNs — both across BalonixOS and right here on balonix.org.

Why combine GPL-3.0 for the OS with MPL-2.0 for standalone repos?

Strong copyleft prevents closed-source rebranding of the desktop OS while keeping independent libraries and daemons straightforward to reuse.

How are personal settings separated from the public OS?

Universal OS code lives in balonixOS (GPL-3.0), while personal hardware, keys, and preferences stay in a separate private host flake.

Where does development happen?

Actively developed in public as an open-source Private Alpha on GitHub.