Air-gapped deployment for RubusNode

No required outbound dependency

Local registries and broker paths mean the control plane and its Non-GMS/AOSP MQTT push path can operate without a required outbound internet connection, for environments where that isolation is mandatory.

When air-gapped fits

Air-gapped deployment is for environments where network isolation is a hard operational or regulatory requirement — not a convenience choice. It carries the most operational ownership of any deployment model.

• Local registries and broker paths, no required outbound internet dependency
• Same IAM, PBAC, approvals, and hash-chained audit model as every deployment path
• Highest operational ownership — plan for update and patch distribution inside the isolated boundary

Planning an air-gapped rollout

Air-gapped environments need a clear plan for how updates, patches, and Android app distribution reach the isolated boundary. Talk to our team early in your evaluation to plan this correctly.