Open Source

Software components & licenses

LeafKVM is built from several software components with well-defined open-source licenses:

• Linux kernel & build framework

  • Modified Linux kernel and build scripts.
  • License: GPLv2.

• LeafKVM backend (Rust)

  • Handles control logic, streaming orchestration, and device management.
  • License: GPLv2.

• On-device GUI (Slint)

  • The touchscreen UI that runs directly on LeafKVM.
  • License: GPLv3.

• Modified RustDesk

  • LeafKVM integrates modified RustDesk components to provide remote access.
  • License: AGPL-3.0.

• Web frontend

  • Browser-based UI for controlling LeafKVM, adapted from the JetKVM frontend.
  • License: GPLv2.

• Vendor binaries

  • Rockchip video blobs, required for video encoders/decoders on the SoC.
  • Delivered as-is, only where redistribution is allowed.
  • Kept separate from open build recipes.

Hardware: CERN-OHL-W

LeafKVM’s hardware schematics will be released as PDFs under the CERN-OHL-W license:

• You can:
  • Study how the hardware works.
  • Repair or modify your own device.
  • Use the design as a base for compatible, open derivatives (under CERN-OHL-W terms).
• We believe this level of openness is rare in the KVM market and want to set a higher baseline.

Layouts, project files, and mechanical models may be provided where licenses and toolchains allow.

Build system & CI

We aim to provide a fully reproducible firmware build flow:

• Buildroot-based top-level project.
• Separate layers for:
  • Kernel patches.
  • LeafKVM-specific services and configuration.
  • Web frontend and GUI assets.
• Public CI (e.g. GitHub Actions) will:
  • Build firmware images from source.
  • Run basic automated checks.
  • Publish reproducible artifacts.

This allows you to:

• Verify that released images can be reproduced from the published sources.
• Fork the build recipes and adapt LeafKVM to your use cases.

When will sources be available?

All code and design files will be released:

• After the campaign is funded, and
• Before products are shipped for fulfillment.

This includes:

• Firmware and software repositories.
• Schematics (PDF) and, where possible, layout and mechanical files.
• Full build instructions and CI configuration.
• A public index of files at https://kvm.rs.

How to participate

Once repositories are public, you can:

• Discuss & give feedback

  • Join the official discussion channels (links will be published on kvm.rs).
  • Share your use cases, bug reports, and feature requests.

• Contribute code

  • Submit pull requests for:
    • Bug fixes and optimizations.
    • New firmware features or UI improvements.
    • Documentation and localization.

• Extend the platform

  • Prototype your own firmware variants using the published build system.
  • Extend the GUI or backend using documented APIs.
  • Experiment with custom integrations (home automation, lab control, robotics fleets, etc.).

We aim to keep the codebase approachable even for people with limited embedded experience, with clear build instructions and a focus on transparent, reproducible development.