System Profiles
Nexus OS produces multiple system profiles from a single codebase. Each profile targets a specific hardware class and use case — from a 256-byte sensor firmware to a 40MB cluster node.
The build toolkit selects which components to include based on the profile:
sh
nexus build --profile=tiny --arch=riscv64
nexus build --profile=micro --arch=aarch64
nexus build --profile=core --arch=x86_64
nexus build --profile=fleet --arch=riscv64
nexus build --profile=unikernel --arch=aarch64Standard Template Constructs (STCs)
| Profile | Size | Target Hardware | Status |
|---|---|---|---|
| Nexus Tiny | 256B – 32KB | 8-bit MCU, single sensor | Planned (Q2 2026) |
| Nexus Micro | 180KB – 1.2MB | Embedded (Pi, VisionFive, satellite) | Prototype Verified |
| Nexus Core | 4 – 8MB | Workstations, servers | Planned (Q3 2026) |
| Nexus Fleet | 8 – 40MB | Clusters, quantum farms | Planned (Q4 2026) |
| Nexus Unikernel | 100KB – 500KB | Aerospace, radiation-hardened | v0.9 Complete |
Shared Foundations
All profiles share:
- The same
.np*package format - The same GoboLinux-style
/Programs/App/Version/hierarchy - The same capability-based security model
- The same ProvChain audit trail
- The same build toolkit
The difference is which components are included. A Tiny profile includes one NPS (sensor package) and no OS. A Core profile includes the full Rumpk kernel, Surface Manager, nip, and hundreds of NPK applications.
Feature Matrix
| Feature | Tiny | Micro | Core | Fleet | Unikernel |
|---|---|---|---|---|---|
| Rumpk kernel | — | Yes | Yes | Yes | Yes |
| Rumkv hypervisor | — | Optional | Optional | Yes | — |
| NexFS | — | Core only | Full | Full + Mesh | Core only |
| Network (Membrane) | — | LwIP | Full | Full + UTCP | LwIP |
| Display (Surface Manager) | — | — | Yes | Optional | — |
| nip package manager | — | Minimal | Full | Full | — |
| SignalForge | — | Optional | Optional | Optional | — |
| ProvChain | — | Yes | Yes | Yes | Yes |
| ECC scrubbing | — | — | — | — | Yes |