guideXOS Server Wiki
guideXOS Server is the multi-architecture systems-platform branch of the guideXOS ecosystem. It explores a layered OS design, UEFI-first boot, native desktop services, multi-architecture support, and future application models that can span CPU families.
What this branch is trying to do
guideXOS Server is not a relabel of the guideXOS desktop branch. The current Server branch is a distinct codebase centered on a native
UEFI bootloader, a multi-architecture kernel, a hosted compositor and desktop service, a manifest-driven app model, package-management
work for .gxapp, and an SDK path for future native applications.
The most stable current path is still Windows-hosted development and amd64 UEFI QEMU validation, but the current codebase already contains architecture directories, build scripts, and platform abstractions that push far beyond a single CPU family.
guideXOS Server hosted desktop and compositor work from the current repository screenshots.
Server ISO status
guideXOS Server is being prepared for ISO-based testing. Until a public Server ISO is posted, the recommended path is building from source and testing through the QEMU and UEFI workflow.
Server ISO
Coming soon. This area is ready to become a real download card when the public ISO is posted.
PlannedBuild from source
Recommended current path for contributors and early testers.
Active workflowQEMU and UEFI test path
Primary validation route today for Windows-hosted amd64 development.
Recommended current pathBare-metal validation
Still evolving and not yet presented as a polished public install flow.
EvolvingWhat languages and components are actually in the repo?
Native C++ is the core path
Most of the current OS-facing Server code is native C++: guideXOSBootLoader, the multi-architecture kernel under
kernel/, the hosted compositor and desktop service, Navigator, storage tools, app registry, package manager, and Native ELF work.
There is also some .NET code
The repo also includes guideXOSServer.csproj targeting net9.0 and smaller C# areas such as
GuideXOS.FileExplorer and GuideXOS.FileSystem. Those are real components, but they are not the primary OS runtime path described by the Server app-model docs.
Start here
Overview
Read the big-picture explanation of the branch, its layered goals, and how it differs from the guideXOS C# branch without treating either one as secondary.
Open OverviewArchitecture
See how the repo splits bootloader, kernel, hosted compositor, desktop service, app registry, and user-facing applications.
Open ArchitectureBoot and UEFI
Follow the current UEFI-first boot path from the MSVC bootloader through kernel handoff and QEMU launch scripts.
Open Boot and UEFISupported Architectures
Review what is in-tree, what has build or emulator evidence, and what should still be treated as planned or experimental.
Open Supported ArchitecturesDesktop and UI
Explore the hosted compositor, taskbar, start menu, icons, file-explorer integration, and what is known about bare-metal UI paths.
Open Desktop and UIApplication Model
Understand built-ins, manifests, Native ELF, GXAPP packaging, launch resolution, and the split between hosted and bare-metal app registration.
Open Application ModelNavigator Browser
See what the current browser can actually do today, including HTTP, HTML subset parsing, forms-lite, CSS-lite, bookmarks, and current limits.
Open Navigator BrowserFile System and Storage
Read about ATA, NVMe, RAM disks, VFS mounting, filesystem support, Disk Manager, package installation paths, and the current HD installer state.
Open StorageBuild and Testing
Use the actual build scripts and repo workflows for bootloader builds, kernel builds, hosted builds, QEMU launches, and sample app validation.
Open Build and TestingHypervisor and Emulation
Review the hypervisor/emulation concepts carefully as roadmap territory unless the source clearly proves more.
Open Hypervisor and EmulationRoadmap
Track the planned universal-binary, SDK, package, browser, storage, and architecture milestones without confusing them with finished work.
Open RoadmapContributor Notes
Get oriented quickly, avoid mixing up guideXOS Server with guideXOS C#, and understand how to test and document changes honestly.
Open Contributor NotesCurrent branch character in one page
The current Server branch presents guideXOS Server as a branch that cares about strict layering: the bootloader loads the kernel, the kernel owns boot knowledge, the hosted compositor and desktop service drive current rich desktop development, and the app model is moving toward manifest registration plus future multi-architecture packaging. That does not make guideXOS invalid; it simply means guideXOS Server is pursuing a different branch goal under the same umbrella project.