Air-gapped deployment
Definition
Running software in an environment with no network route to the internet, so every dependency it needs must already be inside the boundary.
Air-gapping is common in defence, critical infrastructure, some healthcare estates and any environment where the threat model includes exfiltration rather than only intrusion. Getting anything in means media and a documented process, not a package manager.
The requirement quietly disqualifies a great deal of commercial software, and licensing is usually the reason rather than functionality. Any product that validates its licence against a vendor endpoint — at startup, or periodically — simply cannot run there. Offline activation has to be a design decision made early, not a flag added later.
Updates work the same way: they arrive on media, on your schedule. Which means the version you install has to keep working indefinitely, not until a subscription check fails.
In Doconut
Licensing resolves a local .lic file through options.LicensePath or Viewer.DoconutLicense(path). There is no activation call and no runtime revalidation, so rendering, conversion and licensing all work with no outbound connectivity. Archive the DLLs alongside the licence — a licence is tied to a version range.
Related terms
Document viewer SDK
A library you embed in your own application so it can display documents, as distinct from a hosted service you upload documents to. The SDK runs inside your process; the service runs inside somebody else's.
Web farm deployment
Running one application across several servers behind a load balancer, so consecutive requests from the same user may be handled by different machines.
Office interop (server-side automation)
Driving Microsoft Office from code to open or convert documents. It works on a desktop and is explicitly discouraged on a server, by Microsoft as well as by everyone who has tried it.