pulse

Pulse is a self-hosted monitoring workspace aimed at homelab and small-to-mid infrastructure operators. It covers Proxmox VE, PBS and PMG, Docker and Podman, Kubernetes, TrueNAS SCALE and CORE, Linux/Windows/macOS machines, and early-access VMware vSphere environments. Rather than replacing a full enterprise monitoring stack, it focuses on surfacing what needs attention: failed backups, capacity pressure, restart loops, unhealthy containers, clock drift and similar issues that a dashboard alone will not flag when nobody is watching. Each platform gets a dedicated view (nodes, guests, storage, backups, replication, Ceph, containers, Compose projects, Swarm services, clusters, workloads, pods, pools, datasets, snapshots, apps, VMs, datastores, networks), while search, alerts, history and investigation run on one shared resource model. Alerts, Actions and Patrol are cross-platform views. Patrol is the scheduled-check component: it runs periodic analysis over current state and recent history. Community installations can point it at a local model or their own AI provider for watch-only analysis; a commercial Pro edition adds investigation and policy-bound fixes with approval, verification and an audit trail. An interactive Assistant and an MCP adapter for external clients such as Claude Code and OpenCode sit on the same scoped inventory, metrics, alert, storage and governed-action contracts. Deployment options include a Docker image (port 7655, data volume, bootstrap-token setup), a signed Proxmox LXC/Linux installer verified with an SSH signature, Docker Compose, and Kubernetes/Helm. Proxmox VE, PBS and PMG can be monitored through the Proxmox API with a read-only token, so no host agent is required; the unified agent is only needed for data the platform API cannot supply, such as host SMART health, temperatures, Docker hosts or standalone machines. The agent is operator-controlled: command execution is off by default, the local listener binds to localhost, systemd units ship hardened, and a least-privilege profile runs the service as a dedicated non-root user with optional scoped sudo grants. Security posture includes credentials encrypted at rest, scoped API tokens, and governed fixes requiring a configured policy and approval path. The project documents an agent security model, production/security guidance, privacy notes and a code-signing policy. Editions: Community (self-hosted monitoring, seven days of metric history, core SSO, update alerts, Patrol with your own provider or local model), Relay (adds secure remote web access, mobile pairing, push notifications, fourteen days of history), Pro (adds Patrol investigation, governed fixes, ninety days of history, centralized agent profiles, RBAC, audit logging, reporting) and MSP (one account running many isolated client workspaces). Core self-hosted monitoring is not gated by monitored-system or child-resource volume. The repository itself is MIT-licensed; the commercial Pro product is built from private sources and distributed separately. Development uses Go and a SolidJS/TypeScript frontend, with a managed dev runtime proxying API and WebSocket traffic to the backend. The project follows an issue-first contribution process and generally does not accept unsolicited pull requests.