Can iDBQuery run inside my own VPC?
Yes, iDBQuery can run inside your own private VPC, deployed in your cloud account right next to your databases so your data never crosses your network boundary. You keep full control of networking, access, and storage, while getting the same plain-language chat and cited answers as the managed cloud version.
A private-VPC deployment puts iDBQuery inside the cloud account you already control.
- Data stays in your boundary. Because iDBQuery runs alongside your sources and queries them in place, query traffic never leaves your VPC. There is no copy of your data sitting in a vendor's cloud.
- Your networking rules apply. Security groups, private subnets, VPN, and existing access controls govern iDBQuery the same way they govern your other internal services.
- Same product, your infrastructure. You get the identical experience, connect sources, build one live model, ask questions, get cited answers, generate reports, and run the Analyst agent, just hosted where you decide.
This option suits teams whose security or compliance posture does not allow sensitive data to leave their environment, but who still want the speed of natural-language analysis. Because iDBQuery does not require a warehouse or external pipelines, the footprint inside your VPC stays lean.
We work with your team on the deployment so it fits your account structure, IAM, and network policies. Reach out to scope a private-VPC rollout for your organization.
Updated 2026-06-22