Resilience from the ground up
Failures are treated as conditions that should be contained, diagnosed and recovered from in a controlled way.
Operating system
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.
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
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.
Failures are treated as conditions that should be contained, diagnosed and recovered from in a controlled way.
Isolation, explicit authority and resource policies are part of the platform design, not a layer added at the end.
Login, desktop, compositor, terminal, shell, administration and utilities are developed as native components.
Compatibility with applications from other ecosystems grows incrementally without turning those ecosystems into the foundation of the system.
Capabilities
Status describes maturity within a validated scope. It is not a promise of universal compatibility or a public release.
GalvyOS already boots as an independent system and runs processes, services and user sessions on its own platform.
The graphical experience already forms a complete, usable session in controlled test environments.
The Vulkan path is integrated on supported virtualized platforms, including presentation inside the desktop. Broad physical GPU coverage remains an active work area.
GalFS already covers a broad set of modern capabilities focused on integrity, recovery and practical data management.
The system works with several storage families and common external formats, keeping conservative limits where a path is not yet ready for general use.
Dual-stack client networking is integrated and the system already has a native SSH stack for secure remote administration.
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.
GalvyOS can be inspected and administered from its own userland. galctl adds a consistent interface for configuration, inventory and operational control.
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.
The signed package, repository, staging and rollback foundation already exists. The complete in-system install, execute, verify and remove flow remains an active milestone.
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.
Current state
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.
Boot, multiprocessing, processes, IPC, services and user sessions form an operational platform.
Login, compositor, desktop, input and terminal are integrated; Vulkan works on supported virtualized platforms.
GalFS covers a broad range of modern storage, verification, recovery and integrity capabilities.
IPv4/IPv6, DHCP, DNS/DoH, NTP and native SSH are integrated within their current scope.
The foundation exists and runs real software, but complete third-party-facing flows are still being closed.
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
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.