onyxOS
Active build
Private development

OnyxOS / Windows 11 target · One machine. Zero disguise.

The machine, reimagined.

Exact Windows 11 behavior. An Onyx-owned boot path. Native Linux workflows. One operating system built to run the software you already use—directly, without a virtual machine.

Native system Windows-compatible No virtual machine
Enter the system Live build 54%
ONYXBOOT / UEFI64

Boot path preview

Ready
00 / FIRMWARE Presence detected.

UEFI environment acquired. Preparing the measured OnyxBoot path.

Interactive concept · States describe the target path, not unverified completion.

The project, revealed 02 / ONE NATIVE SYSTEM

This is OnyxOS

Windows software.
Linux power.
One native OS.

OnyxOS is an independently developed operating system targeting direct compatibility with Windows applications and hardware, while making Linux tools and services first-class parts of the same desktop.

It is not a theme, a remote desktop, or one operating system hidden inside another. The project spans the boot path, kernel, system services, compatibility layers, desktop, and developer environment as one coherent platform.

01 / DIRECT

Windows compatibility

Run familiar applications directly against a native compatibility surface, with driver compatibility as a platform target.

Active development
02 / OWNED

Onyx-native core

One system owns startup, hardware, services, security boundaries, and the desktop experience from boot onward.

Verified foundations
03 / UNIFIED

Linux, without a VM

A planned native Linux environment will bring shells, toolchains, services, and graphical apps into the OnyxOS desktop.

Architecture phase

What the live number means: 54% measures the public-preview gates shown below—not total feature completion. Build, boot, services, graphical logon, secure input, and hardware discovery are verified; the desktop, broader compatibility, native startup, and Linux environment remain in development.

System architecture 03 / ONE MACHINE, ONE SYSTEM

No guest OS.
No remote session.
No artificial divide.

OnyxOS is designed as a single native platform. The Windows compatibility environment and the planned Linux environment meet at shared system services and one desktop instead of crossing a virtual-machine boundary.

BOOT / ACTIVE OnyxBoot Firmware to native startup
CORE / VERIFIED FOUNDATION OnyxOS kernel + executive Scheduling · memory · I/O · security · hardware
COMPATIBILITY / ACTIVE Windows application environment Native APIs · applications · driver target
LINE / ARCHITECTURE Native Linux environment Shells · packages · services · graphical apps
EXPERIENCE / IN DEVELOPMENT One OnyxOS desktop Shared files · windows · input · graphics · identity

NOW Boot, core services, logon, input, and hardware foundations are verified.

NEXT Authentication, desktop continuity, compatibility depth, and native startup.

LATER LINE becomes the first-class Linux environment inside the unified desktop.

LINE — Linux Integration and Native Environment 04 / NATIVE LINUX

A new execution personality

Linux stops being
a place you enter.

LINE is the planned native Linux environment for OnyxOS. Unmodified x86-64 Linux programs execute directly on the CPU as Onyx kernel processes, then share one scheduler, one security authority, one compositor, and one desktop with Windows applications.

No Linux kernel. No CPU emulator. No RDP. No nested desktop.

LINE CONSOLE / ONYXOS

OnyxOS › line shell

kain@onyx:~$ uname -a

Linux onyx-line x86_64 / native personality

kain@onyx:~$ sudo apt install kate

Dependencies verified · signed transaction ready

kain@onyx:~$ kate README.md

Kate opens as an ordinary OnyxOS window beside native Windows applications.

THE TARGET EXPERIENCE One command line.
One desktop.
Both ecosystems.
  • Native Bash, SSH, tmux, editors, and build tools
  • KDE, Qt, GTK, Electron, and Wayland applications
  • APT-compatible signed packages with complete dependencies
  • Shared files, networking, audio, input, printing, and graphics
01 / EXECUTION

Direct Linux ELF

A per-process Linux x86-64 personality routes native syscalls into Onyx kernel primitives—without a guest kernel or general syscall proxy.

Foundation roadmap
02 / CONSOLE

Native terminal

line shell opens an Onyx terminal with real PTYs, job control, signals, UTF-8, Bash, SSH, tmux, and developer tooling.

Planned console profile
03 / WINDOWS

Direct Wayland

Linux GUI clients map to ordinary Onyx windows. Focus, input, clipboard, scaling, and presentation stay under the Onyx compositor.

Planned desktop profile
04 / SERVICES

Inspectable init

lineinit supports rc.d and init.d, dependency-aware startup, bounded restarts, and clean shutdown—without systemd.

Planned service model
05 / PACKAGES

Atomic dependencies

Signed profiles solve packages, symbols, services, and kernel capabilities before install, then publish or roll back as one transaction.

Planned package profile
06 / ACCELERATION

Shared GPU buffers

Native allocations, explicit fences, Vulkan and OpenGL target a measured zero-copy compositor path instead of streaming pixels.

Future accelerated profile
Further ahead
  • Rootless OCI containers
  • Namespaces + cgroup v2
  • Seccomp syscall policy
  • eBPF observability
  • ptrace + perf tooling
  • FUSE + overlay storage

Security by construction

One authority.
Narrower trust.

LINE does not create a second privileged operating system. OnyxOS remains the only hardware owner and security authority, while Linux permissions can narrow access but never elevate beyond the caller’s Onyx token.

ROOT ≠ HOST ADMIN

Linux UID 0 stays confined to its environment unless a specific Onyx capability is granted.

EXPLICIT PORTALS

Host files, secrets, camera, microphone, capture, clipboard, and devices cross permissioned boundaries.

MEASURED SOFTWARE

Signed roots, capability profiles, package transactions, and measured PID 1 prevent silent substitution.

MEMORY + SYSCALL GUARDS

W^X, ASLR, image validation, and seccomp policy constrain execution before native objects are acquired.

LEAST-RIGHTS OBJECTS

Descriptors and shared buffers cross only by allowlisted class, reduced rights, verified lifetime, and audit record.

FAIL-CLOSED EVIDENCE

Loaders, syscalls, portals, packages, graphics, and containers remain experimental until fuzz and negative gates pass.

The security promise is measurable: no fake success, no hidden fallback, no capability promotion without passing evidence, and no Linux failure allowed to take down the Onyx shell or compositor.

The shortest path to 1:1

Replace owners.
Prove contracts.
Cut over.

We do not recode what already passes. Work moves through the dependency spine, replaces NT5-era production owners, and closes only when the real linked system matches the pinned Windows 11 oracle—including failure behavior.

  1. 01 / NOW Native API spine

    Finish NTDLL, Kernel32, and KernelBase runtime ownership and differential behavior.

  2. 02 / CUTOVER OnyxBoot owns startup

    UEFI-first measured boot, signed manifests, recovery, and a verified native kernel handoff.

  3. 03 / SESSION Windows 11 logon model

    Credential providers, secure attention, tokens, lock, sign-out, and shell lifecycle.

  4. 04 / DESKTOP Modern graphics

    Compositor-owned presentation, WDDM-class contracts, scaling, accessibility, and resilient input.

  5. 05 / SCALE Compatibility lab

    Automated Windows 11 versus OnyxOS probes across applications, drivers, installers, and hardware.

  6. 06 / RELEASE Update and recover

    Atomic signed updates, A/B rollback, repair media, stress qualification, and reproducible releases.

Verified build signal 05 / LIVE Checking source activity

Local authentication

You are watching an operating system become real.

54 %
Public preview readiness

6 of 12 public-preview gates have verified evidence.

  1. SYS.01 Foundation 2/2 verified
  2. SYS.02 System services 2/2 verified
  3. SYS.03 Devices and input 2/2 verified
  4. SYS.04 Desktop session 0/2 verified
  5. SYS.05 Native startup 0/1 verified
  6. SYS.06 Preview release 0/3 verified

Build console

Public preview gate map

12 gates · 54 verified points · evidence only

Verified · 8 ptsReproducible system buildEvidence accepted
Verified · 10 ptsUEFI boot reaches the kernelEvidence accepted
Verified · 10 ptsCore services startEvidence accepted
Verified · 10 ptsGraphical logon is visibleEvidence accepted
Verified · 8 ptsKeyboard and secure input pathEvidence accepted
Verified · 8 ptsCore hardware discoveryEvidence accepted
Active · 10 ptsLocal authenticationCurrent focus
Active · 12 ptsDesktop session and shellIn development
Active · 10 ptsOnyx-native startup pathIn development
Queued · 6 ptsInstall and update experienceWaiting on earlier gates
Queued · 5 ptsStability qualificationWaiting on earlier gates
Queued · 3 ptsPublic preview packageWaiting on earlier gates

A gate earns its full weight only when its named evidence exists. Active work remains visible, but adds no progress until it clears.

6 / 12 Verified gates 6 gates remain

Live Status feed Checked every two minutes

Today Source activity Latest change verified today

Evidence ledger

What has been verified

These gates have named source evidence and currently contribute to the public-readiness score.

Verified now

  • Reproducible system build
  • UEFI boot reaches the kernel
  • Core services start
  • Graphical logon is visible
  • Keyboard and secure input path
  • Core hardware discovery

In progress and next

  • Local authentication
  • Desktop session and shell
  • Onyx-native startup path
  • Install and update experience
  • Stability campaign
  • Public preview package
How the live score works

The percentage is calculated from twelve weighted public-preview gates. A gate contributes only after its named evidence exists; unfinished work receives no partial credit.

Why OnyxOS 06 / THE INTENT

Familiar enough to use.
Different enough to matter.

N

Native by default

One system owns the hardware, the desktop, and the experience. No second OS hiding underneath.

P

Performance with purpose

Fast startup, direct execution, and a responsive desktop are architecture—not afterthoughts.

O

Measured progress

Every milestone earns its place through working evidence. The public signal moves only when the system does.

The next boot starts here

OnyxOS is coming.

The first public preview will arrive when every release gate is ready—not a moment before.

Private build in progress