Federal and defense environments demand air-gapped deployment. The cloud is not an option. The internet is not an option. Even DNS resolution to external hosts can be a non-starter. We've built Innfini to run in these environments. Here's what changes.
What still works
Most of Innfini doesn't care about the internet. The object graph, the event backbone, the connector layer, the edge runtime — all of these operate on local infrastructure. The model gateway can serve pre-deployed models locally. Agentic orchestration runs entirely on-prem.
What needs different patterns
Model updates
Models can't pull from a remote model registry. Updates ship as signed artifacts through air-gapped media. We support the oras OCI artifact format for this — the same patterns federal agencies already use for container distribution.
License validation
License keys must validate without phoning home. We use offline cryptographic license tokens with limited time-to-live and rotation through the same air-gap media channel.
Telemetry
No telemetry leaves the air-gapped boundary. Operational telemetry is captured locally and can be exported on customer request through the same secure channels.
The hard part
It isn't any one technical change. It's the operational discipline of every team treating "the internet doesn't exist" as a first-class constraint, not an afterthought.
What you give up
Continuous improvement loops slow down. The platform updates on the customer's cadence, not ours. Model retraining requires customer-side ground truth. The trade-off is sovereignty — and for the customers who need it, it's the only option that exists.