Does iDBQuery need outbound internet access?
No, not necessarily. In an air-gapped deployment iDBQuery runs with no outbound internet access at all, using a locally hosted language model and internal data sources only. Cloud and VPC deployments do use network connectivity, but you control the egress and can restrict it to what your policy allows.
Whether iDBQuery reaches the internet depends entirely on how you deploy it, and full isolation is a supported design.
- Air-gapped - no outbound access whatsoever; the language model runs locally and iDBQuery connects only to internal sources, with no telemetry or callbacks.
- On-prem or VPC - you decide the egress rules, so connectivity can be limited to specific internal endpoints and nothing more.
- Cloud - uses network connectivity, protected with encryption in transit, and still governed by your access controls.
- You hold the controls - IP allow-listing and private networking let you constrain both inbound and outbound paths.
For example, a secure facility can run iDBQuery on hardware with no route off the network, and analysts still get plain-language answers cited to source rows, because the intelligence runs inside the boundary. This ability to operate with zero outbound access is a defining feature of iDBQuery's architecture rather than a special mode bolted on - it is why the product suits defence, healthcare, and financial environments where external calls are prohibited. Even in connected deployments, query-in-place means iDBQuery is moving answers, not shipping your database out. If your requirement is 'no data or prompt may leave the network', the air-gapped path meets it directly. Contact us to plan a deployment that matches your egress rules.
Updated 2026-06-22