Free Lesson
Find the telemetry your air-gapped AI is still sending
30 min
Oct 8, 2026 11:00 AM
By continuing, you agree to Maven's Terms and Privacy Policy.
What you'll learn
Check the three properties an air gap actually requires
Isolated weights, disabled telemetry, controlled updates. Most deployments hold two and claim three.
Find outbound traffic your stack sends without being asked
Updaters, crash reporters, and a dependency three levels down with analytics on by default.
Test whether your deployment survives losing its registry
Cut the mirror and run a full deploy. Whatever breaks was never controlled, it was only reachable.
Why this topic matters
Most teams running self-hosted AI believe it is isolated. Almost none have checked, because the check is not obvious and nothing fails when it is skipped. The weights are usually fine. What leaks is a crash reporter nobody chose, an
updater nobody disabled, or a dependency three levels down with analytics on by default. Your auditor is unlikely to test this claim, which is exactly why you should test it first.
