Skip to content
Hiiko

Security and deployment

The plant network stays closed.

OT and IT can evaluate Hiiko without opening inbound access, without a mandatory cloud for operational data, and without a path from AI to equipment.

Read-only to plant control

No code path from a chat prompt, a dashboard, or a report to a PLC. The assistant can draft a view. A person applies it. Equipment is never the target.

Nothing inbound to the plant network

An edge collector in OT initiates one outbound connection to the core. Nothing analytics-related listens inside the machine network.

The core runs where the plant decides

On-site or in a DMZ, in an existing cloud account, or as a signed offline bundle. Same product. Operational data does not have to leave the site.

AI is a choice, not a dependency

A local model with nothing leaving the environment, a cloud subscription that only receives small retrieved snippets, or no AI at all. Trends, OEE, and alerts do not depend on a language model.

How it sits in the network

The plant-side rule never changes.

Toggle where the core runs and whether AI is involved. The edge still only talks outbound.

Plant floor · OT

PLCs · SCADA · documents

Edge

Collects & queues locally

One outbound connection — no inbound, ever

IT / your cloud · Core

Core — Your servers

Core runs in the plant IT environment, on-site or in a DMZ.

Dashboards & OEE

Plant map

AI — Local model

Runs inside the Core. Nothing leaves the environment.

Where the Core runs

AI, if needed

A picture worth forwarding to OT.

A pilot conversation, or a note to follow.