Every action justified
The twin ties each setpoint to the perception and simulation that justified it.
Security & integration
Autonomy your OT team can approve.
Clinkum overlays your existing control system, runs at the plant edge, and writes only bounded setpoints, under least-privilege segmentation, with a full audit trace of every action.
100%
Actions traceable
0
Rip-and-replace
Edge
Real-time control locus
OPC UA
Open integration
Grounded, bounded, auditable.
Envelopes, not free rein
Agents write only within safe, operator-defined envelopes, per loop.
Least-privilege OT
Deployed in a segmented OT zone with least-privilege access.
Full trace
Every recommendation and action is logged and reviewable.
Deployment
Runs at the plant edge.
Real-time control lives on a plant edge appliance, not in the cloud. If the uplink drops, autonomy keeps running locally; the cloud handles management and fleet coordination only.
- Edge appliance owns real-time control.
- Local operation if the link drops.
- Cloud for management and fleet, not control.
Control locusedge
Cloud rolemanagement
Link losskeeps running
Data residencyon-prem
Integration
Open protocols, your systems.
Clinkum connects to your DCS, APC, analyzers, CEMS, and historian via open OPC UA and Modbus. It overlays what you have instead of replacing it.
- OPC UA / Modbus to DCS and APC.
- Analyzer, CEMS, and historian connectors.
- Read-only fallback at any time.
DCS / APCOPC UA
Analyzersconnected
CEMSconnected
Historianread/write
The security spec.
Network
Segmented OT zone; no inbound control from the internet.
Access
Least-privilege, role-based, with SSO and per-loop permissions.
Control writes
Bounded setpoints only; operator pause and hand-back per loop.
Audit
Every recommendation and action logged with its justification.
Data
Process data stays on your infrastructure by default.
Resilience
Edge-local operation on link loss; graceful degradation on sensor loss.
What we commit to.
- Segmented, least-privilege OT deployment
- No inbound control paths from the public internet
- Bounded setpoint envelopes with per-loop hand-back
- Full audit trace of recommendations and actions
- On-prem data residency by default
- Graceful degradation on sensor or link loss
- Read-only fallback available at any time
- Role-based access with SSO
Shadow first, then closed-loop.
Connect
Integrate read-only via OPC UA / Modbus; nothing is controlled yet.
Shadow
Agents recommend while operators run; accuracy is proven on your data.
Bound
Define safe envelopes and per-loop permissions with your OT team.
Close the loop
Enable bounded autonomy per loop, with hand-back always available.
Cloud-control vs. edge-resident
Cloud-dependent control
- Real-time control in the cloud
- Stops if the link drops
- Broad access to the OT network
- Opaque, unlogged actions
- Data leaves the plant
Clinkum edge-resident
- Real-time control at the edge
- Runs locally on link loss
- Least-privilege, segmented access
- Every action logged and justified
- Data stays on your infrastructure
Security questions
No inbound control paths come from the public internet. Real-time control runs in a segmented OT zone on the plant edge.
The soft-sensors widen their uncertainty and reduce autonomy or hand back before acting on unreliable inputs.
On your infrastructure by default. The cloud is used for management and fleet coordination, not for holding your process data.
Yes. Autonomy is per-loop and can be paused instantly, with a read-only fallback available at any time.
Related
Bring your OT team.
We'll walk through segmentation, envelopes, and audit with your security and controls engineers.