Can iDBQuery connect to a database that requires SSL/TLS?

Encrypting database connections in transit is a baseline security requirement for many teams, and iDBQuery supports it. When your database requires SSL/TLS, iDBQuery negotiates an encrypted connection so credentials and query results never travel in the clear.

Depending on your database's policy, you can:

• Require TLS — iDBQuery connects over an encrypted channel by default where the database mandates it (managed services like PlanetScale and Neon require TLS, for example).
• Verify the server — provide the CA certificate so iDBQuery validates the database's identity.
• Use mutual TLS — where supported, supply a client certificate and key.

This sits alongside iDBQuery's broader security posture: encryption in transit and at rest, a read-only user, query-in-place, and deployment in your own VPC, on-prem, or air-gapped. For private databases you can also combine TLS with an SSH tunnel or private link so the connection is both encrypted and never publicly exposed.

Example: a healthcare-adjacent company mandates TLS on every database connection. They point iDBQuery at their Postgres with the CA certificate, iDBQuery verifies the server and connects securely, and staff get cited answers without weakening any of the database's connection requirements. Your database's rules stay in force — iDBQuery meets them rather than asking you to relax them.