Notes on Shipping Air-Gapped

Air-gapped is easy to claim and awkward to build. A platform that has never run without internet access tends to have assumptions buried in it, and they surface at the worst time. The usual ones, in the order we hit them. Package installs that reach out during first run. A licence check that fails closed. Time synchronisation pointed at a public pool. Font and map tile requests from the browser side that nobody notices until the page renders wrong on a network with no route out. Crash reporting that queues forever. Each is a small fix. The discipline is having somewhere to catch them, which for us means the build is exercised with no route to the internet at all, not with a firewall rule we can quietly relax. There are things you genuinely give up. Updates arrive as a signed bundle somebody carries in, not as a background download. Threat intelligence is only as current as the last import, so that import needs an owner and a schedule. Remote support means a screen share with your engineer driving, and every session is on your terms. For a lot of buyers this is a fair trade, and for some it is not a trade at all. If your logs cannot leave the country, a cloud platform with a regional data centre is still a platform that holds your data. Running it on hardware in a room you control is a different proposition, and increasingly it is the only one that clears review.