Introduction to ShellHub

ShellHub is access infrastructure for connected devices. Reach any device from any network, and everything you run on it.

You install a small agent on a device, the agent dials out to the ShellHub server, and from then on that device — and the things running on it — are available to you through a single address. Access is granted to an identity, a person or an automation, rather than to a credential anyone could hold.

There is no inbound port to open and no public IP to arrange. The device makes the connection, so it works from a customer’s network, a factory floor, or a cellular link just as well as from a rack you own. Once it is connected you can open a terminal, move files, forward a port, step into a container, or publish an HTTP service it is running.

It takes a single command on the device to get there.

Guides

• Quickstart — Reach your first device, and let your team reach it.
• Self-Host ShellHub — Run your own server with Docker Compose.
• How Authorization Works — Decide who may reach which device, as which login.
• Add People to Your Namespace — Invite members and give them roles.
• Connect to a Device — The web terminal, native SSH, and the SSHID.
• Port Forwarding — Reach a service on the device or on its network.
• Provisioning Keys — Enroll devices at scale without a manual step.
• MCP Server — Let an AI assistant operate your fleet.

About ShellHub

• How ShellHub Works — Concepts, architecture, and the path a connection takes.
• ShellHub vs. Jump Hosts and VPNs — How this differs from what you have now.
• Self-Hosted vs. Cloud — Compare the deployments and decide which fits.
• Editions — What Community, Cloud, and Enterprise each include.