GitHub

A local-first project in development

Ride your
own systems.

A local-first desktop virtual machine manager. Every system, one place, without an account or a cloud dependency.

See the roadmap Read the documentation

Wave VM is in development. No public download is available yet.

wWave VMWORKSPACEA
MACHINES / UBUNTU DEV

Ubuntu Dev

Running
CONSOLE PREVIEW● ● ●
ubuntu@wave-dev:~
$ ready when you are
ResourcesAssigned to this machine
⌘PROCESSORS4 cores
▤MEMORY8 GB
◫STORAGE64 GB
ⅡPause machine•••
Interface concept · Planned product direction
VIRTUAL MACHINES, WITHOUT THE FRICTION01 — A CLEARER WAY TO WORK

Current status

A real lifecycle. Not a finished VM manager.

The desktop shell, host diagnostics, machine definitions, QCOW2 disks, QEMU start and stop, QMP control, and a loopback noVNC console are implemented. Guest installation and networking are still ahead.

Current milestoneMilestone 2 is implemented.

Machines can be created, started, stopped, and opened in a genuine guest console. The code is public and inspectable.

See what is complete
Next milestoneInstallation media and networking

Planned, not started. The current build cannot install a guest operating system or configure guest networking.

Inspect the next phase
AvailabilityNo public download

There are no release artifacts or installers. Build from source to inspect the current lifecycle.

Build from source

Available now

Real machines. No mock controls.

The current build creates local machine definitions, QCOW2 disks, and real QEMU processes. A running machine can be opened in its actual guest console.

See all features
  • 01

    Virtual machine definitions

    Creates and persists local machine definitions with a validated name, x86_64 guest architecture, memory, virtual CPU count, and disk size. Definitions are stored in the schema-v2 configuration.

    Available now
  • 02

    Real QEMU process lifecycle

    Starts QEMU with the configured memory, virtual CPUs, and disk. KVM is used only when its probe succeeds; otherwise QEMU uses software emulation (TCG). Stop uses QMP with bounded process-termination fallbacks.

    Available now
  • 03

    Interactive guest console

    Displays the actual guest framebuffer through QEMU WebSocket VNC and the bundled noVNC 1.7.0 client. The listener is bound to 127.0.0.1, the WebSocket port is discovered through QMP, and a password is generated per run and kept in memory only.

    Available now

Roadmap

The path to a complete machine.

The foundation, host checks, VM lifecycle, and graphical console are implemented. Guest installation media, networking, and packaging are still ahead.

See the full roadmap
  1. 01

    Desktop foundation

    Establish a real desktop application with a trustworthy shell, local configuration, and a clear frontend boundary.

    Complete
  2. 02

    Host readiness and engine discovery

    Detect what the host can actually do before attempting any virtual machine operation.

    Complete
  3. 03

    VM definitions and disk lifecycle

    Turn a virtual machine into a validated local definition with explicit, protected storage.

    Complete
  4. 04

    QEMU launch and QMP lifecycle

    Start and supervise QEMU safely, then control supported lifecycle operations through QMP.

    Complete
  5. 05

    Graphical console

    Provide a genuine interactive graphical console for the running guest.

    Complete
  6. 06

    Guest installation media and networking

    Next milestone

    Make operating system installation and guest connectivity practical without weakening local control.

    Planned

Documentation

Understand what exists.

The documentation separates implemented behavior from planned work, with source evidence where it matters.

01

Getting Started

What the current build does, what it needs, and how to run it from source.

Read the section 02

Architecture

How the Tauri shell, Rust backend, QEMU lifecycle, QMP, and local storage fit together.

Read the section 03

Development

Set up the repository, run the checks, contribute, and report problems.

Read the section

Built in the open

Trust starts with
transparency.

WAVE VMPUBLIC SOURCE
01source available to inspect✓
02decisions documented with the code✓
03local control by design↗

Virtual machines can hold your work, tools, and important environments. You should be able to understand the software that manages them.

Wave VM is being developed in the open as a local-first project. The source is public under the MIT License, and third-party dependencies retain their own licenses.

See the project on GitHub

Every system, one place

Make room for
what’s next.

Wave VM is still taking shape. Follow the public work or read exactly what the current build can do.

Follow development Read the documentation