Can I connect a database to iDBQuery over an SSH tunnel?

If your database lives in a private network or subnet, you don't have to open it to the internet for iDBQuery to query it. iDBQuery can connect over an SSH tunnel: it opens an SSH session to a host you control, then forwards the database connection through that encrypted channel.

What you provide:

• SSH host and port of a reachable jump machine.
• SSH credentials — typically an SSH key.
• The private database host/port as seen from inside the network.

iDBQuery then talks to the database as if it were local to the SSH host, and your query traffic stays encrypted end to end. The database's own firewall can keep denying all public traffic.

This matters for security-conscious teams: your production or analytics database is never publicly listed, and you can pair the tunnel with a read-only user so iDBQuery can query but never modify data. For even tighter setups, deploy iDBQuery inside your own VPC or on-prem so it's already on the private side of the network.

Example: a company keeps its Postgres in a locked-down subnet. They give iDBQuery an SSH key to the bastion, and analysts start asking cited questions of production-safe data the same day — no ports opened, no data copied out. It's the same experience as a direct connection, just reached securely.