From first launch to a full cockpit

Install it and open it

Download the signed installer for macOS or Windows. With nothing configured, the cockpit already shows:

• this machine: per-core CPU, memory, disk and network, GPU and battery;
• your local docker, podman or tart containers;
• your Claude Code token usage, read from the logs on your disk;
• the status pages of the vendors it can see you use, starting with Anthropic once those logs exist.

Connect GitHub optional

For the Repos and Runners panels, create a fine-grained personal access token. Solador never writes to GitHub, so everything is read-only:

• Repository permissions: Actions, Contents, Issues and Pull requests (Metadata comes with them).
• Organization permissions: Self-hosted runners, for the Runners panel, and Projects, for the Repos panel's Ready column.
• Everything else stays at No access.

Then in Solador: Settings → Connections → Add connection → GitHub. Name the account, paste the token into Fine-grained PAT and choose Add Account. On the account's card, Configure repos… picks the repositories to watch, and Runner organizations takes the orgs whose runners you want.

The full walkthrough, with what each permission feeds: docs/github-setup.md.

Add your other machines optional

Another machine (a Linux server, a second Mac) shows up in your cockpit by running the agent. It runs as your user, with no sudo, on Linux with systemd or macOS 11 and later. It needs minisign to check the release's signature: brew install minisign, apt install minisign (Debian 12+, Ubuntu 24.04+) or dnf install minisign.

On the host:

curl -fsSLo bootstrap.sh https://raw.githubusercontent.com/Sassy-Dog/solador/main/agent/deploy/bootstrap.sh
bash bootstrap.sh

It fetches the installer from main, verifies the agent binary's signature before anything runs, installs it, and asks for a bearer token (press Enter to generate one). It finishes by printing the agent's certificate fingerprint. Two steps rather than a curl | sh, deliberately, so you can read what you run.

Then in Solador: Settings → Connections → Add connection → Remote host. Enter a name, the host's address and the token, then Check certificate. Compare the fingerprint it shows with the one the installer printed, choose Trust, and Add Host.

Any network path works: a LAN, a VPN, Tailscale, an SSH tunnel. A paired host is reached over TLS pinned to the certificate you approved, and Solador never sends the token over plain HTTP anywhere but loopback or Tailscale. A fresh install serves TLS, and on a machine without Tailscale it listens on all interfaces, behind TLS and the token: firewall its port on a machine with a public address. The agent reference covers binding, updates, unattended updates and uninstalling.

Connect the rest optional

Each is independent, under Settings → Connections → Add connection:

• Neon: an organization API key, for compute, storage and estimated charges.
• Sentry: an org:read token and your org slug. One credential feeds both Usage and Sentry Crons.
• Vercel: a token, for month-to-date spend from the billing export.
• Azure Cost: a daily cost export in blob storage. Nothing to paste: each read is signed by the az CLI you are already signed in to.
• OpenClaw: your gateway's URL. Solador shows the command that approves this device on the gateway, then follows it over a live WebSocket.
• Status page: any Atlassian Statuspage you depend on, watched beside the built-in vendors.

Credentials go to your OS credential store (Keychain on macOS, Credential Manager on Windows), never the settings file.

Make it yours

Edit dashboard moves, hides, duplicates and scopes the overview's tiles. Settings → Detailed layout arranges the full cockpit per window width. Then put it on your second monitor and leave it open.

Doesn't fit your stack? Start a discussion or open an issue.