Live Dashboard

Summary

Lux Sync can power live dashboards where backend jobs, services, edge workers, or metric collectors publish current state and browser viewers receive updates without polling and without a message queue stack.

Buyer phrase: “I need dashboards to show the current operational state immediately, but I do not want Kafka, RabbitMQ, AppSync, or a custom realtime backend just to push small state updates.”

Buyer Problem

Teams often build dashboards for operations, finance, support, logistics, ML jobs, or SaaS control planes. The dashboard usually needs the latest state, not a durable replay of every historical event. Common examples include current throughput, active incidents, queue depth, workflow progress, deployment status, or service health.

Without Lux, buyers typically choose one of three heavier paths:

• polling a REST endpoint every few seconds, which adds lag and waste;
• pushing events through a queue or stream system, which adds operational weight;
• adopting a hosted realtime database or GraphQL subscription system, which can add vendor coupling and data-path hops.

Lux provides a buyer-deployed broker for current state synchronization. Producers write the current dashboard state to Lux. Viewers subscribe over WebSocket and receive the latest state as it changes.

Lux Architecture

The buyer runs the Lux broker close to the application workload. The dashboard app uses the Lux SDK or direct HTTP/WebSocket calls.

Data path:

1. Metrics or service agent computes the current dashboard state.
2. Agent writes JSON to PUT /api/lux/dashboard-main.
3. Lux stores the active state in broker memory.
4. Lux broadcasts the new state to WebSocket subscribers.
5. Browser dashboard updates without polling.

Voxell is not in the dashboard hot path for buyer-deployed brokers.

Example State

{
  "metric": "orders_per_second",
  "value": 42,
  "source": "metrics-agent",
  "summary": "orders_per_second=42"
}

Implementation Shape

Producer:

curl -X PUT "$BROKER/api/lux/dashboard-main" \
  -H "Authorization: Bearer $LUX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data":{"metric":"orders_per_second","value":42,"source":"metrics-agent"}}'

Browser:

import { lux } from './lux.js';

const dashboard = lux('dashboard-main', {
  endpoint: `${broker}/api/lux`,
  websocketUrl: `${wsBroker}/api/lux/stream/dashboard-main`,
  apiKey,
  realtime: true
});

await dashboard.load((state) => renderDashboard(state));

AWS Estate Proof

Scorecard: /mnt/data/ubuntu_data/code/lux/artifacts/usecase-scorecard-aws/20260617T221800Z/scorecard.md

Proof string: orders_per_second=42

Result:

• CLI proof: PASS
• Browser Playwright proof: PASS
• PUT ack observed from external operator machine to AWS EC2: 153.624 ms
• WebSocket delivery observed from external operator machine to AWS EC2: 477.867 ms

Timing boundary: this external AWS estate timing includes public network latency. It proves demo UX behavior, not the core broker hot-path latency claim.

Customer Data Handling

For buyer-deployed brokers, dashboard payloads remain in the buyer environment. Voxell stores only Marketplace entitlement/license/support metadata for activation and support. Dashboard state does not need to transit Voxell.

Good Fit

Use Lux for:

• operational dashboards;
• real-time business metrics;
• deployment/status boards;
• support or incident control panels;
• live job progress views;
• lightweight admin screens that need current state.

Poor Fit

Do not use Lux alone as:

• a historical time-series database;
• a durable event replay system;
• an analytical warehouse;
• a compliance audit log.

Lux can complement those systems by projecting the current state to viewers.

FAQ

Can Lux replace polling for dashboards?

Yes. Producers publish state updates to the Lux broker, and dashboard clients subscribe over WebSocket. The dashboard can update as state changes instead of polling repeatedly.

Does Lux require Kafka or RabbitMQ for a live dashboard?

No. Lux is designed for active-state synchronization without Kafka, RabbitMQ, AMQ, or another queue layer in the hot path.

Does Voxell see my dashboard data?

For buyer-deployed brokers, the dashboard sync payloads stay inside the buyer environment. Voxell only needs control-plane records such as entitlement, license, activation, and support contact metadata.

Is this a durable metrics database?

No. Lux synchronizes current active state. Buyers should keep durable metric history in their existing database, warehouse, time-series store, or event platform.