The console

Views

Arrange a view — dashboards, maps, floor plans and live cameras, saved exactly as you left them.

Dashboards

Compose your own view: drag widgets onto a canvas and pin each one to an identifier, detail identifier and time range. Saved per credential and restored exactly as left.

Log Stream Line Chart Bar Chart Latest Values Camera Compass Rose Wind Rose

Drag from a palette onto the canvas, then drag to reorder and pull to resize — width in columns, height in pixels.
Each widget carries its own query: a relative or absolute range, the summary per step — average, minimum, maximum, sum, count, median and percentiles (P05–P99), spike envelopes, standard deviation, first/last/consumption for meters, or data coverage — the size of each step along the axis, a result cap and a refresh interval.
Charts take several series at once, each with its own identifier and colour.
Bands — shade a min–max envelope or ±2σ around each series, or a learned baseline: the chart studies the last two weeks of each hour of day, shades what normal looks like, and flags every reading outside it.
Compare — overlay the same series from the previous day, week or 30 days as a ghost line, so “is this normal for a Tuesday?” is answered by looking.
Any chart exports what it is showing as CSV, exactly as zoomed.
Replay — scrub a time range and every widget that can replay follows it together.
Correlate — put series side by side to see whether two things really move together.
Bearings get their own widgets: a compass rose and a wind rose, because a direction averaged as a plain number is nonsense across the 0°/360° seam.
A live camera is a widget like any other, so a feed sits next to the readings it explains.
Filed under your Labels, shareable read-only, and openable straight from a Maps pin or a Floor Plans marker.
Log markers — the asset's own error and warning lines drawn as ticks along the chart's timeline, so a reading is read next to what the machine said at the time.

A dashboard canvas with line charts, value tiles, a camera tile and a log stream. — A dashboard mid-replay: charts drawn exactly up to the scrubber, live-only widgets honestly sitting it out.

A line chart with a learned baseline band; a temperature spike pierces the band and is flagged with red anomaly markers. — The learned baseline at work: two weeks of “normal” shaded behind the line — and the one spike that isn't, flagged in red.

Replay & Correlate

Built for the question “what happened here?”

Live views answer “what is happening”. The harder question arrives later — after the incident, during the review, in front of a customer — and two dashboard features exist purely for it.

Replay — run the moment again

Pick a starting point and press play: every chart and log stream on the dashboard moves through the same timeline together, at 1× to 10×, with a scrubber to jump straight to the minute that matters. Widgets that only make sense live — cameras, current-value tiles — say so and sit it out, so what you see is honestly labelled. Nothing is exported, reconstructed or stitched: it is the same dashboard, moved back in time.

Correlate — put a second witness next to the first

A spike on a chart raises one question: what else was true at that moment? Click the spike, choose Correlate here…, and a new widget — a log stream, another chart, a wind rose — lands beside it, pinned to the exact window the first chart is showing. The pair stays locked together instead of drifting apart on refresh, so the comparison you set up is still the comparison an hour later. A correlated log stream even carries your highlight colours, so the fault line is marked before you read a word.

The Correlate dialog on a dashboard, showing the pinned time window the new widget will inherit and the widget types to choose from. — Correlate at a clicked moment: the new widget inherits the exact window, pinned so the pair can never drift apart.

Maps

Drop pins on a world map and link each one to a dashboard, a floor plan or a camera. Pan, zoom and move pins freely; the whole map — pins and the view it opens at — is saved per credential.

Dashboard pins — a place on the map that opens the data behind it.
Value markers — a live readout sitting where the sensor is, recolouring itself as it crosses threshold bands you define.
Direction markers — an arrow that points where the bearing actually points.
Location markers — a tracker's own position, drawn from its readings rather than placed by hand.
Camera markers — the lens where the lens is; click to watch it live in place.
Floor plan markers — a building on the map that opens the drawing inside it.
Markers are dragged to move and resized with a grip; colours, sizes and threshold bands are yours to set, and a legend explains the result.

A world map with value badges, direction arrows and camera markers placed on it. — Live values, bearings and cameras placed where they physically are.

Floor Plans

Upload a building drawing and place the same markers a map takes — pin dashboards, live readouts, direction arrows and cameras — anywhere on it.

Several floors per building, switched from a floor menu.
The same marker palette as Maps, so what you learned on one surface works on the other.
Positions are stored as fractions of the drawing, not pixels — so a re-exported plan at a different size keeps every marker exactly where it was.
Reachable from a map marker, so a site on the world map opens into the room inside it.

A building floor plan with markers placed on rooms. — A floor plan with live markers placed room by room.

Cameras

One registry shared by everyone on this server: watch any registered camera live — here, on a dashboard, or on a map or floor plan where the lens actually is — a fraction of a second behind.

Live, not lagging. The picture arrives a fraction of a second behind rather than the several seconds live video in a browser usually costs.
Two kinds of camera. Streaming sources, with the connection pinned or left to negotiate itself, and plain snapshot cameras that serve a single image.
Leave the picture alone, or re-encode it. A camera already producing something a browser can play is passed through untouched; one that is not gets converted. Audio optional.
One pull, many viewers. A snapshot camera is fetched once and the frame shared by everyone watching, rather than every viewer reaching the device.
Nothing is recorded. A camera is pulled only while somebody is watching and stops shortly after the last viewer leaves, on a per-camera idle timeout.
Registering is administrative. Watching takes one grant; registering, re-pointing or deleting takes another, because a camera is a device rather than a document.
Camera passwords are stored encrypted, never in the clear.
Plays in Safari and on iOS, where the browser's own media engine is the only option.