Does iDBQuery support VPC peering and private networking?

Private networking ensures iDBQuery talks to your databases over internal paths rather than public endpoints.

• In your VPC - deploy iDBQuery inside your own cloud account so it sits on the same private network as your data.
• Peering and private links - connect to sources in other VPCs or accounts through peering or a private link, keeping traffic off the public internet.
• No public exposure required - your databases can stay in private subnets with no internet-facing endpoint; iDBQuery reaches them internally.
• Query-in-place - iDBQuery runs SQL against your live sources rather than bulk-exporting them, so private networking protects the actual data path, not just a copy.

For example, an analytics team can peer the iDBQuery VPC with the VPC holding their production read replica, so queries flow over private addresses that never leave the cloud provider's backbone. This is a direct benefit of iDBQuery's deployment model: because it can live in your VPC or fully air-gapped, network isolation is native rather than an add-on. Combined with encryption in transit and at rest, RBAC, and IP allow-listing, private networking means both where the traffic goes and who can send it are under your control. For the most sensitive environments, an air-gapped install removes external connectivity entirely. Contact us to design the peering topology for your accounts.