Monitoring tells you what is happening now. RackMarshal remembers what happened.
RackMarshal maintains operational state across time: observations become evidence, meaningful changes become events, failures become incidents, and recovery is tracked instead of assumed.
Operational domains in RackMarshal 1.0
The current codebase contains operational domains for the following infrastructure. RackMarshal stores observations, events, incidents, cycle health and related state locally in SQLite.
Proxmox VE
Resource and infrastructure observations.
ZFS
Storage and pool health observations.
Backup / PBS
Backup observations and operational state.
Home Assistant
Home Assistant observations.
Hardware health
Infrastructure hardware health observations.
Mounts
Mount availability and state.
Local first by design.
RackMarshal is designed to operate without turning your infrastructure telemetry into a dependency on somebody else's hosted service.
Built in a real environment, not just designed on paper.
RackMarshal grew from a working homelab operations system and the need to understand Proxmox, ZFS, backups, Linux infrastructure, hardware and other systems as a whole.
RackMarshal 1.0 turns that system into a reproducible open-source platform for homelabs, self-hosted infrastructure, edge systems and small infrastructure environments.
Put RackMarshal into infrastructure we did not build.
We are looking for technically experienced users willing to install RackMarshal, configure it against real systems, challenge its assumptions and find the environments we did not anticipate.
A successful base installation proves the RackMarshal runtime, database, status API and notification queue can run. It does not automatically configure access to Proxmox, PBS, Home Assistant, ZFS, hardware or mount targets.
Those integrations require site-specific configuration and credentials. The installer does not copy production credentials or discover your infrastructure automatically.