SSH tunnels, terminal profiles, and database connections in one app.
Mongrel combines saved SSH terminal profiles, ProxyJump-style chains, local and remote port forwarding, SFTP/SCP, and per-connection database tunneling where supported. Database tunnels are stored on each database profile; reusable SSH profile references currently serve terminal and API Client workflows.
Linux x86-64 · macOS Apple silicon · Windows x64 and ARM64
// Why a GUI
The tunnel was never the point; the database behind it was.
Supported database profiles own their SSH tunnel lifecycle, so you can save a bastion with the database connection instead of maintaining a separate ssh -L process. Full SSH terminal profiles are a separate surface with jump-host chains and explicit local or remote forwards. Keeping that distinction clear avoids promising profile reuse the product does not implement.
// What ships
Everything around the tunnel, in one place.
Saved SSH terminal profiles
Store host, user, authentication, jump-host, and forwarding settings in reusable SSH terminal profiles.
Jump-host chains
SSH terminal profiles support ordered ProxyJump-style chains, with loop validation and native or system-SSH transports.
Local credential handling
Passwords and key passphrases use the OS credential facility when available; private keys remain files and their paths stay machine-local.
A full SSH terminal
SSH and local shell sessions include logging, search, triggers, and quick commands; Mosh uses a user-installed client, and SSH profiles support local or remote forwarding.
Secure file transfer
Dual-pane SFTP/SCP supports upload, download, recursive transfer, progress, cancellation, and SCP fallback.
Database SSH tunneling
Supported database connection forms include their own saved SSH tunnel settings. These are per connection, not shared terminal-profile references.
// Honest tradeoffs
Honest tradeoffs, because there are some.
OpenSSH remains more scriptable and may already cover your workflow. Mongrel's database tunnels are per connection, and multi-hop chains belong to SSH terminal profiles rather than every database driver. Mongrel is also commercial software, so use the 7-day trial to decide whether the integrated terminal, file-transfer, and database workflows justify it.
// FAQ
Frequently asked questions.
What SSH tunnel features does Mongrel provide on Linux?
Mongrel ships a Linux x86-64 desktop package with SSH terminal profiles, local and remote port forwarding, jump-host chains, agent or key authentication, and SFTP/SCP. Supported database profiles also have per-connection SSH tunnel settings.
How do I connect PostgreSQL through a bastion without typing ssh -L?
Enable SSH Tunnel in the PostgreSQL connection and enter the bastion host, port, username, and authentication settings. Mongrel owns the tunnel lifecycle for that database profile.
Does Mongrel support ProxyJump-style chains?
Yes for SSH terminal profiles. They support ordered jump-host chains. Database connection tunnel forms generally store a single bastion configuration, so this page does not claim multi-hop support for every database driver.
Can I reuse one SSH profile across multiple database connections?
Not currently. Database SSH settings are saved per connection. Reusable SSH terminal profiles can be selected by API Client tunnel configuration, but database profiles do not use that reference today.
How does Mongrel handle SSH secrets and keys?
Passwords and encrypted-key passphrases use the operating system credential facility when available. Private keys stay in their existing files; Mongrel stores paths, and Connection Sync keeps private-key and known-hosts paths machine-local.
Related guides and comparisons
Terminal, forwarding, files, and database tunnels together.
7-day trial. Linux, macOS, Windows. No credit card.