Mona, your web app

Observability · Layer 4

"I see everything, darling."

What Mona does

Mona is the React web app the Kevin daemon serves. Open it in a browser and you can see what's running, what it costs and what needs attention, updated live.

Service status

Every service reports a build version and a heartbeat on the bus. Mona shows who's up, which version they run, and when one drifts.

Devices

Your registered edge devices, with their telemetry and firmware state, in one place.

Live bus view

Watch MQTT traffic as it happens. Handy when you're debugging a sensor or a rule.

Spend

Model costs by request, project and provider, taken from the carousel's cost ledger.

Alerts

Alerts raised by other services, such as compliance flags from Trixie, show up where you'll see them.

Live updates

The browser gets events over server-sent events, so pages update without a refresh.

How it works

Mona doesn't poll each service. The data comes to her.

  1. Services publish heartbeats, telemetry and events to the bus.
  2. The daemon collects them and exposes them through its HTTP API and a live event stream.
  3. Mona renders them as pages: status, devices, metrics, spend and alerts.
  4. Marco's authoring tools run inside the same app.

Where it fits in the four layers

1 Infrastructure & roles Vera, Grant, the bus, the device registry
2 Data pipeline & state Flo, DynaRAG, the carousel
3 Reasoning & inference Rick, Annie, Max, Hank
4 UI & collaboration Marco, Noted, Norm, the graph

Mona is a layer 4 surface. She gets her data through the daemon's API and event stream rather than calling each service, which is why a service can change without her noticing.