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

A private home for personal apps

Fleet turns your own computers into a private home for personal apps. Your coding agent edits the files, Fleet builds and updates the app automatically, and every device on your Tailscale network can open it at a short address like https://notes.fleet.
Your code and data never leave the computer where you created the app. Tailscale connects your devices privately; Fleet adds .fleet addresses, HTTPS certificates, sign-in through Fleet Gate, persistent storage, and background jobs.
Install Fleet and build an app
Install Fleet in one command and open a working notes app in minutes.
Explore the app format
A Preact frontend, typed server operations, static assets, and SQLite-backed JSON data.

How the pieces fit together

App checkouts live as ordinary folders on your computer. Each folder holds a Preact client, server operations, a fleet.json manifest, and an AGENTS.md guide for your coding agent. When you or your agent save a file, Fleet rebuilds automatically — no separate dev server or deploy step.
The Fleet runtime runs on Bun in the background. It watches your checkouts, caches built frontends, starts app workers on demand, and unloads idle workers after 30 seconds so unused apps do not waste memory. If a build fails, Fleet keeps the last working version live and records the error in fleet logs.
Your gateway is the first computer you set up with Fleet. It answers .fleet DNS lookups, issues private HTTPS certificates, signs devices in through Fleet Gate, and routes requests to whichever computer owns the app.
Your Tailscale network privately links your computers and phones. One restricted DNS rule tells Tailscale to send .fleet lookups to your gateway, and every new app works automatically under that same rule.

What Fleet is (and isn't)

Fleet is built for trusted personal apps on computers you own:
  • Private by default — no public URLs, guest links, or hosted cloud relay.
  • Trusted code — apps run under your operating-system user account, not an untrusted-code sandbox.
  • Stays where you build it — each app and its database stay on the computer with its checkout. That computer (and your gateway) need to be awake to open the app or run scheduled jobs.
  • Simple backups — a failed build won't break a running app, but a compiling edit can still change data, so Fleet includes one-command SQLite snapshots.
Ready to try it? Start with the quickstart, then read the agent workflow guide.