Add a device as a node
Downloads come straight from this hub’s current stable release. During the private beta you also need an account or a pairing code from the hub’s operator.
Android phones and TVs
The node app is not on the Play Store. It needs Android 11 or newer; there is no iOS version. Pick the build for your device:
| File | For |
|---|---|
| Phones and tablets (litert2 APK) | GPU and NPU through LiteRT. The right choice for most phones. |
| TVs and older devices (nnapi APK) | Uses Android’s NNAPI, for TVs and 32-bit devices. |
Android will ask you to allow installs from your browser, and Google Play Protect may warn about an app it does not know. That is expected for an app installed outside the Play Store; check the download first (below) if you want to be sure it is the published file.
Then pair it: scan the QR code or enter the pairing code from the hub’s dashboard (Add nodes in the docs).
Linux machines
amd64 or arm64, installed as your own user (never root). One command installs and pairs with this hub:
curl -fsSL https://ai.baseira.casa/install.sh | shThe script checks every file it downloads against the release’s signed checksums before installing. It prints a code such as K7TQ-3MZA; the hub’s operator approves it on the dashboard. Prefer to read the script first? curl -fsSL https://ai.baseira.casa/install.sh -o install.sh, read it, then sh install.sh.
Chat models: install llama.cpp, then kinherd-node up finds your GGUF models and adds them.
On a Mac, or with a binary you built
Three commands: kinherd-node pair, kinherd-node install, kinherd-node up(Add nodes). This is what they print:
$ kinherd-node pair ai.baseira.casa
Approve this device on the hub:
code K7TQ-3MZA
at https://ai.baseira.casa/admin/pair
The hub will show: Intel NUC11, x86_64, Ubuntu 24.04, 15872 MB RAM
Waiting (expires in 15 min; Ctrl-C to stop)…
Paired with home-hub as "nuc" (wss://ai.baseira.casa/v1/nodes/connect). Token saved to /home/me/.config/aigw-node/credentials.json (mode 600).
Trusting publisher key(s) 9f5f41fe560113f7; recipes are applied automatically.
Next: kinherd-node install (the service; or: kinherd-node run) then kinherd-node up (chat models, wait until online)
$ kinherd-node install
wrote /home/me/.config/systemd/user/kinherd-node.service
started; `kinherd-node status` shows what it does, `journalctl --user -u kinherd-node -f` its log.
To keep it running while you are logged out (headless boxes): loginctl enable-linger $USER
$ kinherd-node up --yes
backed up config.json to /home/me/.config/aigw-node/config.json.bak-20261120T101502Z
added chat model "qwen2.5-1.5b-instruct-q4_k_m": /home/me/models/qwen2.5-1.5b-instruct-q4_k_m.gguf (llama-server /usr/local/bin/llama-server, context 8192, 1 slot(s), ~2986 MB)
edit ~/.config/aigw-node/config.json "llm" to change them (docs/LLM.md)
waiting for home-hub to report the node online (up to 5m0s; Ctrl-C stops waiting, the node keeps running)…
connecting to the hub…
online; loading [qwen2.5-1.5b-instruct-q4_k_m]…
Online: home-hub has node "nuc".
Serving: efficientnet-lite4-int8, qwen2.5-1.5b-instruct-q4_k_m
Verify a download
Every release has a SHA256SUMS file and its detached signature SHA256SUMS.sig, made with the publisher’s key. Check a file against the sums:
mkdir aigw-check && cd aigw-check
for f in SHA256SUMS SHA256SUMS.sig app-litert2-release.apk; do
curl -fsSLO "https://ai.baseira.casa/downloads/latest/$f"
done
sed -n 2p SHA256SUMS.sig # the release these files belong to
sha256sum --ignore-missing -c SHA256SUMS # app-litert2-release.apk: OKLinks: SHA256SUMS, SHA256SUMS.sig. To check the signature itself with openssl and the publisher key, follow “Checking install.sh before running it” in docs/UPDATES.md. Installed nodes verify every update against the signed release manifest on their own.