// the find
shellhub-io/shellhub
:computer: Get seamless remote access to any Linux device. Centralized SSH for the edge and cloud computing
ShellHub is a self-hostable SSH gateway that proxies connections to Linux devices through a central server, so you can reach anything on your fleet without public IPs, VPN changes, or jump hosts. It's aimed at IoT/edge fleets and teams managing many servers who want audit logs, session recording, and firewall rules in one place. There's also a hosted cloud option if you don't want to run the infrastructure yourself.
The agent is a single Go binary that phones home to your gateway — no inbound ports needed on managed devices, which makes it genuinely useful for devices behind NAT or in restricted networks. Session recording with in-browser replay is a real differentiator over raw SSH setups; most teams bolt this on with asciinema hacks. The store layer is properly abstracted with a test suite that runs against real Postgres (storetest package with fixture YAML), not mocks — that's a sign of a codebase that takes correctness seriously. Native SCP/SFTP and port forwarding work through the same tunnel without extra configuration, so you're not losing standard tooling when you go through the gateway.
2031 stars after what looks like several years of work is a modest number for a tool in this space — Teleport and Boundary have mindshare and enterprise backing; ShellHub is playing catch-up with fewer resources. The codebase is a Go monorepo with separate go.mod per service (agent, api, cli all independent), which means dependency drift between services is a real maintenance burden and you'll hit version skew bugs. The self-hosted deployment story requires running the full Docker Compose stack with multiple services, which is heavier than alternatives for small teams just wanting secure SSH to a handful of boxes. MCP route (`api/routes/mcp.go`) appeared recently with no context in the README — it's unclear what it does or whether it's stable, which is a yellow flag for adopters.