Download
Tether is freeware: free of charge for personal and commercial use, no registration. The links below always point at the current release; checksums are published next to every file.
Agent binary (Linux boxes)
One static, dependency-free binary (5 MB on disk, about 3 MB of RAM while running). Normally you don't download it by hand: the hub serves it at /dl/ and the install one-liner fetches it for you. Grab it here for air-gapped boxes, custom images or to inspect it.
| File | Architecture | Typical hardware |
|---|---|---|
| tether-x86_64 | x86_64 / amd64 | Intel & AMD servers, most VMs and NUCs |
| tether-aarch64 | aarch64 / arm64 | Raspberry Pi 4/5, Ampere, AWS Graviton |
| SHA256SUMS | checksums of all binaries (Linux and macOS) | |
curl -fsSLO /dl/tether-x86_64 && curl -fsSLO /dl/SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS
sudo install -m 0755 tether-x86_64 /usr/local/bin/tether
sudo tether install --url https://<your-hub> --token <registration-token> --name box1 --ports 22,80Later, sudo tether upgrade fetches the hub's current agent and restarts the service — no token needed. Add --auto-upgrade to let the box do that by itself every 30 minutes (see docs).
Needs systemd (Debian, Ubuntu, Fedora, RHEL/Rocky, Arch, Raspberry Pi OS, …). Macs: see below. Windows agents are not available.
Agent on a Mac (Homebrew)
A Mac becomes a box like any other: it shows up in the list, and the web terminal, HTTP ports and tether ssh reach it through the hub. macOS 11 or newer, Apple silicon or Intel. Install with Homebrew from the tap this site serves:
brew tap smtech/tether https://tether-pro.web.app/brew/tether.git
brew install smtech/tether/tether
sudo tether install --url https://<your-hub> --token <registration-token> --name mac1 --ports 22Or skip Homebrew: the install one-liner from Add box works on a Mac as well (curl -fsSL https://<your-hub>/install.sh | sudo bash -s -- --token …). Either way tether install copies the binary to /usr/local/bin/tether and starts it as a launchd daemon (ch.smtech.tether) that runs at boot without anyone logged in, as the user who ran sudo.
- SSH: turn on Remote Login in System Settings → General → Sharing (or
sudo systemsetup -setremotelogin on);tether installreminds you if it is off. - Upgrades:
sudo tether upgradeupdates the daemon's copy from your hub, like on Linux;brew upgrade tetherupdates the command on your PATH. - Status and log:
sudo launchctl print system/ch.smtech.tether,/var/log/tether.log.
| File | Mac | |
|---|---|---|
| tether-macos-aarch64 | Apple silicon | M1 and newer, macOS 11+ |
| tether-macos-x86_64 | Intel | Intel Macs, macOS 11+ |
The binaries are not notarized. Homebrew, curl and the one-liner install them without a Gatekeeper prompt; a copy downloaded with a browser needs xattr -d com.apple.quarantine tether-macos-* first.
Helm chart (hub on Kubernetes)
The chart pulls gocarlos/tether-hub from Docker Hub and deploys the hub with a persistent SQLite volume, a Secret for the admin login and JWT key, a Service and an Ingress with the WebSocket timeouts the agents need.
| tether-hub-chart.tgz | packaged Helm chart, current release |
helm upgrade --install tether ./tether-hub-chart.tgz --namespace tether --create-namespace \
--set publicUrl=https://tether.example.com \
--set ingress.host=tether.example.com \
--set secrets.jwtSecret="$(openssl rand -hex 32)" \
--set secrets.adminEmail=you@example.com \
--set secrets.adminPassword='change-me-now' \
--set secrets.registrationToken="tether_reg_$(openssl rand -hex 32)"All values are documented in the chart's values.yaml. Point secrets.existingSecret at your own Secret (keys TETHER_JWT_SECRET, TETHER_ADMIN_EMAIL, TETHER_ADMIN_PASSWORD, TETHER_REGISTRATION_TOKEN) if you manage secrets elsewhere. Then open the URL, log in and continue in the docs.
Docker image (hub)
The hub ships as one image on Docker Hub: hub, web app and both agent binaries (served at /dl/ for the install one-liner). Pull it from gocarlos/tether-hub; for air-gapped clusters there is an archive to docker load.
docker pull gocarlos/tether-hub:2026.11.16-095bdc6 | linux/amd64, also tagged latest |
| tether-hub-image.tar.gz | same image as an archive for offline use (docker load -i) |
Releases are named after the commit they are built from: YYYY.MM.DD-<commit>, the commit's date (UTC) and its short hash, for example 2026.10.18-873b4b4. Hub image, chart and agents of one release carry the same name, and tether --version prints it. A later date is a newer release.
Run it standalone (no Kubernetes)
docker run -d --name tether -p 8080:8080 -v tether-data:/data \
-e TETHER_PUBLIC_URL=https://tether.example.com \
-e TETHER_JWT_SECRET="$(openssl rand -hex 32)" \
-e TETHER_ADMIN_EMAIL=you@example.com -e TETHER_ADMIN_PASSWORD='change-me-now' \
gocarlos/tether-hub:2026.11.16-095bdc6Use your own registry
Clusters that only pull from an internal registry (or air-gapped ones) mirror the image and point the chart at it:
docker pull gocarlos/tether-hub:2026.11.16-095bdc6 # or: docker load -i tether-hub-image.tar.gz
docker tag gocarlos/tether-hub:2026.11.16-095bdc6 registry.example.com/tether-hub:2026.11.16-095bdc6
docker push registry.example.com/tether-hub:2026.11.16-095bdc6
helm upgrade --install tether ./tether-hub-chart.tgz -n tether --create-namespace \
--set image.repository=registry.example.com/tether-hub --set image.tag=2026.11.16-095bdc6 \
--set imagePullSecrets[0].name=my-registry-credentials -f my-values.yamlUpdating: pull the new tag and bump image.tag. The hub keeps its data in the persistent volume; agents reconnect on their own.
Operator CLI (your laptop)
The agent binary is also the operator CLI. On a Mac, brew install smtech/tether/tether (see above) is all you need — no service unless you run tether install. On Linux use the binary above.
tether login --url https://<your-hub> --email you@example.com
tether ssh admin@box1