ShellYard
Last reviewed against v0.9.0 source: app_http_tunnel.go

SSH-tunnel routing

The differentiator. Set 'Route via' on a saved request to a saved SSH connection ID; the call flows through that session.

Set Route via on a saved request — or environment, or a whole collection — to a saved SSH connection ID. ShellYard opens a session against that host and forwards the HTTP request through it, hitting whatever’s reachable from the SSH server’s network:

  • A controller management VLAN
  • A private VPC subnet
  • A localhost-only admin port

Works for REST, GraphQL, and the collection runner. The tunneled session reuses the SSH manager so a single connection is shared across requests.

Why this is different from a manual port forward

  • No -L flags to remember.
  • No port collisions on your machine.
  • The route lives on the saved request, so collaborators get it via reverse export.
  • Multiple requests can share one tunnel; opening the SSH session once is enough.