Native device installation
Where apps execute Applications run directly on supported hardware running Wasabe OS.
What you install The Wasabe OS image, through its installer — once that installer is qualified.
We’re building Wasabe OS: a Fedora-based operating system with its own desktop, real applications and an assistant designed to work across the tools you have approved. Use it on supported hardware, or access the same OS through your browser with Wasabe Runtime on your own computer.
Where apps execute Applications run directly on supported hardware running Wasabe OS.
What you install The Wasabe OS image, through its installer — once that installer is qualified.
Where apps execute Applications run inside a persistent local Linux VM.
What you install A native Wasabe Runtime for the host platform — once a supported build is available.
Native installation remains part of the product direction. Our first acceptance target is the local Apple Silicon VM, followed immediately by browser access through the Runtime. Broader host and hardware support follows qualification. There is no installer or Runtime download on this site yet.
Wasabe Runtime is the installed host software that runs the persistent Linux VM on an existing Windows, macOS or Linux computer. Wasabe Web Runtime is the shared web engine inside the OS that executes Wasabe apps. They are different components that have historically shared a name.
Wasabe Runtime provisions the OS image, manages the VM and persistent storage, and pairs with the browser.
The browser displays and controls the actual Linux desktop through an authenticated local connection. It is not a separate web desktop product.
The Runtime’s lifecycle policy decides whether the VM continues, idles or suspends. Applications and files live on persistent storage.
Same-machine desktop video stays local. Optional cloud services can later cover identity, AI, updates, distribution, sync and backup. Remote access is a separate, permissioned future capability.
Existing Windows / macOS / Linux computer
Browser: setup, connection, display and input
↕ authenticated local connection
Wasabe Runtime (host): VM, storage and approved host integrations
↕
Persistent Wasabe OS VM
Fedora Linux → Wasabe desktop → native Wasabe and Linux apps
Supported device running Wasabe OS directly
Fedora Linux → the same Wasabe desktop and application modelThe base is Fedora Linux, with normal Linux drivers, system services and package infrastructure. Wasabe supplies its own desktop and window manager. GNOME is not the desktop underneath the Wasabe interface. React renders the shell; Rust owns native window management, placement, focus, input, workspaces, compositing and permission-controlled system operations.
Kernel, drivers, package ecosystem and Linux services.
Native Wayland/XWayland windows, display, input and workspaces.
The existing React desktop and system presentation on OS-owned surfaces.
The shared, system-managed web engine inside the OS — not the host Runtime you install on macOS, Windows or Linux.
Typed, identity-bound, permission-controlled native operations.
Application packaging, lifecycle, integration and developer contracts.
A shared assistant with scoped tools and approved app actions.
Native liquid glass is in development as a shared OS material for window chrome and the dock. We are not presenting a mockup of it as a shipped or benchmarked effect.
Existing Wasabe applications are being converted into real native windows while preserving their content, features and logic. A catalog tile is not a release-ready application. Normal Linux applications coexist through the same desktop — Fedora packages, RPM/DNF and Flatpak, with Wayland and XWayland. We do not claim every Linux app works.
Explore the application catalogFedora-based OS with the retained React desktop and Rust window authority. Working development VM; not a completed OS release.
Browser access through a distributable host Runtime, after local-VM acceptance. There is no downloadable completed Runtime today.
Native hardware installer, broader host support, and a published compatibility matrix. ARM64 and x86-64 need their own builds.
There is no qualified download yet. Leave your email and we will write when a supported Runtime or installer is ready to try.