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

Private app names, DNS, and HTTPS

Fleet builds on top of your existing Tailscale network. Tailscale handles encrypted device-to-device connectivity; Fleet adds clean .fleet URLs, trusted HTTPS certificates, and Fleet Gate sign-in. No public Funnel or exit node is required.

One gateway, local checkouts

The first computer you set up acts as your gateway. It serves .fleet DNS, HTTPS certificates, and Fleet Gate sign-in.
Apps always run on the computer that holds their checkout, and their data stays there too. When you open an app hosted on another Fleet computer, the gateway proxies the request privately over Tailscale. Both the gateway and the app's computer need to be awake and connected to Tailscale. See multiple computers.

Restricted DNS

fleet setup prints the Tailscale IP of your gateway. In Tailscale DNS settings, add that IP as a restricted nameserver for the domain fleet:
  • Leave all other DNS rules untouched — only .fleet lookups go to Fleet.
  • Every device that opens .fleet apps must have Accept DNS enabled in Tailscale.
  • If you use a Tailscale exit node, turn on Use with exit node for the fleet nameserver. Otherwise, no exit node is needed.
The gateway answers DNS queries only for gate.fleet and your registered apps, and rejects unknown names. Both UDP and TCP port 53 must be reachable on your gateway over Tailscale. See Tailscale's DNS reference.

Private HTTPS

Every Fleet installation generates its own private certificate authority (CA) during setup. The private signing key never leaves your gateway.
Computers and phones trust only that CA's public root certificate, allowing browsers to verify per-app certificates like notes.fleet over real HTTPS with zero certificate warnings.
Because trusting a root certificate is a broad system-level trust decision, only trust a root generated by your own gateway — and never bypass browser certificate warnings to work around a setup issue.
When you run fleet phone, Fleet temporarily exposes a private setup page over Tailscale Serve at a .ts.net address on port 8444. Because Tailscale already issues a trusted certificate for .ts.net, Safari can open the setup page cleanly to download your public root profile.
That .ts.net address is used only during one-time phone setup and shuts itself off automatically once you tap Open Fleet. All of your actual apps live at https://<app>.fleet.

Check your setup

Run fleet doctor to verify Tailscale connectivity, the Fleet daemon, and local gate.fleet DNS resolution:
fleet doctor
If anything fails, head to troubleshooting.