An AI-native OS where intelligence can act without owning the system.
KINGAI OS connects planning, task graphs, capability policy, one-time approvals, constrained execution, persistent M0–M6 memory, model routing, audit, updates and recovery into one local-first architecture.
Good morning.
Your local intelligence runtime is healthy.
One KINGAI Core, four ways to run it.
Server, Desktop, IoT/Edge and Container share the same identity, governance, task, memory, model and audit foundations. Platform differences stay at the system, hardware and delivery layers.
Server Preview
VPS, private infrastructure, AI nodes and governed enterprise automation.
Explore Server →Desktop
The personal-computer edition for developers, creators, workstations and local models.
Explore Desktop →IoT / Edge
ARM64 and x86-64 edge foundations for gateways, robotics and offline intelligence.
Explore Edge →Container
Docker/OCI runtime for cloud, CI, homelab and portable service composition.
Explore Container →From goal to action through explicit trust boundaries.
The runtime validates plans, schedules dependency-aware steps, checks agent identity and capability policy, requests approval where required, then delegates only approved capability-specific operations to constrained executors.
Explore the trust model →No generic privileged AI shell. High-risk actions are mapped to explicit capabilities.
D5 Alpha Runtime Foundation
The source line is 0.1.0-dev. Core runtime, CodeQL, constrained ExecD tests and container build paths are under continuous verification. Production TUF keys, production Secure Boot signing, final hardware Device Packs and Stable lifecycle commitments remain release gates—not marketing claims.
Verified software foundation
Policy, approvals, task graph/scheduler, constrained execution, M0–M6 memory metadata/search, model/provider registry, update/recovery foundations and CI.
Published preview
The current public Server Developer Preview remains available for VM/infrastructure testing and predates some newer D5 source capabilities.
Stable remains gated
Signing custody, production TUF, final hardware validation, supply-chain release controls and long-term support are still required before 1.0 Stable.
Build with the source, test the preview, follow the gates.
KINGAI OS is developed openly in the source repository while the product site remains a pure static Cloudflare Pages deployment.