Introduction
kanade — 奏 is an endpoint management system for Windows fleets. It gives an operator a single CLI / SPA to run scripts, install software, gather inventory, and stream live perf data from hundreds of PCs at once. The pieces:
| Component | What it is |
|---|---|
| kanade-agent | Service that runs on each managed PC. Subscribes to NATS, executes commands, ships results. |
| kanade-backend | HTTP API + projector. Persists state, serves the SPA, exposes operator endpoints. |
| kanade-client | Optional Tauri desktop app. End-user-facing surface. |
| NATS server | Message broker for command fan-out + result aggregation. The agent talks NATS-only; the backend reads NATS too. |
| kanade CLI | Operator-facing command line: publish binaries, fire jobs, query state. |
This site covers two audiences:
- Operators running a kanade fleet — how to update each component without ssh-ing into endpoints (see Agent-mediated updates).
- Developers writing PowerShell jobs the agent will execute — what works, what doesn't, what changed in recent agent versions (see Writing scripts for the agent).
The detailed protocol / on-wire spec lives at Spec (the legacy single-page document; will be split into chapters as the docs site fills out).