Release status
Review the unified public release policy and product-scoped release truth.
KINGAI OPS / Public Beta
Evaluate from verified release truth.
Customer-facing installers are published only after a customer-safe artifact passes the release gate. Private production repositories and legacy repositories are not public installation channels.
Public Beta Evaluation PathIllustrated walkthrough
Release gate
Check the public release hub before installing anything.
A product-scoped KINGAI OPS Current / Verified record is the authority for downloadable customer builds. If that record is absent, do not substitute a private repository URL, legacy repository or guessed raw installer path.
Safe default: no private-source installer is published on this page. The public release hub is the only GitHub surface linked for customer release status.
Evaluation access
When no verified customer build is published, request the supported evaluation path directly from KINGAI.
Local-first safety
Verified releases should keep management private by default and document safe local or SSH-tunneled access.
Compatibility
Target coverage is broad; verified compatibility is release-specific.
The platform targets major Linux package-manager families and multiple architectures. Treat the compatibility matrix attached to a verified release as authoritative for installation support.
Debian / Ubuntu
apt-family target.
Fedora / RHEL / Rocky / Alma
dnf/yum-family target.
openSUSE / SUSE
zypper-family target.
Arch / Manjaro
pacman-family target.
Alpine
apk-family target.
Void Linux
xbps-family target.
Init systems
systemd, OpenRC, runit and manual fallback are product targets.
Architectures
Release notes define the architectures verified for each customer build.