Lyra OS Unveiled

Lyra OS Unveiled

In this article

• Hello, Lyra OS

• Under the Hood

• Your First Steps

Every so often, a Linux distribution turns up that feels less like a product and more like a personal conversation. Lyra OS is one of those. It is a Brazilian, openSUSE Leap-based system that comes in two flavours, a GNOME desktop and a headless server, both tied together by a home-grown control centre called Vega. It also comes with a refreshing amount of candour about still being a work in progress. Pour yourself a cuppa and let's take a proper look.

Hello, Lyra OS

Lyra OS is an independent personal project by Rodrigo Brito, created to make the Linux desktop feel more coherent, welcoming and dependable. Its motto, "Harmony. Performance. Freedom." (Harmonia. Performance. Liberdade. in the original Portuguese), neatly captures the ambition: a system that balances power, stability and liberty, on the desktop and in the server room alike.

The name comes from the constellation Lyra, a small pattern in the night sky with a memorable identity. The astronomical theme runs right through the project. Vega, the brightest star in Lyra, lends its name to the control centre. The current generation is called Odisseia, Portuguese for "Odyssey", while the server edition goes by Delos. There is a human story behind it too. Brito traces the spark of the idea back to 2005, when he attended a talk by Jon "maddog" Hall, whose passionate defence of free software changed how he thought about technology, community and freedom. Lyra OS arrived many years later, and its website thanks Hall for lighting that star.

Lyra stands on openSUSE Leap, which the project presents as a solid alternative in a landscape dominated by Arch, Ubuntu and Fedora bases. Leap offers a predictable release cycle and a reputation for steadiness, which suits a system that wants to stay calm without giving up performance.

The version numbering is worth understanding, because it has just changed. A Lyra version now follows the format MAJOR.MINOR[.PATCH], where MAJOR.MINOR is simply the Leap release underneath and PATCH is a maintenance revision made by Lyra itself. So Lyra OS 16.1 is built on Leap 16.1, and that line is currently in development. Until October 2026, however, the cycle was numbered 1.1, and images published under that number remain valid as a historical record. That is why the current downloads still read 1.1, while the documentation talks about 16.1.

The usual pre-release labels apply, and the documentation spells them out. An Alpha is a development candidate for testing integration and finding problems. A Beta is a validation and stabilisation stage that still comes before the final release. An RC, or release candidate, is a contender for release that must still satisfy the project's quality criteria. The desktop and server editions follow independent cycles, and moving up a stage depends on testing and the resolution of blockers rather than on a calendar date. Support is community-based, and the project makes no contractual promises or end-of-support dates without a formal policy.

The Desktop edition is built around GNOME, and for the 1.1 cycle GNOME is the only release target. KDE Plasma and XFCE flavours exist as experimental repositories, but they carry no commitment to a release or to feature parity. The Server edition is the same Leap 16.1 foundation without any graphical environment or Lyra desktop components, aimed at administering services and infrastructure.

Both editions are honest about their status. The project repositories carry a prominent notice that the ISO images should not be treated as final until the full cycle of building, installing and booting the installed system has been validated again after the latest fixes.

A small housekeeping note for fellow fact-checkers: the project's moving parts do not always update in lockstep. The website and SourceForge list Desktop Alpha 8 and Server Beta 1.1 as the current downloads, yet the desktop repository's README still refers to Alpha 7, and the server README mentions a 16.1 "Delos" RC 1. In a young, fast-moving project, that sort of lag is entirely normal. The website and the per-release notes are the best guide to what you actually download.

Under the Hood

Let's start with the desktop, where openSUSE Leap 16.1 meets a clean GNOME session wearing Lyra's own theme, icons and wallpapers, designed for GNOME 48 and later. Out of the box you get Firefox, VLC, Flatpak with Flathub enabled, and LinuxToys, a friendly graphical collection of tools for everyday tasks and tweaks.

For full-featured FFmpeg and VLC builds, the system enables only the Packman Essentials repository rather than the whole of Packman, and the official Leap repositories take priority over Lyra's own on an installed system.

A few design decisions deserve applause:

• A native installer. The Lyra Installer is written in Rust with Tauri, rendering its HTML and CSS through the system's WebKitGTK. During installation you choose between ZRAM with Zstandard compression, a swap partition on disk, or no virtual memory at all.

• A safety net by default. The system uses Btrfs with Snapper, taking snapshots automatically around Zypper operations, and you can recover from a snapshot straight from the GRUB menu. Lyra Upgrade, a Rust-based engine, handles recoverable updates, and Secure Boot is supported through openSUSE's shim.
  

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

• Privacy that means it. There is no automatic telemetry. A tool called lyra-report gathers diagnostics only when you ask, saves a local file with restricted permissions, anonymises what it collects, shows you the sanitised content before you confirm and never sends it anywhere.

• Three languages. The installer and Lyra's own interfaces cover English (United States), Portuguese (Brazil) and Spanish (Spain), with English as the default and the fallback.

• A tidy welcome. Lyra Welcome appears at each user's first graphical login, and Beam, a pure-Rust RDP client built on IronRDP, is there for reaching Windows machines.

The most distinctive ingredient is Sheliak, a suite of six independent GNOME extensions: Lyra Dock, Panel, Menus, Search, Animations and Desktop Icons. Each can be switched on or off separately, and together they power six desktop profiles. Lyra is the signature layout. Ubuntu extends the dock down the left-hand side and tucks the top-bar menus away. GNOME Vanilla leaves the shell as upstream intended. Lyra Classic and Lyra Central use a fixed bottom taskbar, with applications aligned left or centred respectively, and an L button or the Super key opens the matching menu. Lyra Floating offers a centred floating dock with icon magnification. Switching profiles restores the preferences you had previously, so experimenting costs you nothing.

One caveat worth knowing: NVIDIA support is optional. The plan is a single GNOME ISO without the NVIDIA stack pre-installed, with the official driver offered afterwards through Vega, using a SUSE-signed module and a mandatory recovery snapshot. The project is candid that the ISO and this optional flow still need qualification.

Now for the star of the show. If Lyra has a signature feature, it is Vega. The project describes it as a native control centre built exclusively for openSUSE, bringing software, hardware, kernel, network, backup, user and service administration into one interface that complements GNOME Settings rather than replacing it. It spares you from juggling zypper, nmcli, systemctl and hand-edited configuration files.

Under the surface, Vega is a family of cooperating parts:

• vega-gtk is the graphical interface, written in Rust with GTK4 and libadwaita.

• vega-cli is the terminal interface, built with Bash and dialog, and aimed mainly at headless servers.

• vega-web is an HTTPS panel for LAN-only administration, written in Rust with axum and including an embedded administrative terminal.

• vegad is a daemon written in Go that carries out authorised system operations.

• lyra-vega-dbus provides the typed D-Bus client and the public contract shared by the Rust front ends.

The design is thoughtfully security-minded. Every interface talks to the same privileged daemon over D-Bus. The daemon is activated on demand and quietly exits after two minutes without activity. Read-only queries need no authentication, and anything that changes the system is guarded by granular polkit rules, so the graphical app never runs as root.

What can you do with it? Vega's dashboard offers a health overview and shortcuts. It manages Zypper packages, Flatpak applications, updates and repositories. It supports optional snapshots with Snapper or Timeshift and backups with Restic. It also handles hardware inventory, the kernel and bootloader, storage, date, time and locale, networking with Wi-Fi, Bluetooth, firewall, VPN and proxy, users, services, logs and live process monitoring. Personalisation covers wallpapers and screen-lock preferences, and there is even an optional multi-provider AI assistant. That assistant stores its keys in the session's Secret Service and presents any system-changing action as a proposal before anything runs. Where a feature depends on an optional program that is missing, the page simply shows it as unavailable, without breaking the rest.

Vega's interface speaks Portuguese (Brazil), English and Spanish, or follows your system language. Be aware that it targets openSUSE Leap 16 and Tumbleweed only, and other distributions are not supported.

Then there is the server, a lean, console-driven edition for people who prefer a prompt to a desktop. You administer it through the console, the Vega CLI or Vega Web, which listens on port 9090/tcp. Typing vega in an interactive terminal, locally or over SSH, opens the menus, and authentication is requested for each privileged action.

The installer is an interactive shell script with a dialog-based text interface, and the project is refreshingly plain about its limits in the current series. Installation is UEFI-only onto a whole disk, with a GPT layout, an EFI partition and an ext4 root. RAID, LVM, Btrfs, Snapper, legacy BIOS and unattended installation are outside the documented flow. Networking uses DHCP, and a static address is something you set up afterwards. The project's initial firewall policy opens only SSH and Vega Web. Secure Boot is supported through the same openSUSE shim as on the desktop, and an optional NVIDIA installation through Vega CLI or Web comes with an offline recovery path on ext4.

Because there is no Snapper rollback and no automatic downgrade, the documentation sensibly urges you to plan backups of both data and service configuration.

The supply chain is neatly divided. GitHub validates sources and contracts, the Open Build Service compiles and publishes the RPM packages, KIWI assembles the ISO locally, and SourceForge distributes the approved images. The project's own code and documentation are released under the GNU General Public License, version 3, while third-party material keeps its original licences.

Your First Steps

The published requirements are provisional and subject to validation, but they give a good picture of what to expect. For the Desktop, the minimum is an x86_64 processor with two cores, 4 GiB of RAM, 24 GiB of storage and a 1024 × 768 display. The recommendation is four cores, 8 GiB of RAM, an SSD of 40 GiB or more and a Full HD screen. The Server is far less demanding. It needs one core, 2 GiB of RAM, 8 GiB of storage and Ethernet with DHCP at minimum, while two or more cores, 4 GiB of RAM or more, a 20 GiB SSD and Gigabit Ethernet are recommended.

The Desktop also calls for UEFI firmware, a USB stick for the installation media and an internet connection for updates. Secure Boot is supported, and the installation takes over the entire disk.

Head to the download section of the website, where the Desktop Alpha 8 and Server Beta 1.1 images are listed. They are hosted on SourceForge, and the Desktop ISO is listed at 2.8 GB. Download the checksum file from the same release folder and verify the image before you write it. On Linux, run sha256sum -c against the checksum file for your image and continue only if it reports OK. Do note that, according to its release notes, the Alpha 8 ISO has no detached GPG signature, so the checksum confirms integrity but not provenance.

Next, write the ISO to a USB stick with a disk-imaging tool. In GNOME Disks, choose the option to restore a disk image. Simply copying the ISO file onto the stick is not enough. Then boot from the UEFI entry for your media using your firmware's boot menu, whose key varies by manufacturer. In a virtual machine, attach the ISO as an optical drive and enable UEFI. This is a fine way to try Lyra without risking a real disk, so long as the virtual machine has a disk of its own.

Once the live session opens the Lyra Installer, you will be asked for your language, keyboard, region and account details. Then you choose the dedicated disk and review the summary, paying particular attention to the destination. Only confirm when you are certain, because a whole-disk installation erases the selected disk. Back up first, and keep the computer powered on until the process finishes. When prompted, restart and remove the installation media. The official guide is clear that it is not a recipe for dual-booting or manual partitioning.

The Alpha 8 release notes add useful context. This image supports fresh installations only, and the docs describe it as the last Alpha of the Desktop 16.1 line. Its focus was qualification in virtual machines, plus fixes to the installer and the dock.

The server installer runs in the console and walks you through language, keyboard, time zone, machine name and account details. After reviewing the chosen disk, you confirm and reboot into the installed system. 

Three read-only commands make a sensible first check: cat /etc/os-release to confirm the version, ip -brief address to see the address your network interface received, and systemctl --failed to spot any services that did not start. 

The documentation also advises confirming the effective state of the firewall and services before exposing anything remotely, and notes that Vega Web is meant for local-network use, with its own guide to HTTPS and authentication. Log in with the account you created, check that the network is working and open Vega. 

The documentation explains the difference between updating the system and migrating to a new version, and a troubleshooting guide helps you prepare a useful report if something misbehaves. 

The guides are available in Portuguese, English, Spanish and Italian, and anyone can suggest edits. If you prefer to watch, the website also links video walkthroughs of earlier Desktop and Server alphas, which the project notes are a visual reference only. An official book by Rodrigo Brito, Lyra OS: From first contact to mastering the system, is in development and planned in Portuguese and English.

In closing, Lyra OS is a young and openly unfinished project, but a thoughtful one. A steady Leap foundation, a well-considered control centre, careful privacy choices and a plain-spoken approach to its own limits make it well worth watching, especially for anyone who likes a distribution with a clear point of view. If you are tempted, try it in a virtual machine first, and read the release notes for whichever image you choose.

Disclaimer: all product names, logos and trademarks mentioned belong to their respective owners and are used here for identification only. The Distrowrite Project strives for accuracy, but pre-release software changes quickly, so please check the official sources for the latest details. Please use open-source software responsibly and legally.

References:-

• Lyra OS official website

• Lyra OS download section

• Lyra OS documentation

• Versions and support

• Meet Vega

• Installing Lyra OS

• Lyra OS Server guide

• Lyra OS on GitHub

• lyraos-desktop repository

• lyraos-server repository

• Vega repository

• Lyra on SourceForge

↑ Back to top