guideXOS Server Overview
Purpose: introduce the guideXOS Server branch as the multi-architecture systems-platform path in the guideXOS ecosystem.
What guideXOS Server is
guideXOS Server is the multi-architecture operating-system branch of the guideXOS ecosystem. The current Server branch describes it as an experimental operating system focused on strict layered design, a UEFI-first boot path, a desktop environment, networking, storage, and a future where one application package can carry binaries for more than one CPU architecture.
This branch sits beside guideXOS under the same umbrella project. It should be understood as a different technical direction, not as a relabel or dismissal of the guideXOS desktop branch.
Current status: active development with source-first build and QEMU validation.
Known gaps: broader ISO readiness, full cross-architecture maturity, and stronger hosted versus bare-metal parity are still evolving.
Back to /Wiki/Server
Current repo emphasis
- Native UEFI bootloader in
guideXOSBootLoader/ - Multi-architecture kernel in
kernel/ - Hosted desktop/compositor path in
server.cpp,compositor.cpp, anddesktop_service.cpp - Manifest-driven app registration and launch-resolution work
.gxapppackaging and SDK planning for future cross-architecture applications
What the repo is made of
Most current OS/runtime code is native C++. The repo also includes some .NET helper and desktop-tooling projects, such as
guideXOSServer.csproj, GuideXOS.FileExplorer, and GuideXOS.FileSystem, but the core Server branch story is not primarily a .NET runtime story.
How the branch is meant to operate
| Area | Current Picture | Status |
|---|---|---|
| Boot path | The main public build scripts focus on an MSVC-built UEFI bootloader, an architecture-selected kernel, ESP staging, and QEMU launch with OVMF firmware. | Implemented |
| Desktop environment | The repo contains a substantial hosted compositor/window-manager path and a separate bare-metal desktop path in the kernel. | Partial |
| Application model | Manifest loading, validation, registry scanning, built-in metadata, and launch resolution exist. Execution remains hybrid and differs between hosted and bare-metal modes. | Partial |
| Universal application packaging | .gxapp has a real format spec and package-manager/install code, but the wider universal-app vision remains broader than what is fully deployed today. |
Experimental |
| Cross-architecture app story | The repo clearly plans for multi-architecture packages and SDK tooling, but cross-architecture execution is not something the current docs claim is complete today. | Planned |
Hosted and bare-metal are both important
One of the clearest traits in the current Server branch is that guideXOS Server is built around two complementary paths. The hosted path lets the same desktop/compositor and app-model work move quickly on Windows. The bare-metal path keeps the project honest by requiring the bootloader, kernel, framebuffer, storage, and networking layers to work in an actual OS bring-up flow.
- Hosted path: best for desktop iteration, UI experiments, app registration, diagnostics, and some Navigator and Native ELF validation.
- Bare-metal path: best for validating boot, framebuffer setup, input, storage, networking, VFS, and kernel desktop behavior.