Does iDBQuery offer EU data residency and hosting?

Yes. iDBQuery can be deployed so that your data stays in the EU, either in an EU-region cloud deployment, inside your own EU-based VPC, or fully on-premise. Because iDBQuery queries your sources in place, the data itself never has to leave the jurisdiction where you host it.

Data residency is about keeping data within a chosen jurisdiction, and iDBQuery's deployment model lets you pin it wherever you need.

  • EU-region deployment - run iDBQuery in an EU location so processing and any stored configuration stay in-region.
  • Your own VPC - deploy inside your EU-based cloud account, keeping everything within infrastructure you already control.
  • On-prem or air-gapped - host entirely within your own EU facilities for the strictest residency requirements.
  • Query-in-place - iDBQuery runs SQL against your sources rather than exporting them, so the underlying data stays put in the region you host it.

For example, a company that must keep customer data in the EU can deploy iDBQuery in an EU region or its own EU VPC, so neither the data nor the queries touch infrastructure outside the bloc. This flexibility is a direct consequence of iDBQuery's architecture: because it deploys in the cloud, your VPC, or air-gapped, residency is a deployment choice rather than a limitation. Residency pairs well with an EU-focused setup for supporting your GDPR obligations, and with a Data Processing Agreement to document the arrangement - though residency and a DPA are architectural and contractual measures, not certifications. Encryption in transit and at rest and RBAC apply throughout. Contact us to plan an EU-resident deployment.

Updated 2026-06-22