Engineering · Published May 26, 2026
Notes on Offline, Air-Gapped Deployment
Factory, government and large enterprise networks often cannot reach the internet, so deployment must be designed for it.
Our first offline deployment followed the usual process and lost a full day on site: dependencies would not install, fonts failed to load, maps showed nothing. Air-gapped environments need an entirely different checklist.
Six things to confirm before go-live
OS version and CPU architecture, especially on domestic platforms where images and dependencies must match.
Who provides the database and middleware, which versions, and whether administrator credentials are available.
A complete offline bundle: language runtimes, fonts, map tiles and frontend assets.
Time sync and certificates; clock drift on an intranet invalidates tokens.
Disk space and permissions for logs and backups.
Whether remote support is possible on site, or only phone calls.
What we do now
Everything is bundled into one offline installer and rehearsed end to end on a clean machine before delivery.
Deployment scripts check prerequisites and fail with a clear message instead of leaving people guessing on site.
Offline deployment tests preparation, not technical depth. The finer the checklist, the calmer the site.
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →