· 4 min
Air-gapped image AI is practical now
An air-gapped image workflow is a series of controlled transfers, not just a workstation with Wi-Fi turned off. The team still needs a safe way to approve model files and software, move inputs to the machine, review outputs and return approved deliverables. Design those boundaries before loading client material.
Separate preparation from production
Use a connected preparation machine to retrieve approved installers, model checkpoints, plugins and documentation. Record their source, version, checksum where available, license and intended use. Have an owner review that package, then transfer it through the studio’s approved media process. The offline workstation should run from a known set of files, with a clear list of what is installed and who can change it.
On the production side, separate client source assets from working files and final exports. Assign access to named users, keep a simple job manifest, and record which model and workflow produced each approved output. A local file browser or desktop cache can expose a client image to other accounts on the same machine, so include operating-system accounts, shared folders and backups in the access plan.
Plan updates and exceptions
“Air-gapped” may mean fully disconnected, or it may mean controlled access to a limited network. State which boundary applies. If the workflow must be fully offline, define how security fixes, model updates and license changes are checked and transferred. If a temporary network connection is allowed, specify who approves it, what destination is reachable and how the transfer is logged. Never improvise an update on the machine during a client job.
Before moving a project into the offline room
- Confirm the client has approved the source files and the planned creative use.
- Verify the required software, models and adapters against the approved package list.
- Test input, export and review steps with non-sensitive files.
- Document the removable-media route, custody owner and cleanup date.
- Keep a recovery plan for a failed workstation or corrupted project disk.
A fully disconnected machine can still have weak accounts, copied artifacts or unclear retention. The NIST Privacy Framework provides a voluntary way to frame data processing and privacy risks; pair that discussion with the studio’s security controls and client terms. For end-to-end transfer boundaries, read no-upload pipeline design; for the human approval step, see batch quality gates. Learn about services or contact.