GalvyOS
Advanced technology preview · no public ISO yet

Operating system

GalvyOS

GalvyOS is an independent x86-64 operating system, written primarily in C++ and built from scratch around a microkernel-oriented architecture. It is not a Linux distribution or a variant of BSD or Windows.

x86-64current platform
BIOS + UEFIboot and installation
GUI nativaintegrated graphical session
IPv4 + IPv6dual-stack networking
GALVYOS / STATUS
galvy@system:~$ system overview

platform
    independent x86-64 OS

boot
    BIOS / UEFI

desktop
    native graphical session

storage
    GalFS + external filesystem support

network
    IPv4 / IPv6 + secure DNS + SSH

Core platform ready
Native desktop ready
Storage stack advanced
Network client stack ready
Public release not available yet

Vision

It is not trying to be another distribution. It is trying to be another system.

GalvyOS is being built as a complete product: kernel, services, storage, networking, tools, desktop, installation and recovery evolve as parts of the same platform. The goal is not to copy another operating system, but to provide its own experience without giving up interoperability.

01

Resilience from the ground up

Failures are treated as conditions that should be contained, diagnosed and recovered from in a controlled way.

02

Security with explicit boundaries

Isolation, explicit authority and resource policies are part of the platform design, not a layer added at the end.

03

A native experience

Login, desktop, compositor, terminal, shell, administration and utilities are developed as native components.

04

Compatibility without losing identity

Compatibility with applications from other ecosystems grows incrementally without turning those ecosystems into the foundation of the system.

Capabilities

What GalvyOS can already do.

Status describes maturity within a validated scope. It is not a promise of universal compatibility or a public release.

Functional

Core platform

GalvyOS already boots as an independent system and runs processes, services and user sessions on its own platform.

  • BIOS and UEFI boot
  • Multiprocessing and preemptive scheduling
  • Isolated user processes and services
  • IPC, capabilities and resource control
Functional

Native desktop

The graphical experience already forms a complete, usable session in controlled test environments.

  • Graphical login and user sessions
  • Native compositor and desktop
  • Windows, keyboard, mouse and input
  • Graphical terminal and native applications
Functional in virtualization

Accelerated graphics and Vulkan

The Vulkan path is integrated on supported virtualized platforms, including presentation inside the desktop. Broad physical GPU coverage remains an active work area.

  • Vulkan devices, queues, memory and pipelines
  • Presentation integrated with the compositor
  • Surface resize and recreation
  • 2D fallback on device loss within the validated scope
Advanced

GalFS, the native filesystem

GalFS already covers a broad set of modern capabilities focused on integrity, recovery and practical data management.

  • Copy-on-write, snapshots and reflinks
  • Large files, sparse files and range I/O
  • Compression, encryption and key management
  • ACLs, quotas, deduplication and verification
  • Scrub, rollback, recovery and multi-device support
Expanding

Storage and interoperability

The system works with several storage families and common external formats, keeping conservative limits where a path is not yet ready for general use.

  • NVMe, SATA/AHCI, IDE and USB storage
  • FAT32 and exFAT read/write
  • EXT4 read/write with journaling evolving
  • Usable NTFS read support and QA-gated write support
  • ISO9660 read support
Functional

Networking and remote administration

Dual-stack client networking is integrated and the system already has a native SSH stack for secure remote administration.

  • IPv4 and IPv6
  • DHCPv4 and DHCPv6
  • Cached DNS and DNS over HTTPS
  • TLS/X.509 and dual-stack NTP
  • SSH client and server, SFTP and forwarding
Most mature in virtualization

Drivers and platforms

QEMU/KVM is currently the most mature platform. VirtualBox already covers a functional baseline and several physical hardware families are supported, but universal hardware compatibility is not claimed.

  • VirtIO and common virtual devices
  • VirtualBox baseline for boot, installation, networking, display and input
  • NVMe, AHCI, USB xHCI/HID and PS/2
  • Selected Intel and Realtek NICs
  • Wi-Fi, Bluetooth, physical GPU, audio and laptop power management are still incomplete
Functional

Shell and administration with galctl

GalvyOS can be inspected and administered from its own userland. galctl adds a consistent interface for configuration, inventory and operational control.

  • GShell and everyday utilities
  • CPU, memory, PCI, USB, disk and network inventory
  • Processes, services, events and logs
  • Transactional configuration and structured output
  • CLI autocompletion and automation
Functional with lifecycle still evolving

Installation, Recovery and updates

Setup already performs real BIOS and UEFI installations, and Recovery exists as an independent environment. The complete update, reboot, rollback and recovery lifecycle is still being closed.

  • Real installation to an empty disk
  • BIOS and UEFI boot
  • Recovery independent from the main system
  • Update and anti-rollback infrastructure
  • End-to-end lifecycle closure still in development
Advanced foundation, E2E flow pending

Packages and software

The signed package, repository, staging and rollback foundation already exists. The complete in-system install, execute, verify and remove flow remains an active milestone.

  • Signed package format and verification
  • Signed repository
  • Staging and rollback
  • Durable GalFS-backed storage
  • Full user-facing flow still pending
In development

Application compatibility

Compatibility grows from real applications. The Linux subsystem already runs console workloads and toolchains; Windows compatibility is much earlier and is not presented as general-purpose compatibility.

  • Real Linux applications validated at different levels
  • Toolchains and development utilities used as test cases
  • Linux coverage expanded from observed blockers
  • First Win64 execution milestone reached
  • General Windows compatibility is not yet available

Current state

Functional today, with complete product verticals still to close.

GalvyOS is already a functional operating system for development, demonstration and validation in controlled environments. The hard part now is not proving that individual pieces exist, but closing complete verticals: a reference physical hardware profile, update/rollback lifecycle, end-to-end packages and a reproducible release that can be handed to third parties with clear limits.

Functional

Core system

Boot, multiprocessing, processes, IPC, services and user sessions form an operational platform.

Functional

Desktop and virtual graphics

Login, compositor, desktop, input and terminal are integrated; Vulkan works on supported virtualized platforms.

Advanced

Native storage

GalFS covers a broad range of modern storage, verification, recovery and integrity capabilities.

Functional

Networking and SSH

IPv4/IPv6, DHCP, DNS/DoH, NTP and native SSH are integrated within their current scope.

In development

Packages and compatibility

The foundation exists and runs real software, but complete third-party-facing flows are still being closed.

In development

Physical hardware and release

The priority is to complete an end-to-end PC/laptop profile and turn the integrated state into a reproducible public release.

Public by design

Share what is useful without publishing what is sensitive.

We publish what a user or evaluator can understand and verify: capabilities, limits, platforms and product direction. Operational details, internal contracts, sensitive security mechanisms and the engineering backlog stay outside the public site.

What we publish

  • Visible capabilities and known limits
  • Validated hardware families and platforms
  • Relevant protocols, formats and user flows
  • General compatibility status
  • High-level product direction and priorities

What stays off the public site

  • Internal implementation details
  • Private contracts and structures
  • Operational build and certification procedures
  • Sensitive security and recovery mechanisms
  • Backlog and internal infrastructure information