The usual assumption about isolated deployments is that you give up half the product. That is not the case here. An air gapped ioMoVo deployment runs with full feature parity.
What you keep
Archive and long term storage, including LTO tape workflows
In app document editing for Word, Excel, and PowerPoint
All native plugins, including Adobe, Avid, Microsoft 365, and Final Cut Pro
Mobile and desktop apps
AI processing, running against models inside your own boundary
What changes
The main difference is who is authoritative for identity and policy. In an air gapped deployment, your environment controls identity and governance rather than ioMoVo's own identity layer. Your directory, your groups, and your policy stack stay in charge, which is normally the reason you chose an isolated deployment in the first place.
Model updates, platform updates, and any content you want to bring in all arrive through whatever transfer process your environment already uses. There is no automatic outbound call to fetch them.
AI without an internet route
Because there is no path out, the models run on hardware inside your environment. Nothing about a prompt, an asset, or a generated result leaves your boundary. This is the part that matters most to regulated and sovereign customers, and it is worth confirming the specific model set you need during planning rather than after deployment.
Planning notes
Two things are worth settling early with your ioMoVo contact: the hardware sizing for the AI workload you expect, and the update process your security team will accept. Both are easier to agree before the deployment than after.