Dashboard
The main Dashboard route is your operational home screen. It refreshes every five seconds and summarizes fleet health, recent sweeps, and a searchable node registry.
On a Central Hub, the same route swaps to GLOBAL FLEET COMMAND, a federation-wide view of enrolled Nodes, site actions, and cross-site alerts. Standalone Nodes and portable sessions show CORE DASHBOARD instead.
CORE DASHBOARD (Node / standalone)
Open Dashboard from the main navigation. The page header reads CORE DASHBOARD with engine status and optional stats:
| Stat | Meaning |
|---|---|
| Recent Alerts | Count of alert events in the last 24 hours (Business appliances only). |
| Next Cleanup | Scheduled database maintenance window from engine health. |
Main sections
| Section | What it shows |
|---|---|
| Network Stability & Availability | Live area chart of online device counts from recent sweep history (PEAK chip + LIVE indicator). |
| Topology map | Interactive hierarchy of the local segment. Parent edges come from each device Network link → Uplink; unmapped hosts hang under the gateway. |
| Node registry | Searchable, paginated list of devices with stability score, vendor, and quick actions (open drawer, copy IP, ignore). |
| Alerts banner | Recent critical events when Business alerting is enabled. |
Click any row in the node registry to open the Device Drawer for full metadata, traceroute, and management actions. To reshape the topology map (Mode, Port / SSID, Uplink), use Overview → Network link or bulk tools on Device inventory.
GLOBAL FLEET COMMAND (Central Hub)
When the appliance is licensed and configured as a Central Hub, Dashboard becomes GLOBAL FLEET COMMAND (v1.8 layout).
Layout (top to bottom)
- Fleet health header: online/offline percentage and critical alert count
- KPI strip: managed nodes, fleet devices, setup-required count, sync health
- Filters: Client, Building, and search; Enroll Node opens the stepped wizard
- Expandable node table: one row per enrolled site; expand for version, database size, last sync, security grade
- Fleet inventory + alerts: site-scoped snippets with links into Devices and Alerts
- Per-site topology map: pick a Node to view that site’s hierarchy (same Network link rules as a standalone Node)
Hub row actions
| Action | Purpose |
|---|---|
| Open node dashboard | Opens the Node UI (HTTP on Linux/Docker :5000, macOS :5050). |
| Open site setup | When status is setup_required: HTTPS onboarding on the Node. |
| Scan (radar) | Opens Devices filtered to that site (/devices?nodeId=) for per-device deep scan. |
| Edit sync & site | Governance dialog: scan policy, alert/SIEM sync flags. |
| Enrollment string | Copy mTLS enroll payload for new sites. |
| More → Reset site | Wipe Node inventory while keeping federation enrollment. |
| More → Remove node | Delete Node from fleet (destructive). |
Deep scan is per device from the Devices page (relayed to the owning Node). Map edges still come from each device’s Network link → Uplink on that site.
For enrollment, Tailscale, and scan policy push, see Hub & fleet federation and Scan settings.
Discovery limits
Device discovery is unlimited on every tier, including free portable. StacksAtlas does not cap, mask, or grey out devices to encourage upgrades.
Free portable is session-only: inventory and reports exist for the active session and clear when you Close & remove portable data (or
docker compose down -v on Docker).Business adds a persistent database, always-on sweeps, alerts, and fleet features, not a higher discovery cap.
Related guides
- Device inventory: Network link (Mode, Port / SSID, Uplink) and bulk mapping
- Alerts: Live Events, history, Hub fleet scope
- Discovery pipeline: how sweeps populate the dashboard chart
- Reporting: PDF exports from inventory summaries