The short answer
Air-gapped AI is artificial intelligence, usually a large language model, installed on servers that have no connection to the internet or to any outside network. Everything the model needs is brought inside on purpose, and nothing it produces can leave except through a controlled channel. It is the standard for classified and defense work, and increasingly for critical infrastructure and finance.
A language model does not need the internet to work: once its files are installed, it answers on local hardware. The hard part is everything around the model, because most software quietly expects a connection. A successful air-gapped deployment finds and removes every one of those expectations before go-live.
What air-gapped means
An air gap is a deliberate separation between a system and every network it should not touch. In its strict form the gap is physical: no cable, no wireless link, no route out. In practice it also covers the procedures around the system: what may be carried in, who may carry it, and how it is checked.
It helps to place air-gapped AI against its neighbors:
- Public AI services run in a provider's data center and are reached over the internet.
- Private, on-premise AI runs on your own servers but may still connect out for updates, licensing or web search.
- Air-gapped AI runs on your own servers that never connect out at all.
Every air-gapped deployment is on-premise, but most on-premise deployments are not air-gapped. Moving from one to the other is mostly a matter of discipline, not of different models.
Who needs it
- Defense and intelligence. Classified networks are isolated by rule. AI on those networks has to live entirely inside them.
- Critical infrastructure. Power, water and industrial operators keep their operational networks separate from the internet to limit the damage an intrusion can do.
- Finance. Research and trading teams handling price-sensitive information increasingly work in enclaves with no outside line.
- Legal and advisory work on matters where even the existence of the work is confidential.
- Remote and mobile operations. Ships, forward bases, mines and offshore platforms that are disconnected for long periods, by circumstance rather than by rule.
What changes when the servers can never connect
| Function | Connected private AI | Air-gapped AI |
|---|---|---|
| Model updates | Downloaded when released | Brought in by controlled transfer, checked, then installed |
| Looking things up | Live web search | An offline copy of reference knowledge, plus internal documents |
| Licensing | Online activation and checks | Offline licensing, agreed before delivery |
| Monitoring | Vendor dashboards | Logs and alerts kept inside the enclave |
| Support | Remote access | On-site, escorted, or by exported logs reviewed outside |
The hidden dependencies that break first attempts
Most failed air-gapped installs fail on the first day, for the same reason: some component tries to reach the internet and stops when it cannot. The usual suspects:
- Model files fetched on first run. Many tools download models the first time they are used. In an enclave, every model has to be present before the system starts.
- License activation and periodic checks that expect to reach a vendor server.
- Telemetry and crash reporting that retry endlessly and fill logs or block startup.
- Software package managers that pull libraries from public repositories during installation.
- Web interfaces that load fonts, scripts or icons from public content networks, and render broken or empty without them.
- Certificate checks that try to confirm a certificate has not been revoked.
- Time synchronization pointed at public time servers, which matters for logs and authentication.
The fix is a rehearsal: build the complete system in a disconnected test environment that mirrors the enclave, run every workflow, and treat any attempt to reach outside as a defect.
Keeping it current without a connection
Models improve every few months, and an air-gapped system that is never updated falls behind. Updates need a routine that is boring and repeatable:
- Prepare outside. Assemble the new models and software on a clean system, and record what changed.
- Verify integrity. Check every file against the publisher's checksums and signatures.
- Scan and approve. Run the transfer media through your security process and record the approval.
- Stage and test inside. Install on a staging server in the enclave and run your own test set of real tasks.
- Roll out, keep the previous version. Promote to production and keep the old release ready for a rollback.
A quarterly cycle suits most organizations; some defense users update less often and validate more heavily.
What an offline model knows
A language model knows what it learned in training, up to the date its training data ended, and nothing after it. Connected systems hide this by searching the web. An air-gapped system cannot, so it needs two other sources of knowledge: the organization's own documents, connected with the same permissions people already have, and an offline copy of reference knowledge from the web, refreshed with each update cycle. With both in place, an air-gapped model can answer questions about current procedures, recent internal reports and technical material without ever touching a network.
Air-gapped AI checklist
- Every model, library and interface asset present on the servers before first start.
- Offline licensing agreed with every vendor in writing.
- All telemetry, update checks and outside calls disabled, then verified in a disconnected rehearsal.
- Local time source and local certificate handling.
- Access tied to the enclave's own directory, with roles and separation between matters or units.
- Logging and alerting that stay inside, reviewed by the enclave's own security team.
- A written transfer procedure for updates, with integrity checks and approvals.
- An offline copy of reference knowledge and connected internal documents.
- GPU capacity sized for the users and the models, with room to grow, because adding hardware inside an enclave is slow.
Common mistakes
- Testing on a connected network. Everything works in the lab, then fails in the enclave on day one.
- Treating the first install as the finished system. Without an update routine the system ages quickly.
- Forgetting knowledge. A model with no access to documents or reference material answers from memory alone, and its memory ends at its training date.
- Undersizing the hardware. In an enclave, more servers can take months to approve and install.
How lualdi.ai does it
lualdi.ai: AI that keeps working when the internet does not
lualdi.ai is a private LLM deployed on-premise, only on dedicated GPU servers inside large organizations, and built for defense, finance and large enterprise. Once a model is downloaded, lualdi.ai answers without a connection, using NVIDIA GPU acceleration where the hardware supports it.
Cloud features are off by default, every install sits behind its own passphrase, and each install is prepared for one client at a time. Its catalog of 24 models runs from a compact assistant for everyday work up to frontier-class reasoning and coding models, and use is unlimited: nothing is counted per question.
Two extensions run on the same servers with no connection at all. NOLAN keeps a searchable copy of the open web inside the deployment, so the models can look things up offline. GRIZZLY adds AI agents that carry whole tasks through, with sensitive actions waiting for a person's approval.
Questions
Can an AI model work without an internet connection?
Yes. A language model runs entirely on local hardware once its files are installed. What usually needs the internet is the software around it, such as licensing, updates and web search, and in an air-gapped deployment each of those is replaced with an offline equivalent.
How do you update air-gapped AI?
By controlled transfer: new models and software are assembled outside, checked against the publisher's checksums and signatures, scanned and approved, carried in, tested on a staging server inside, and only then rolled out, with the previous version kept for rollback.
Does air-gapped AI know about recent events?
Only what it learned in training, plus what you bring inside: the organization's own documents and an offline copy of reference knowledge from the web, refreshed with each update cycle.
Is air-gapped AI less capable than connected AI?
The models can be the same. The difference is in reach: no live web search and slower updates. With internal documents and an offline reference copy connected, most professional work is unaffected.
What hardware does air-gapped AI need?
The same as any private deployment: servers with AI-grade GPUs, sized for the models you run and the number of people using them at once. Size generously, because adding hardware inside a secure enclave is slow.
