How do I connect an on-prem database behind a firewall to iDBQuery?

For a database behind a corporate firewall, the answer isn't to expose it — it's to bring iDBQuery inside the perimeter with it.

• Deploy where the data is. iDBQuery runs in the cloud, your own VPC, or fully air-gapped. Put it on your network (or the same segment as the database) so it connects over private networking — no inbound firewall rule, no public endpoint, no data egress.
• Least-privilege connection. Provide a read-only user and standard connection details (host, port, database). iDBQuery introspects the schema and applies its semantic layer to interpret naming.
• Ask in plain language. The database joins your one live queryable model; iDBQuery writes the SQL, runs it locally, and returns answers cited back to the exact source rows.

Because iDBQuery queries in place rather than copying your data out, nothing has to leave the building — a fit for regulated, offline, or sovereignty-sensitive environments. For the strictest cases, the air-gapped deployment and the Desktop app / Embedded SDK keep everything local with no external calls. You can still combine the on-prem database with other in-network sources — a second database, a warehouse, a folder of files — in a single question, one model, no pipeline. Encryption in transit and at rest plus RBAC apply throughout.