Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Run apps on another computer

One computer acts as your Fleet gateway for DNS, HTTPS, and Gate sign-in. You can join any number of additional computers to host app checkouts — Fleet automatically routes requests for those apps through your gateway over Tailscale.
Apps and their SQLite databases stay on the computer where you created them.

Before you join

  • Install Fleet on the second computer and connect it to the same Tailscale network.
  • Keep your gateway awake and reachable.
  • Make sure your tailnet policy allows your gateway to reach the new computer on TCP port 42174 (Fleet does not modify tailnet ACLs).
  • App names must be unique across your entire Fleet.

1. Create a one-time invitation on your gateway

fleet invite --output computer-invite.json
This file enrolls one computer and expires after 10 minutes. Copy it privately to the other computer (never commit it to Git or share it publicly).

2. Join and create an app on the second computer

fleet setup --join computer-invite.json --install fleet init another-app
During enrollment, the new computer pins your gateway's root certificate, and the gateway pins the new computer's certificate and verifies its private listener on port 42174. Delete the temporary computer-invite.json copies once enrollment completes.

Where to run commands

  • On the gateway: fleet open, fleet gate, fleet phone, and fleet invite.
  • On the app's checkout computer: fleet init, fleet inspect, fleet logs, fleet call, fleet backup, and fleet restore.
fleet list --json fleet inspect another-app fleet logs another-app
Keep in mind that joining a computer is for routing, not replication: if a checkout computer sleeps or disconnects, its apps and scheduled jobs pause until it wakes up.