The gap above the broker

A UNS solves the plumbing. It doesn't solve the work.

The broker is up. Topics are structured. Data is flowing. Then the layer above the namespace turns into another custom build: a dashboard nobody maintains, a reporting project that takes a quarter, or a data lake that answers questions nobody asked.

The data is available and still nobody is using it, because available and usable are different problems.

MQTT / UNSSQLMODBUSOPEN PROTOCOLRS232 / RS485RESTFILES

One working surface

Data, context and output on the same canvas.

Place a source, query, register, machine or document. Wire it. What you build is simultaneously a dashboard, a data-flow definition and the exact context an AI reasons over.

Work visually with industrial data

Organise work as Notebook → Section → Page. Add live blocks and typed relationships such as FEEDS, MEASURES and DEPENDS_ON.

CANVAS + GRAPH + CONTEXT

Connect what is actually on site

Read MQTT, databases, Modbus, torque tools, REST endpoints, watched folders and serial machines through TCP bridges.

READ-ONLY CONNECTORS

Publish something others can consume

Expose a pipeline result over REST and, with one checkbox, as a scoped MCP tool an AI assistant can call directly.

ONE RESULT · TWO TRANSPORTS

Explicit AI context

AI that only sees what you show it.

An agent reads a block only when it is enabled, configured and in scope. Each gate can narrow context, never widen it. Reports identify the blocks used and cite them for factual claims.

✓NAV AI holds no workspace data; it must use permission-aware tools.

✓Writes return as proposals for human approval.

✓Use Anthropic, OpenAI, Azure or local Ollama inference.

UNS Navigator canvas with MCP tools, AI analysis, simulator, forecast and chart — MCP tools + gated analysis + honest forecast

Headless data products

Turn plant results into stable REST and MCP surfaces.

Typed, versioned pipelines run on manual, scheduled, streaming or event triggers. Dry-run traces every step and stubs every sink. Exposed results carry provenance and honest freshness.

✓Per-endpoint tokens are shown once, revocable and tightly scoped.

✓An endpoint outside a caller's rights is absent, not merely refused.

✓REST and MCP share the same stored result and envelope.

UNS Navigator pipelines converting simulator and MQTT results into REST and MCP endpoints — Pipeline result → REST endpoint + MCP tool

Explainable detection

Catch problems now. See the ones coming.

Anomaly detection reports the method, field, value and threshold that fired. Forecasting projects when a signal will cross a target — and refuses to invent a time when the trend is noisy, flat or heading the wrong way.

RANGE

Z-SCORE

MAD

RATE

FLATLINE

EWMA

UNS Navigator canvas with a complete SMT manufacturing flowchart — Process context on the same industrial canvas

Trust by construction

What it will never do to your plant.

UNS Navigator is designed to be additive. It reads existing systems and keeps every deliberate egress path short, named and test-pinned.

No PLC, SQL or equipment command pathConnectors are read-only. The product does not write to PLCs or source databases and does not command machines.

Fail-closed sensitive connectorsSerial bridges, watched folders and outbound REST stay disabled until an operator explicitly allow-lists a target.

Credentials stay server-sideSecrets are stripped from API responses, pages, exports and logs. Blocks store only a connection reference.

Generated and user code is sandboxedInline generated apps run isolated. User transforms run in a worker under a CSP with no network access.

Local-first deployment

Runs on your hardware. Genuinely.

One container, with optional TimescaleDB history and FalkorDB graph services. No cloud account, no phone-home and no network requirement for licensing.

Deployment profile

Containerised and air-gap ready

Verified on x86-64 and ARM64, including single-board hardware suitable for a cabinet-level deployment.

DOCKERARM64X86-64OFFLINE LICENCE

$ docker compose up -d
✓ navigator healthy
✓ data_dir mounted
✓ licence trial · 30 days
GET /health
{
  "status": "ok",
  "network": "local",
  "phoneHome": false
}

Start today, decide later

A full 30-day trial starts on first boot.

No key, account or internet connection. If the trial ends, the workspace becomes read-only rather than bricking: pages, models and history remain viewable and exportable, and already-deployed apps keep serving.

30-DAY OFFLINE TRIAL · WORKSPACE REMAINS ACCESSIBLE AFTER EXPIRY

Talk to us about a deployment →

Questions

Clear boundaries.

Is UNS Navigator an MQTT broker?

No. It connects to yours. The built-in simulator can also generate realistic streams when no broker or plant connection is available.

Does it replace SCADA, MES or a historian?

No. It reads them and provides the working layer above. History is available as an opt-in TimescaleDB service per source.

Will it write to PLCs or databases?

No. Source connectors are read-only. The deliberate egress paths are named and opt-in: MQTT publish, its own history tables and outbound notification webhooks.

What controls what the AI can see?

A block must be enabled, configured and inside the agent's scope. The report lists the exact blocks it used. Local inference through Ollama is supported.

What is MCP support for?

An exposed pipeline result can become a read-only MCP tool, allowing an external AI assistant to query curated plant results without direct access to the source system.