Self-hosted, segmented and disconnected deployment options
Planned deployment options emphasize explicit dependencies and customer control.
Self-hosted software
Install on customer-approved infrastructure with an agreed administration and support responsibility matrix.
0:00
/0:10
Close view of server racks with status lights.
Turnkey appliance
Evaluate integrated local hardware, sensors and an operator interface.
Segmented edition
Plan operation on a separate network segment with controlled boundaries. Reporting, support and updates use only approved paths, such as a maintenance gateway or controlled media. Segmentation is not air-gapping.
Disconnected edition
Plan local inference, identity, alarms, storage and update verification. Live remote reporting is unavailable while strictly disconnected.
Managed on-premises
Optional maintenance or analyst support uses explicitly authorized access and a defined scope.
Planned options Deployment choices and what each depends on
Self-hosted software
Runs on
Customer-approved infrastructure
External reporting
Optional, customer-controlled
Support and updates
Under an agreed responsibility matrix
Turnkey appliance
Runs on
Integrated local hardware, sensors and operator interface (under evaluation)
External reporting
Optional, customer-controlled
Support and updates
Scope defined with the customer
Segmented edition
Runs on
A separate network segment with controlled boundaries
External reporting
Only through approved, controlled paths
Support and updates
Through an approved maintenance gateway or controlled media
Disconnected edition
Runs on
Local infrastructure with no external network connection
External reporting
None live while strictly disconnected
Support and updates
Local, with controlled transfer verified at the destination
Managed on-premises
Runs on
Customer site, with optional maintenance or analyst support
External reporting
Optional, customer-controlled
Support and updates
Explicitly authorized access with a defined scope
Self-hosted, segmented and air-gapped are different things. A strictly disconnected system cannot also send live reports.
Prove independence
Avoiding mandatory cloud inference and licence checks is a design requirement to test, not a completed implementation claim.
