Help centre
Documentation for Zephyr, kstack and Standby. Everything here is written from what the software actually does — if a page claims a number, the number was measured.
What kstack is, what a node is, and the order things happen in.
Thirteen typed resources, one lifecycle, and a plan that is only a bundle of grants.
Fetch, observe, plan, validate, apply, report — and why configs are never edited in place.
How a plan becomes something a billing system can actually sell, and why a location might not qualify.
Vulnerability findings matched to what is genuinely installed, and what you can do from the finding.
Components, incidents, subscribers and the feed — on a deploy that survives what it reports on.
The two apps, the agent, and why the status page runs somewhere else.
How an alert becomes a person, and how to stop it becoming one at 3am for no reason.
What the MCP endpoint is, what a key can do, and where the boundary actually sits.
Which panels and providers are supported, and what happens on a paid invoice.
Dry-run by default, idempotent, and the one thing that cannot come across.
What Zephyr is, what it installs on, and the order to set it up in.
Cannot find it?
Ask us directly — and if the answer should have been here, it will be by the time we reply.