Practical Secure Pipes use cases
Choose a setup by the task you want to complete, then follow the detailed guide for its fields and safety checks.
Reach a remote PostgreSQL database
Goal: use a database client on your Mac without opening the database's port to the public internet.
Create a local forward: Mac listener 127.0.0.1:15432, remote target 127.0.0.1:5432, over your real SSH server. Connect the profile, then point the database client at 127.0.0.1:15432 using the database's own credentials.
If PostgreSQL runs on another machine in the server's private network, use that private hostname/address as the remote target. The SSH server must be allowed to reach it.
Reach several internal services through one profile
Create the first local mapping, then open Manage Port Forwarding… and add an internal web service as a second row. Use different local listener ports, enter purpose labels and save both the table and profile.
The rows share SSH settings and stop together. They are TCP/Unix-target mappings, not general UDP forwarding. Multi-port forwarding requires Pro after the shared trial.
Preview a local web application from an SSH server
Run the web app locally on 127.0.0.1:3000, then create a remote forward with server listener 127.0.0.1:18080. From the SSH server, visit its forwarded port.
This setup is loopback-only. To allow other remote clients, review server GatewayPorts policy, authentication and firewall restrictions with the administrator before exposing it.
Send one browser through a proxy
For a proxy-aware browser/client, create a SOCKS profile on 127.0.0.1:1080 and configure that client to use it, including proxy-side DNS when supported.
For application-based routing, configure an upstream server under Proxy, create a This Mac rule for the chosen browser, select the proxy action and start the transparent proxy. Check the matched rule in active connections instead of assuming the browser used the proxy.
Share routing with a phone
Start transparent proxying and Network Sharing. Enter the Mac's selected LAN address and sharing port in the phone's manual Wi-Fi HTTP proxy settings. Keep authentication enabled and use a trusted network.
To route that phone differently from your Mac, create a LAN Devices rule using its source IP. Apps that ignore manual proxy settings are outside this setup's scope.
Reach an internal service through jump hosts
Create a local-forward profile whose final SSH server can reach portal.internal.example:8080. Add the intermediate servers under Jump Hosts in the required order, then map Mac 127.0.0.1:18080 to that internal target. After the SSH connection succeeds, open http://127.0.0.1:18080 on the Mac. Each hop must permit the next; the internal service need not have a public listener. Sequential jump hosts require Pro access or an active trial. See SSH hosts and authentication.
Maintain an internal Windows desktop
Through an SSH server that can reach the Windows machine, create a local forward from Mac 127.0.0.1:13389 to the machine's private address, for example 192.168.10.25:3389. In Windows App on the Mac, connect to 127.0.0.1:13389. Windows sign-in and Remote Desktop permissions still apply; verify the target before working and stop the SSH forward afterward. The Windows RDP port does not need to be open to the public internet. See local forwarding.
Work in a temporary staging environment
Put the staging local-forward, remote-forward and SOCKS profiles you need in a connection group. Choose concurrent startup or an explicit order and failure policy, then start the group from the app's group controls. Check each member's connection state before using the environment, and disconnect the members when the work is done. A group coordinates startup; it does not grant access or set an automatic expiry.
Switch routing between office and home
Create named Office and Home usage scenarios and assign the relevant rules and quick app assignments to each. Select the scenario manually before starting work. Switching disconnects existing proxy connections so new connections use the selected rules; save work first and verify the scenario and route in active proxy connections afterward. Wi-Fi changes do not switch scenarios automatically.
Route a work application through a chosen proxy
In Proxy → Applications, find the work app and assign a proxy server. Limit the assignment to selected scenarios if it should apply only in one environment, then start the transparent proxy. Make a request in that app and inspect its matched proxy in active proxy connections. A saved assignment alone does not prove that the app's traffic used the proxy.
Inspect server logs and deliver files
Open a saved host's Console or SFTP. In Console, inspect only logs your SSH account is authorized to read; in SFTP, download a diagnostic file or upload a prepared file to the intended folder. Check the target path, account permissions and final transfer state. SFTP runs over SSH and does not require opening another file-transfer port.
Move settings to a new installation
For your own full configuration, export an encrypted backup, retain its password and separately preserve private-key files. Restore and inspect settings before connecting.
For selected connection settings, generate a share QR code, use a short validity and send its password separately. The recipient configures their own credentials and verifies server trust.
Protect an operations Mac with app unlocking
On a Mac used to manage servers, open General → Security and set a master password first. Choose an automatic lock interval and, if needed, require authentication before opening Console/SFTP. Use Lock Now to check that you can unlock the app with your chosen method.
On a compatible Mac, Touch ID can be enabled as another unlock method. App OTP setup requires Pro access or an active trial; keep its recovery codes somewhere safe. Master password, Touch ID and app OTP are selectable unlock methods, not three checks required in sequence. Locking the interface does not disconnect running tunnels or replace SSH authentication or an SSH server's OTP. See Security and preferences.
Let a remote server use your Mac’s proxy
Method 1: Forward the HTTP sharing proxy
Goal: your Mac can reach the internet and can initiate SSH to a server that needs access. Start the Mac’s HTTP network-sharing proxy on loopback at 127.0.0.1:10791. Create a Remote Forward using that server as the SSH destination, with local target 127.0.0.1:10791 and remote listener 127.0.0.1:10791. Your Mac initiates SSH; the remote server then reaches the Mac’s proxy through its own loopback port.
Run the following on the remote server, not on the Mac. The variables apply only to this npm command; they do not change the server’s default gateway or the existing SSH connection. Only applications honoring these settings use the proxy.
http_proxy=http://127.0.0.1:10791 https_proxy=http://127.0.0.1:10791 npm install
If proxy authentication is enabled, configure the required credentials securely in the client; the credential-free example alone will not authenticate. A tunnel or proxy outage can make proxied commands fail, but does not by itself remove the server’s direct network route. Do not expose the remote proxy listener publicly. Stop the remote forward when finished.
Method 2: Reverse SOCKS proxy
Create a Remote Forward to the same SSH server. In its mapping, choose Reverse SOCKS as the local endpoint, keep the remote listener at 127.0.0.1 and use port 10793. Save and connect. The server gets a SOCKS5 listener; your Mac opens each requested TCP destination through its own network connection. This method does not require the HTTP sharing proxy above.
Run this test on the SSH server while the connection is active:
curl --proxy 'socks5h://127.0.0.1:10793' https://example.com/
The socks5h scheme sends the hostname through SOCKS for resolution on the Mac. Configure only SOCKS-aware server applications to use this listener; it does not change the server’s default gateway. Reverse SOCKS currently supports TCP only and has no authentication. Keep the listener on server loopback and stop the SSH connection when finished.
Based on Secure Pipes 2.0.16 · Updated November 3, 2026