INTERACTIVE DEMO · SAMPLE DATA
See what one shared inbox actually looks like.
This is the MeshWatch Central console, running here in your browser with a sample
network loaded — the same screens, the same layout, the same stylesheet as the
real thing. Click the tabs. Open an incident. Click a device row to see its full
history. Nothing to install, no account, and nothing you do here is saved anywhere.
What you just looked at
Five products reported on core-sw-01 inside a few minutes: a configuration
change, an interface going down, a burst of log messages, a certificate that stopped being
reachable, and a device that fell off. Opened separately, that is five alerts in five
applications. Central shows it as one incident with the order preserved — the change
first, then everything it caused.
What Central is not doing here
It is not deciding what went wrong. It groups alerts that landed on the same device
inside a 30-minute window and shows them in the order they arrived; reading the cause off
that timeline is still your job. A single product repeating itself is not treated as an
incident — that already shows up fine in that product's own screen.
Only summaries, even here
Every line you can see is the whole of what a product sends: severity, device name, a
kind, one sentence, a timestamp. No raw log line, configuration file, certificate or
packet capture crosses to Central — the allow-list is enforced on the receiving side,
so a product with a bug cannot leak more by accident.
Where the real one runs
On your own server, not ours. You deploy Central inside your own network — as a Docker
image, or as a Node bundle where Docker is not an option — and it makes no outbound
connections unless you switch on the optional update check. This demo is a browser
mock-up of that console so you can judge it before installing anything.