A real-time dashboard is a live data surface that updates within seconds of the underlying event. It is designed for operators who need continuous awareness of what is changing in the business, not a weekly snapshot. The point isn't freshness for its own sake; it is putting the operator inside the system instead of two hours behind it.
When real time actually matters.
When the lag between an event and a decision costs money or opportunity. A pipeline that went quiet ten minutes ago is actionable; a pipeline that went quiet last Tuesday is a post-mortem. Real-time dashboards earn their complexity when operators run the business off them in the moment, not when they look at them once a week.
The architecture, in five pieces.
- Event source. The system of record emits structured events as they happen (CRM, ERP, product DB, external API).
- Stream layer. The events flow through a stream or change-data-capture layer, durable and replayable.
- Live store. Aggregated state lives in a low-latency store (Postgres with materialised views, ClickHouse, or similar).
- Push surface. The dashboard subscribes to changes via WebSocket or server-sent events, never polling on a timer.
- Observability. Latency from event to surface is instrumented and visible; operators trust the dashboard because they know how fresh it is.
What a real-time dashboard is not.
It is not a dashboard that polls a database every minute. Not a chart embedded from a third-party BI tool with a five-minute refresh. The freshness of the surface is a designed property of the architecture, not a setting.
“Real time is an architecture decision, not a refresh interval.”
Frequently asked.
- What is a real-time dashboard?
- A real-time dashboard is a live data surface that updates within seconds of the underlying event. It is designed for operators who need continuous awareness of what is changing in the business, not a weekly snapshot.
- When does a business need a real-time dashboard?
- When the lag between an event and a decision costs money or opportunity. Sales pipelines, operations metrics, production systems, customer support queues, anything where ten minutes of staleness is the difference between catching a problem and writing a post-mortem.
- What technologies does Morvion use for real-time dashboards?
- Postgres with materialised views or ClickHouse as the live store, change-data-capture or event streaming as the source layer, WebSocket or server-sent events on the surface, and type-safe Next.js or React for the operator interface. Architecture is chosen per use case, not by default.
- How long does a real-time dashboard take to build?
- Eight to fourteen weeks from kickoff to launch in a typical engagement, with a live preview on real data inside the first four weeks. A two-week Discovery Sprint at the start locks the source-of-truth layer and the freshness budgets per metric.