Common questions about Star-Blade OS.
Direct answers for readers who want the essentials without reading every technical page first.
Is SBOS publicly released?
No. SBOS remains private and controlled. These pages are public references, not download pages.
Is SBOS a Linux distribution?
No. SBOS has early Linux-based research history, but current SBOS is a proprietary custom operating system direction with its own kernel lineage, filesystem and storage model, network stack, userland, app execution architecture, provisioning, diagnostics, and service ecosystem.
Does SBOS use Wine, Proton, or a normal VM for app compatibility?
SBOS compatibility is part of its OS execution model. The native hypervisor exists for virtualization, but regular app compatibility is handled through SBOS-controlled app environments and profiles.
Can SBOS run Windows, Linux, and macOS app classes?
Yes. SBOS is designed to support native SBOS apps as well as supported Windows, Linux, and macOS application classes through app-specific environment contracts.
Why does SBOS ask for permissions more often with intrusive tools?
Apps that want broad visibility, network control, capture, remote access, or cross-system reach are asking for sensitive authority. SBOS keeps those decisions explicit instead of silently granting them.
What are SBGS and FST ID?
SBGS is Star-Blade Gateway Services for firewalling, routing, proxying, inspection, DNS controls, remote access, and gateway policy. FST ID is the identity, directory, policy, certificate, SSO, and trust layer.
Does SBOS collect user behavior?
SBOS diagnostics focus on system behavior such as crashes, invalid states, performance faults, compatibility issues, freezes, and stack traces. The model is system telemetry, not user profiling.
What is the simplest explanation of SBOS?
SBOS is a full custom operating system that gives apps the environment they expect while keeping their reach controlled.