The Canvas suite

Each app does one job and hands its output to the next: draw the network, watch it answer, graph what it reports, keep what it says, get told when something crosses a line. Everything runs on your own hardware, stores its data in plain files and SQLite, and works without any of the others - the suite is how they behave together.

CrossCanvas ──draw──► your diagram (.xcanvas) ──upload here──► PingCanvas (the wall)
     ▲                                                             ▲
     │ inventory CSV                                 live readings │
     │                                                             │
SNMPCanvas ──polls your devices──► snmp-status.json ───────────────┤
                                                                   └──► AlertCanvas ──► email / ntfy / syslog
SyslogCanvas ◄──syslog + SNMP traps─── your devices
LaunchCanvas ── one login, the tiles, board upload (you are here)

From a fresh VM and a device list to a live wall is about ten minutes - the Quickstart walks the whole path.

The apps

CrossCanvasDraw the network - or import Visio, draw.io, Gliffy, or a CSV PingCanvasYour diagram as a live wall - reachability colors, kiosk mode SNMPCanvasPoll device health over SNMP - graphs, history, exports SyslogCanvasThe flight recorder - syslog and SNMP traps, searchable AlertCanvasThresholds on the readings - email, ntfy, syslog alerts LaunchCanvasThe front door - one login, tile launcher, board upload

Where things live

• Every app is its own repository with its own README - the cards above link to a short in-suite guide per app, and each guide links to the full documentation on GitHub.
• The wall reads one file: board.xcanvas. Upload a new one from the Launch page any time - the previous board is kept as a one-click backup.
• Live readings travel as one file too: snmp-status.json, written by SNMPCanvas, read by the wall and by AlertCanvas.
• All six are public domain (The Unlicense). Use them, fork them, ship them at work.