Install and releases

Install locally. Run locally. Keep the operator surface local.

The canonical public path is a one-line installer. Tagged GitHub Releases remain the source of truth for platform archives and checksums.

Canonical install path curl -fsSL https://heiwa.ltd/install | sh

Open Releases Install Docs

macOS (Apple Silicon) heiwa-<version>-macos-aarch64.tar.gz

Tagged release archive built by the release workflow for aarch64-apple-darwin.

Linux x86_64 heiwa-<version>-linux-x86_64.tar.gz

Tagged release archive built by the release workflow for x86_64-unknown-linux-gnu.

Windows x86_64 heiwa-<version>-windows-x86_64.zip

Tagged release archive built by the release workflow for x86_64-pc-windows-msvc.

Checksums heiwa-<version>-checksums.txt

Published beside the release archives so installs can be verified and mirrored cleanly.

First run

1. Bootstrap

Run the install path or unpack a tagged release. The runtime writes its local state under ~/.heiwa/.

2. Verify

Run heiwa doctor to confirm local runtimes and provider CLIs are discoverable.

3. Open the local app

Run heiwa app when the local operator app lands. The web surface belongs on localhost, not a hosted dashboard.

Source of truth

GitHub Releases stay authoritative.

The installer is a convenience path. Tagged GitHub Releases are where archives, checksums, release notes, and platform build outputs live.

Public site Delivery and docs

heiwa.ltd exists to deliver software, docs, and identity exchange. It does not execute operator work.

Operator machine Runtime and data

The runtime, app, memory, and provider secrets live where the operator hosts them.