Trust Center: know where the data goes and who controls it

iNut publishes the edge deployment principles that engineering teams can check before buying: data location, network path, access, backup, and support boundaries.

DISCLOSE THE PATHThis is not a certification. It is how we describe and hand over a system.

Trust starts with a concrete configuration

Each project should close the points below in its diagram, handover record, or support scope. Items marked project-scoped are not default promises for every site.

Data ownership

The iNut Edge architecture prioritizes keeping data, logic, and interfaces close to the operation; the final storage location is decided in the project design.

Platform principle

Self-hosting

iNut Datalogger / iNut PC can run the SCADA and storage layer on site; operational data does not have to move into a closed cloud.

In the architecture

Network path

LAN, WiFi, 4G, P2P, and Mesh are selected for the real site; outbound paths and loss-of-network behavior belong in the diagram.

Project-scoped

Access control

Roles, view/control permissions, and operating accounts should be configured per system; sharing one account is not the default.

Technical source

Backup & retention

Retention, backup location, and recovery steps must be agreed with the customer's IT team; iNut does not guess the owner's retention policy.

Scope to close

Updates & support

Firmware, configuration, maintenance windows, response times, and escalation are written into the delivery package or SLA when requested.

Support package

Read the architecture, technical notes, and policy

The Trust Center does not replace technical documents or a contract. It is a map to the right source before a decision is made.

Want to know how your system would be handed over?

Share the network diagram, PLC/device list, and access requirements. iNut will answer with architecture, responsibility boundaries, and acceptance checkpoints — not just “it is secure.”

Request an architecture review