Air-gapped deployment

An air-gapped network is not an edge case for us. It is the environment the system was built inside.

What the system deliberately does not have

• No online licence check.
• No telemetry.
• No runtime asset fetching — fonts, libraries and icons are bundled into the build.
• No auto-update.

Each of those four would break the system on a disconnected network, so none of them is present in the first place — rather than being a configuration switch somebody could forget to turn off.

Transferring dependencies

The installation package contains all dependencies. There is no step at which installation reaches an external repository, so one transfer is enough.

Version updates

The same path: a new package crosses via controlled transfer and installs locally. Transfer frequency is your operational decision, and the patch schedule depends on it as much as it depends on window availability.

Vulnerability sources

With no internet access, the vulnerability list arrives as a file — an export from the scanner or from the security operations team — into a directory the system reads. There is no dependency on an online vulnerability database.

A file that cannot be parsed is not destroyed: it moves to a failures directory with a companion file explaining what failed, so it can be corrected and re-fed.