Data ownership
Set retention, backup, and data paths around your system policy.
Back to solutions
SELF-HOSTED IOT / DATA CONTROL
Self-hosted IoT: data, compute, and logic in your system.
Design the edge layer so operational data, access policy, and integration flow stay close to the environment you control — without depending on a closed cloud.
DATA IN YOUR HANDSLOCAL-FIRSTHANDOVER-READY
INUT / DATA IN YOUR HANDSLIVE
REFERENCE DATA PATH
01Field devices
02iNut Edge / Local runtime
03Store · Compute · Access
04MQTT · REST/JSON · Local API
01 / ARCHITECTURE
Control is part of the architecture.
Self-hosted is more than installing software on site. It defines where data is kept, which network carries it, and who owns the contract.
01Field devices
02iNut Edge / Local runtime
03Store · Compute · Access
04MQTT · REST/JSON · Local API
05System owned by your team
02 / WHERE IT FITS
When data policy belongs in the design.
A fit for factories, buildings, and integration teams that need data, operating logic, and access to remain within their control.
Network choice
LAN, WiFi, 4G, P2P, or hybrid connectivity around the real site.
Open contract
Connect through MQTT, REST/JSON, or a Local API agreed by both teams.
03 / NEXT LAYER
Explore control and architecture boundaries.
04 / START FROM THE CURRENT STATE
Discuss data ownership Want data to stay in your team’s hands?
Share network policy, data points, and the systems to integrate. iNut will turn ownership requirements into a handover-ready edge layer.
FAQ / CLARITY BEFORE CONTACT
Questions teams ask before an architecture review.
Does self-hosted IoT mean no Internet?
Not necessarily. The network path follows the site; the key is a clear control boundary for operational data and logic.
Does iNut lock data into one platform?
The architecture is built around handover-ready protocols and APIs; endpoint, authentication, and mapping are agreed per survey.