Table of contents
Host Inventory
- Type: Reference
- Status: Current
- Scope: Managed hosts and staged NixOS targets
- Canonical sources:
flake.nix,hosts/*/default.nix, host hardware files,modules/common/default-config.nix, andpotential/nova/default.nix- Last verified: Source commit
556df88494686003b1c4f20c8e0b99b5afc16a6e(2026-09-12); deployment evidence checked in Beszel on 2026-09-12- Review triggers: Changes under
hosts/orpotential/,nixosConfigurations,nixosConfig.host, hardware imports, specialisations, release inputs, or host deployment state
This inventory describes each managed NixOS composition root and distinguishes declared configuration from live deployment evidence. Service ownership is summarised only to explain host purpose; the Service Catalogue owns the complete service-level inventory.
Registered NixOS hosts
Electra
| Field | Value |
|---|---|
| Role | Laptop; primary desktop, gaming, local-AI, and mobile-work system |
| Hardware | Framework Laptop 16, AMD AI 300-series platform, integrated AMD GPU, optional removable NVIDIA expansion bay |
| Location | Mobile; deliberately no fixed nixosConfig.host.location |
| Release / state version | Unstable (currently NixOS 26.11) / 25.11 |
| Nebula | 10.10.0.20 |
| Inventory tags | laptop, amdcpu, amdgpu, nvidiagpu, ollama |
| Auto-update | Consumer |
Electra has one flake target and three boot variants in every generation. The
base entry is labelled battery; igpu and dgpu are specialisations. They
describe whether the removable NVIDIA expansion bay is physically absent or
present, not a preference for which GPU to use. The base configuration owns
shared hardware and endurance behavior; the specialisations relax that
endurance policy, add gaming, maker, and local-Ollama workloads, and in dgpu
add the NVIDIA hardware configuration. ADR-001
records why these variants are one generation and why the GPU variants describe
hardware presence.
Lena
| Field | Value |
|---|---|
| Role | Laptop for Claire, with a second administrator account |
| Hardware | Lenovo IdeaPad 5 2-in-1 Gen 9 (16AHP9 hardware module), AMD CPU/GPU, tablet sensors, fingerprint reader |
| Location | Mobile; deliberately no fixed nixosConfig.host.location |
| Release / state version | Unstable (currently NixOS 26.11) / 25.11 |
| Nebula | 10.10.0.21 |
| Inventory tags | laptop, amdcpu, amdgpu |
| Auto-update | Consumer |
Lena uses the laptop and AI desktop profiles, supports tablet-mode sensors, and limits SSH to the Nebula interface. It has no hardware specialisations.
Vega
| Field | Value |
|---|---|
| Role | Headless storage-backed services, AI agents, and cache server |
| Hardware | Physical Intel server with Intel graphics support and a persistent secondary Btrfs SSD |
| Location | Desk |
| Release / state version | Unstable (currently NixOS 26.11) / 25.11 |
| Nebula | 10.10.0.2 |
| Inventory tags | server, intelcpu, docker, attic |
| Auto-update | Consumer |
Vega is the main storage-backed application host. It also provides selected
fleet functions including Attic, AI-agent integrations, Engram Cloud, Trilium,
BookStack, mesh DNS/exit-node behavior, and native services backed by local or
NAS state. Its secondary SSD at /mnt/storage and /mnt/partial deliberately
survives OS reprovisioning and is managed outside Disko.
Lyra
| Field | Value |
|---|---|
| Role | Headless GPU compute and media/service server |
| Hardware | Intel i5-1340P system with integrated Intel graphics and a permanently attached Thunderbolt NVIDIA RTX 4070 eGPU |
| Location | Desk, physically on top of Vega |
| Release / state version | Unstable (currently NixOS 26.11) / 25.11 |
| Nebula | 10.10.0.3 |
| Inventory tags | server, intelcpu, nvidiagpu, docker, ollama, media, attic |
| Auto-update | Consumer |
Lyra owns GPU-heavy and media workloads. The RTX 4070 is compute-only; the integrated Intel GPU is also available to media processing. Current configuration includes native Ollama, Redview, Jellyfin, Immich, Tdarr, and Whisper capabilities alongside retained container support.
Cosmos
| Field | Value |
|---|---|
| Role | Stable PostgreSQL server VM with Adminer |
| Hardware | Proxmox/QEMU virtual machine without configured swap |
| Location | pve2 |
| Release / state version | Stable NixOS 26.05 / 26.05 |
| Nebula | 10.10.0.8 |
| Inventory tags | server, postgresql, adminer, proxmox, nebula |
| Auto-update | Consumer |
PostgreSQL and Adminer bind to the Nebula address rather than a LAN-wide listener. Cosmos also produces logical PostgreSQL backups. Application-specific database contracts live alongside its host configuration.
Chaos
| Field | Value |
|---|---|
| Role | Stable Docker workload VM for packages not suitable for native service packaging |
| Hardware | Proxmox/QEMU virtual machine without configured swap |
| Location | pve2 |
| Release / state version | Stable NixOS 26.05 / 26.05 |
| Nebula | 10.10.0.9 |
| Inventory tags | server, docker, proxmox, nebula, awkward-packages |
| Auto-update | Consumer |
Chaos isolates container-oriented workloads from the physical service hosts. Its declared workloads include Rangarr, Killarr, the Paseo relay and web UI, slskd, SynthSeek, and Plexdrome. Individual service entries must distinguish enabled configuration from dormant or transitional runtime state.
Staged host: Nova
Nova is a Framework Desktop with an AMD Ryzen AI Max+ 395 platform. Its proposed
NixOS configuration lives under potential/nova/, is not imported by
flake.nix, and is not built by normal flake checks or fleet CI. The file
proposes AMD/ROCm Ollama, Docker, and an auto-update producer role.
Beszel reported Fedora 44 on Nova on 2026-09-12. Until a NixOS deployment is
explicitly completed and verified, treat everything in potential/nova/ as
future intent rather than an active NixOS capability.
Inventory semantics
role,purpose, optionallocation, and tags come from evaluatednixosConfig.hostvalues.- Tags are filterable inventory facts. They must not be moved to
system.nixos.tags, which would alter boot-generation labels. system.stateVersionprotects compatibility defaults; it is not the installed NixOS release.- Release values above record the inputs evaluated on the verification date and will change as channels advance.
- Live online/offline state belongs in monitoring, not this page.
Return to Fleet Overview, continue to the Service Catalogue, or use the System Atlas.