01
Work visually with industrial data
Organise work as Notebook → Section → Page. Add live blocks, typed asset models and relationships such as FEEDS, CONTROLS and MEASURES.
CANVAS + GRAPH + CONTEXTThe 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 / UNSOPC-UASQLMODBUSOPEN PROTOCOLIPC-CFXIPC-HERMES-9852RS232RESTFILESCAMERAS
One working surface
Data, context and output on the same canvas.
Place a source, query, register, machine, camera or document. Wire it. What you build is simultaneously a dashboard, a data-flow definition and the exact context an AI reasons over.
02
Connect what is actually on site
Read MQTT, OPC-UA, SQL, Modbus, Open Protocol, CFX, Hermes, REST, watched folders, cameras and serial machines through TCP bridges.
READ-ONLY CONNECTORS03
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 TRANSPORTSExplicit 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 uses permission-aware tools and holds no hidden copy of your workspace data.
✓Durable page memory, reusable skills and budgeted multi-step investigations stay visible and controlled.
✓Use Anthropic, OpenAI, Azure, OpenRouter, an OpenAI-compatible endpoint or local Ollama inference.
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.
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
From signals to operational knowledge
More than a dashboard over MQTT.
UNS Navigator carries plant context from the raw signal through to the operator surface, the knowledge behind it and the systems that consume the result.
Give raw signals a typed industrial model.
Define an asset type once, bind each field to MQTT, OPC-UA, Modbus, SQL or a static source, then reuse the same apps and detectors across instances. Opt selected sources into TimescaleDB history with retention, compression, rollups and safe pruning.
Capture what the topic tree cannot tell you.
Turn the namespace into a graph of typed relationships and operator notes. Feed it an SOP, Online Work Instruction or machine manual and it proposes reviewable knowledge with page-and-sentence citations. A person accepts every addition.
Ship operator surfaces from the same data.
Generate live dashboard apps from a curated page, collect them in an App Hub and run a fullscreen Present rotation for control-room screens. Standalone exports use revocable read-only capability tokens.
Use the identity your plant already has.
Sign in with local accounts, Windows / Active Directory or Microsoft Entra. Viewer roles are enforced server-side, while separate audit and activity logs show deliberate actions and live system behaviour.
MQTT · OPC-UA · SQL · MODBUS-TCP · OPEN PROTOCOL · IPC-CFX · IPC-HERMES-9852 · REST · FILE INGEST · RS232 VIA TCP BRIDGE · CAMERAS · MCP
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.
01
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.
02
Fail-closed sensitive connectorsSerial bridges, watched folders and outbound REST stay disabled until an operator explicitly allow-lists a target.
03
Credentials stay server-sideSecrets are stripped from API responses, pages, exports and logs. Blocks store only a connection reference.
04
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
}
✓ 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. Every feature is available for evaluation. 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
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. Plant-facing source connectors are read-only. Deliberate egress paths are narrow, named and opt-in: MQTT publish, its own history tables and notification webhooks. It has no PLC or equipment command path.
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.
Can it learn from our SOPs and work instructions?
Yes. Give the knowledge graph an uploaded document, a watched file or rows from a document database. It proposes relationships and notes with page-and-sentence citations, and a person accepts or rejects each one.
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.
Can staff use our Microsoft sign-in?
Yes. Microsoft Entra sign-in sits alongside local accounts and Windows / Active Directory. Viewer permissions are enforced by the server.
What hardware does it need?
A Docker-capable host. UNS Navigator is verified on x86-64 and ARM64, including single-board hardware for line-level or cabinet deployments.