Built inside BalonixOS. Woven into the OS core.

Jev, balo_engine, and balo-immune v2 live directly inside the main repository as core BalonixOS engines under GPL-3.0. Separate tools live on subdomains under MPL-2.0.

Integrated inside the BalonixOS Flake

# Integral parts of BalonixOS (GPL-3.0)
system/llm-agent/orchestrator   # Rust Jev harness + balo-immune binary
system/llm-agent/balo_engine    # Typed OS talents & EmbeddingGemma-2
system/security/immune.nix      # fanotify + Landlock + Idle CVE gatekeeper
01

GPL-3.0 Core OS

02

Jev & balo-immune v2

03

Standalone Repos under MPL-2.0

Four cleanly isolated OS layers

Secrets, immutable platform, system engines, and Wayland experience remain isolated while shipping as one unified distribution.

Memory-safe Rust at the core

Orchestration and synchronous fanotify vault guarding share one clean Rust workspace — keeping vault defense under 15 MB RSS.

Clean split from standalone subdomains (MPL-2.0)

Independent projects — SpatialWire, ClickClick, and Niri Canvas — live on their own subdomains and public repositories under MPL-2.0.

Why are Jev and balo-immune licensed under GPL-3.0 instead of MPL-2.0?

Both are tightly integrated inside BalonixOS alongside a GPL-3.0 desktop stack (Niri, Astal, Matugen, Lanzaboote), ensuring derived OS forks remain open.

Where do SpatialWire, ClickClick, and Niri Canvas live?

Links below and in the footer point directly to spatialwire.balonix.org, clickclick.balonix.org, and niricanvas.balonix.org under MPL-2.0.

How light are the core engines at idle?

balo-immune stays under 15 MB RSS and local AI holds 0 MB VRAM when idle.