Durable inventory
Every monitored host, service, endpoint, application, database, network device, UPS, or sensor is a post with identity, ownership, dependencies, labels, and maintenance state.
Product direction
A watchpost for every environment.
Each node remains useful by itself: collect locally, retain history, evaluate rules, open incidents, and investigate. Connect nodes into a fleet when coordination adds value—not because the product requires a cloud control plane.
One operational model
Monitoring that remembers the investigation.
Watchpost connects inventory, telemetry, alert state, incidents, human notes, agent conversations, and approved actions without flattening them into an undifferentiated event stream.
Signals and events
Measurements and transitions retain time, source, quality, freshness, and units so operators can distinguish failure from uncertainty.
Alerts and incidents
Rules create visible state; incidents gather related evidence and preserve the path through acknowledgement and resolution.
Operational agent
Investigation tools traverse bounded data and expose evidence. Privileged actions are typed, scoped, approved, and audited separately.
Designed to grow
Local first. Fleet capable.
A disconnected Watchpost continues monitoring its environment. Federation adds selective sharing, fleet-wide views, and coordination while preserving local authority and bounded failure.
Independent nodes
Collection, rules, incidents, dashboards, and investigation work on one node without a mandatory external service.
Selective federation
Nodes share only configured post, event, and incident state across explicit trust and tenancy boundaries.
Store and forward
Bounded queues, identity, ordering, deduplication, revocation, and reconciliation make disconnection a designed state.
Open interfaces
Versioned collector and integration contracts meet heterogeneous environments without an unsafe in-process free-for-all.