Weave Fleet

Installable local Fleet server builds are published through GitHub Releases.

Install

macOS / Linux (linux-x64, osx-arm64)

curl -fsSL https://github.com/pgermishuys/weave-fleet/releases/latest/download/install.sh | sh
export PATH="$HOME/.weave/fleet/bin:$PATH"
fleet version

Windows PowerShell (win-x64, win-arm64)

irm https://github.com/pgermishuys/weave-fleet/releases/latest/download/install.ps1 | iex
fleet version

Desktop app

The newest installer for each platform:

• macOS (Apple Silicon): https://github.com/pgermishuys/weave-fleet/releases/latest/download/Fleet-mac-arm64.dmg
• Windows x64: https://github.com/pgermishuys/weave-fleet/releases/latest/download/Fleet-win-x64-setup.exe
• Windows arm64: https://github.com/pgermishuys/weave-fleet/releases/latest/download/Fleet-win-arm64-setup.exe
• Linux AppImage: https://github.com/pgermishuys/weave-fleet/releases/latest/download/Fleet-linux-x86_64.AppImage
• Linux .deb: https://github.com/pgermishuys/weave-fleet/releases/latest/download/Fleet-linux-amd64.deb

The installers aren't signed yet; RELEASE.md says how to open them.

Run

fleet

Default URL:

• http://127.0.0.1:6262

Health check:

curl -fsS http://127.0.0.1:6262/healthz

From another device

fleet --host 0.0.0.0 listens on every address, so you can open Fleet from another machine on your network. Fleet then asks every request for its access token, its own machine's included; open the /login?token=… link it prints once.

Another Fleet can add this one as a machine (Settings → Machines) and work in its sessions. Behind tailscale serve or another reverse proxy, keep Fleet on loopback and start it with --require-token. See docs/machines.md, and docs/phone.md for Fleet on your phone.

App previews in the Browser tab follow Fleet: each preview gets its own port on the address Fleet listens on. With --host 0.0.0.0, anyone who can reach this machine can open a running preview without signing in to Fleet, so only do this on a network you trust. The app itself stays on localhost. To let previews through a firewall, give them a fixed range with Fleet__Browser__PortRange=41000-41099.

As a node, without the web app

fleet node --host 0.0.0.0 starts the same Fleet without its web app, and asks every request for the access token. It prints its addresses and token; add it from another Fleet under Settings → Machines. See Run a node without the web UI.

fleet node install-service keeps it running when you log in and after a crash: a systemd user service on Linux, a LaunchAgent on macOS, a scheduled task on Windows. See Keep a node running.

Common commands

• fleet node
• fleet node install-service / fleet node uninstall-service
• fleet version
• fleet update
• fleet uninstall

Supported release artifacts

• linux-x64
• osx-arm64
• win-x64
• win-arm64

Releasing

Release workflow details live in RELEASE.md.