Secure, Persistent Access with Hashicorp Boundary and Tmux

Hashicorp Boundary changes that. It lets you control and audit secure access to systems without exposing network paths. No VPNs to manage. No IP allowlists to update. Users authenticate to Boundary, then connect to targets through authorized sessions. Every step is logged. Every session has clear context.

Tmux takes those sessions and makes them powerful. With Tmux you can split terminals, detach, and resume work without losing state. When combined with Boundary, you get secure, persistent, multiplexed access to infrastructure from anywhere. Even over unstable networks, running long tasks or monitoring pipelines becomes reliable.

Start by installing the Boundary CLI and authenticating against your Boundary controller. Use boundary authenticate with your credentials or tokens. Identify your target with boundary targets list. Then use boundary connect ssh (or another protocol you’ve configured) to launch your secure session.

Now launch Tmux inside that session. For example:

tmux new -s prod-access

You can split panes with Ctrl+b % or Ctrl+b " and create windows with Ctrl+b c. All of it stays inside a single secured Boundary session, isolated from the open internet and fully auditable. You can detach with Ctrl+b d and reconnect later with:

tmux attach -t prod-access

If the SSH session drops, Boundary reconnects and Tmux preserves your work.

The combination of Hashicorp Boundary and Tmux is minimal, secure, and fast. You control who gets in, what they can reach, and every action they take, while keeping your workflow efficient and recoverable.

See how Boundary with Tmux works in a real environment. Visit hoop.dev to try it live in minutes.