staxmonitor documentation
Choose a version
Version 0.1.x
StaxMonitor Product Requirements (PRD) #
Status: Draft for spec review · Owner: StaxDash studio. Likely first-contract flagship.
Problem #
Organizations in regulated or disconnected environments (air-gapped networks, on-prem-first operations, security-conscious teams) need host monitoring that never leaves their perimeter. They cannot adopt cloud SaaS, so they need a hardened agent and a central console that run entirely in-network, with reliable alert routing to the channels their ops teams already use.
Target users #
- Enterprise operations / NOC teams that operate air-gapped or on-prem infrastructure.
- First-contract prospect — the studio’s initial paid engagement is expected to center on this product.
- Managed-service providers that need per-node monitoring under their own control.
Solution overview #
A hardened, signed agent collects host metrics locally and reports to a central console (a self-hosted control plane) in the same network. The console provides a multi-host view, configuration, and alert routing to webhooks, Slack, and email. Because deployment must work where internet is unavailable, the whole system is air-gapped capable.
Deployment model #
Agent (per host) ── local network ──▶ Central console (self-hosted)
│
└──▶ alerts: webhook / Slack / email
- Agent: hardened, signed binary; low overhead; fails closed; buffered offline. Linux/macOS/Windows.
- Console: self-hosted control plane; multi-host view; per-host config; alert rules; audit of who changed what.
- Distribution: air-gapped — portable artifacts and a fully offline install path with no phone-home.
MVP scope (in-scope) #
- Metric collection: CPU, RAM, disk, network, service/process state
- Signed agent binaries and verified update path
- Central console with multi-host view and per-host configuration
- Alert routing to webhook, Slack, and email
- Air-gapped install and deployment (no mandatory phone-home)
- Per-seat/per-node licensing with offline license validation
Out of scope (MVP) #
- Hosted multi-tenant cluster (that is StaxLens’ role)
- Log aggregation beyond health/alert context
- Machine-learning anomaly detection
- Third-party marketplace integrations
Monetization #
Per-seat/per-node commercial license; air-gapped and support terms are part of the licensing policy.
Timeline #
Specified under Phase 3 of the organization roadmap; build begins in Phase 4.1 (flagged for earliest build). Definition of done for the spec phase: approved PRD + docs shell + repo skeleton with CI matrix.