Where does my data live when I use iDBQuery?
Where your data lives depends on the deployment you choose. With iDBQuery's cloud, sources are queried in place under read-only access; in your own VPC, everything runs inside your network; and on the Desktop app or air-gapped deployment, your data never leaves your machine or environment at all.
iDBQuery is designed so you control where your data sits, and it's the same product across every option:
- Cloud: iDBQuery connects to your sources with read-only credentials and queries databases in place. Uploaded files are indexed for querying. Your data isn't sold or used to train any AI model.
- Your own VPC: iDBQuery runs entirely inside your cloud environment, so processing and storage stay within your network boundary and your existing controls apply.
- Desktop app: a fully local version where connecting, ingesting and querying all happen on your own machine — nothing leaves the device.
- Air-gapped: for the strictest environments, iDBQuery can run with no external connectivity at all, keeping every byte inside your perimeter.
Across all of these, iDBQuery only reads from your sources and never writes back to them, and answers stay cited to your own records. The Embedded SDK lets you put the same querying capability inside your own application while keeping data local. If data residency or geographic control matters to you, the deployment model is the lever — you pick where iDBQuery runs, and your data follows.
Updated 2026-06-22