How do I deploy iDBQuery in an air-gapped environment?

An air-gapped deployment removes all external connectivity so iDBQuery operates entirely within your isolated network. The rollout typically follows a clear path.

• Prepare infrastructure - provision servers or VMs on your isolated network, sized to your data and user count.
• Transfer the package - bring the installation package in through your approved media or internal artefact process, since there is no internet download.
• Run the model locally - the language model runs on your own hardware inside the boundary, so no prompt or data is ever sent out.
• Connect internal sources - point iDBQuery at your on-network databases, warehouses, and file shares; it queries them in place.
• Apply access controls - wire up your internal identity provider for SSO, set RBAC, and enforce encryption in transit and at rest.

For example, a government analytics team can stand up iDBQuery on hardware with no route to the internet, host the model locally, and let staff ask questions of classified datasets that never leave the room. This is where iDBQuery's architecture is the whole story: because it is built to run air-gapped, there are no hidden callbacks, telemetry pings, or cloud dependencies to work around. Answers are still cited to source rows, so analysts can verify every figure offline. We provide an installation runbook and help validate isolation during setup. Contact us to plan an air-gapped rollout.