[Announcement] VeloOS - Freestanding x86_64 Hybrid Kernel with 60-FPS Atomic Compositor & Integr

[vntxlabs]

Hi everyone,
I wanted to announce a project I have been working on continuously for the past few months: VeloOS, a custom, freestanding x86_64 hybrid operating system booting natively via UEFI.
The primary architectural goal of the project is to achieve extreme RAM execution velocity by combining an in-memory VFS with aggressive page-table isolation between privileges, separating the core driver stack from the modular user-space infrastructure.

Current Architectural Status:

• Kernel Design: Hybrid-model architecture. Device drivers (AHCI, NVMe, Keyboard, Mouse, Network) remain stable within Ring 0 to prevent context-switch overhead, while the Window Manager (Argon), Desktop Environment (Cinnamon-Muffin), and Shell are isolated in Ring 3.

• Graphics Subsystem (Jupiter): Features an atomic 60-FPS blitting and frame-buffer synchronization layer encapsulated within Ring 0. This guarantees jitter-free execution and prevents scheduler-preemption display freezes when user-space applications saturate the CPU. Includes a procedural 3D Raymarching/SDF real-time cinematic boot animation.

• Storage & VFS: POSIX-compliant VFS backed by a customized lwext4 subsystem mapping directly to raw disk partitions. Implements a clean, standardized Linux FHS directory layout (/bin, /etc, /sys, etc.).

Toolchain & Technical Specs:

• Target: x86_64-elf cross-compiler toolchain

• Environment: Freestanding C and Assembly (kernel_entry.S bootstrap handles immediate UEFI code-segment overriding and enforced System V ABI 16-byte stack alignment).

• Testing: QEMU with KVM acceleration enabled.

The code is fully open-source and hosted on Codeberg. I’m currently stabilizing the Global Offset Table (GOT) layouts for dynamic object linking (.so) and would love to get some feedback on the hybrid Ring 0 / Ring 3 VFS character device abstraction mapping.

• Newest version is not online because of not working apps.

Codeberg Repository: codeberg.org/vntx-labs/VeloOS

In case of questions or if you decided to join the project just write me on discord or write an E-Mail

Looking forward to your architectural thoughts, advice, and critiques!
Best regards,
Vantix