Is your feature request related to a problem?

No

Describe the solution you'd like

Background

Are there any plans to support SSH tunneling for additional database types?

In many real-world deployments, databases are not exposed to the public internet for security reasons and are only accessible through a bastion host or internal network. Currently, users often have to rely on manual ssh -L port forwarding, which can be inconvenient to manage and maintain.

Why This Matters

Using SSH tunnels would provide several benefits:

• Avoid exposing databases directly to the public network
• Improve overall security posture
• Simplify access to private/internal databases
• Reduce operational complexity compared to manually managing ssh -L sessions
• Better support for production environments where private networking is common

Suggested Capability

It would be great if the application could support built-in SSH tunneling for more database connections, for example:

• Configure SSH host/user/key directly in the connection settings
• Automatically establish and manage the tunnel
• Support password and private key authentication
• Reconnect handling and connection health checks

This would significantly improve usability for self-hosted and enterprise environments.

Thanks for considering this feature.

Additional context

No response