The Nitrux distribution has taken a definitive turn with the official announcement of its Workspace Environment. After months of hints and partial development, the team behind this distribution has unveiled a new, fully modular desktop stack built on Hyprland, QML, and the MauiKit graphical environment.
Far from trying to compete with giants like KDE Plasma or GNOME, Nitrux seeks to establish a new intermediate standard: a system that offers the aesthetic cohesion of a complete environment, while maintaining the lightness and process separation of a traditional window manager.
This approach consolidates tools that the distribution had recently been developing , such as QMLGreet and NudgeOSD, and brings the old Maui Shell project to a close. The new architecture divides the desktop into independent and highly specialized components , following the Unix philosophy of "do one thing and do it well."
Valenz and Marina: The Independent Bar and Dock
This new environment relies on two complementary tools developed with QML, MauiKit and LayerShell-Qt:
- The first is Valenz: a top bar of the system (Workspace bar) designed exclusively for this function. Valenz It manages navigation between workspaces, multimedia controls, notifications, and the system tray. integrating critical indicators such as network, Bluetooth, volume, battery and night light, plus widgets for weather and system resources.
Its design rejects GTK and CSS-based interfaces, opting instead for native QML integration that guarantees flawless performance on the Wayland compositor. - Complementing the top bar is Marina: the new application dock that definitively replaces Crystal Dock. The developers rejected the latter because it relied on traditional Qt widgets, which broke the visual consistency of the environment. Marina integrates directly with the Hyprland compositor via events, allowing it to track and group open windows across multiple screens.
In addition, it supports automatic discovery of XDG applications, drag-and-drop reordering, horizontal scrolling, and visual notifications (badges) for unread messages, all under a unified interface free of configuration overload.

Workspace Settings and Desklock: Configuration and Security
One of the most important steps in Nitrux has been the creation of Workspace Settings . For a long time, the distribution relied on KDE's "System Preferences" to manage settings, an application tied to technologies that Nitrux no longer uses , such as KWin, SDDM, and systemd.

Workspace Settings is born as the new native control panel , managing everything from networks, Bluetooth, audio and user accounts, to the visual appearance of MauiKit and the specific settings of Valenz and Marina, ensuring that the administrative tools share the same visual language as the rest of the desktop.

In the session security section, Nitrux introduces Desklock, a native Wayland screen blocker that replaces Hyprlock. The decision to replace Hyprlock was made due to visual integration issues and persistent state failures after system suspension. Built on the QMLGreet codebase, Desklock offers direct authentication via PAM, integrated media controls (MPRIS), real-time resource monitoring, and multi-screen support, resulting in a secure, stable, and visually consistent user lifecycle with the rest of the MauiKit stack.
The Philosophy of the Five Layers and the End of Maui Shell

Nitrux has defined a five-layer model that explains exactly what a "Workspace Environment" is. In this scheme, the window manager (Layer 1, occupied by Hyprland) is solely responsible for rendering, while the static components (Layer 2) and the interactive visual environment (Layer 3, comprised of Valenz and Marina) operate independently. The Workspace Environment (Layer 4) integrates these graphical interfaces with essential utilities such as the file and settings manager, completely separating the processes from the graphics server. This prevents the massive crashes typical of monolithic Desktop Environments (Layer 5), where if the compositor fails, all applications close.
The launch of this modular ecosystem marks the final demise of Maui Shell, whose code has been archived. The Nitrux developers openly acknowledge that this restructuring (along with recent decisions such as removing support for virtual machine installation) could be overwhelming for some users.
However, they argue that these changes reflect the true identity of the distribution: a highly specific system, focused on developers and advanced users who value a lightweight, modular and deliberately curated architecture under the premise that "Nitrux is not for everyone."
Finally, if you are interested in learning more, you can find the details at the following link.