Install
Homebrew today, installers for every platform from the download feed — and an optional login daemon that watches while the app is closed.
Moonway needs exactly two things: a kubeconfig with the contexts you care about, and a Kubernetes version from the last few years — every minor from 1.28 to 1.36 is exercised in CI on real clusters. There is no account to create; the free tier is just what the app is until you add a license key.
brew install --cask moonwayio/tap/moonwayHomebrew tracks the stable channel and updates with brew upgrade. Prefer
a plain download? The DMG on the homepage is the same build.
Until the first tagged release
Homebrew works today. The DMG, AppImage, deb and Windows installer are published by the release pipeline and appear on the download feed the moment the first release is cut.
What gets installed
The app bundle, and inside it the daemon binary, moonwayd. When you open the
app it starts its own daemon on 127.0.0.1, mints a random token for it, and
everything else — cache, engines, journal — happens inside that one process.
Nothing is installed into any cluster, and nothing runs as root.
Start at login (optional)
Settings → Start at login installs a supervisor artifact so moonwayd
runs from the moment you sign in — same journal, same watched clusters, same
guard state as the daemon the app was running. That's what keeps
alerts and the
change journal alive with the app closed.
| Platform | Artifact | Daemon log |
|---|---|---|
| macOS | ~/Library/LaunchAgents/com.moonway.moonwayd.plist | ~/Library/Logs/moonwayd.log |
| Linux | ~/.config/systemd/user/moonwayd.service | ~/.local/state/moonway/moonwayd.log |
| Windows | HKCU …\CurrentVersion\Run registry entry | %USERPROFILE%\AppData\Local\Moonway\moonwayd.log |
The log is size-capped and rotated by the daemon itself, and the artifact is removed cleanly by turning the toggle off — or by uninstalling.
Next: your first incident.