Is iDBQuery single-tenant or multi-tenant?
iDBQuery can be deployed single-tenant, giving you a dedicated, isolated instance in your own VPC or on-premise where no other customer shares the infrastructure. This is the recommended option for regulated or high-sensitivity environments, since isolation is delivered by architecture rather than by shared-tenant configuration alone.
Tenancy is about whether your instance shares infrastructure with other customers, and iDBQuery gives you a genuinely isolated option.
- Dedicated single-tenant - deploy iDBQuery in your own VPC or on-prem so the application, data access, and, if you choose, the language model run on infrastructure only you use.
- Full isolation - there is no shared database of customer data to worry about, because your deployment is your own.
- Air-gapped extreme - for the strictest cases, run entirely offline with no external connectivity at all.
- Query-in-place throughout - regardless of tenancy, iDBQuery runs SQL against your live sources rather than pooling your data anywhere.
For example, a bank or defence organisation can run a single-tenant, on-prem iDBQuery so that isolation is structural - a property of where the software runs - rather than a permission setting in someone else's cloud. This is exactly why iDBQuery leads with architecture: instead of asking you to trust logical separation on shared infrastructure, it can put the whole system inside your walls. That isolation combines with RBAC, encryption in transit and at rest, and, for air-gapped installs, a locally hosted model, so nothing about your workload is co-mingled or externally reachable. The right tenancy depends on your risk and compliance needs. Contact us to design a dedicated deployment.
Updated 2026-06-22