On-Prem Deployment
Sensors live on your local network: devices publish MQTT to an on-site hub gateway that buffers telemetry locally. Cloud uplink from the hub is in development — direct device-to-cloud publishing is the supported path today. Self-hosted platform delivery is not yet offered, and the Unreal client keeps working offline from its last-known-state cache.
Architecture
- DevicesLocal Wi-Fi network
- Hub GatewayOn-site MQTT · local buffer
- Cloud SyncPlanned · batched uplink
- UE5 TwinOffline cache · last-known state
- DevicesLocal Wi-Fi network
- Hub GatewayOn-site MQTT · local buffer
- Cloud SyncPlanned · batched uplink
- UE5 TwinOffline cache · last-known state
Capture happens on your local network — the hub buffers telemetry on-site, and its cloud uplink is in development. For enclosed, fully isolated sites, the pipeline is scoped per engagement; the Unreal client keeps working from its last-known-state cache either way.
Security Model
Credentials are held in OS-native secure storage; devices publish on your local network, and the twin cache is a local SQLite database.Update Policy
Platform updates are managed by Twinise in the cloud; the offline client works from its last sync.Data Ownership
The offline cache keeps last-known twin state locally on the client machine.Licensing
On-premise licensing is not yet offered; Twinise is delivered as a managed cloud platform. Talk to us about on-premise requirements.
Request Architecture Review