Skip to content
saphiralinux

Direction

Roadmap

What is finished, what is being built, what comes next, and what Saphira deliberately has no intention of becoming.

  • Earlybird Beta image and public repository

    A bootable Saphira image, 481 packages, and a public APK repository that real systems can install from.

    Complete

  • GCC 16.1.0 toolchain migration

    Rebuilding the native compiler stack around GCC 16.1.0, with broader language support and musl-specific compatibility work.

    In progress

  • Full clean reproducibility rebuild

    Once the new native toolchain is proven, rebuild the distribution from the beginning and verify that every stage is reproducible.

    Planned

  • Package-quality fixes from real use

    Dependencies, package splits, runtime libraries, service scripts and configuration corrected as real workloads expose problems.

    In progress

  • Expanded compiler and language support

    C, C++, Fortran, Ada, Go and other GCC-supported languages are being brought into the native toolchain rather than treated as optional afterthoughts.

    In progress

  • Package validation

    More package-level smoke testing, runtime checks and dependency validation before packages are considered complete.

    In progress

  • Installation tooling

    A guided TUI installation path for installing Saphira onto a machine without requiring users to manually import a prepared disk image.

    In progress

  • Virtualisation compatibility

    Formal testing beyond KVM/QEMU, including other common hypervisors where the required virtual hardware interfaces are available.

    Planned

  • Physical hardware support

    Saphira is intended to run on physical x86-64-v3 systems as well as virtual machines. Hardware installation, storage and network discovery will be expanded as testing grows.

    Planned

  • Saphira administration tools

    Small inspectable tools for web, DNS, mail and other server administration without introducing a proprietary control plane.

    In progress

  • Documentation

    Installation, administration, packaging, networking and recovery documentation written for people who actually operate servers.

    In progress

  • Package catalogue expansion

    More useful server software, developer tooling and infrastructure packages added as they are requested and can be maintained properly.

    Planned

Deliberate boundaries

What Saphira will not become

A small server distribution stays useful by knowing what it is not trying to be. These are deliberate project boundaries, not limitations placed on what users may build themselves.

  • Desktop environment

    Saphira is a server operating system. There are no plans to turn it into a desktop distribution.

  • X11, Wayland and Plasma

    They are not part of the Saphira base system or roadmap. Nothing prevents somebody from packaging them independently, though the project itself will remain server-first.

  • NVIDIA proprietary drivers

    Saphira will not package NVIDIA's proprietary driver stack.

  • NVIDIA Open Kernel Modules

    Support depends on NVIDIA providing a practical musl-compatible userspace and driver path. Until that exists, this is not something Saphira can reasonably solve on NVIDIA's behalf.

  • Graphical installer

    Installation tooling is terminal based. A TUI path for installing onto target disks is planned.

  • Mandatory hosted control plane

    Saphira will not require a SaaS dashboard or remote service in order to administer the machine. Configuration remains local, inspectable and owned by the operator.