Can MonkeyCode run in an air-gapped network?
The project documents private and offline deployment, which is the basis for air-gapped operation, but a true no-egress setup requires mirroring models, packages, and updates inside the isolated network.
Important context
Offline deployment and strict air-gapping are not identical. Plan how models, package registries, license checks, and updates are supplied without outbound access, and verify current steps in the deployment docs.
| Documented | Private and offline deployment |
|---|---|
| Air-gapped needs | Mirrored models, packages, updates |
| Not identical | Offline vs strict no-egress |
| Verify | Current steps in deployment docs |
What to do next
Plan how models, registries, license checks, and updates are supplied without outbound access.