KINGAI OS Container

Portable intelligence. Controlled authority.

Package the governed KINGAI runtime for Docker and OCI environments while keeping policy, approvals, tasks, memory, model routing and audit consistent across infrastructure.

KINGAI OS Container runtime product preview
Docker / OCI Runtime · linux/amd64 + linux/arm64Build foundation verified
Secure defaults

Portable does not mean privileged.

The normal container profile is designed to run as a non-root service, keep management local and avoid inheriting host authority by default.

Verified

Non-root runtime

The runtime uses the `_kingai` identity instead of root by default.

Verified

Unix socket

Management stays local instead of exposing a control TCP port by default.

Verified

Persistent state

Memory, tasks, approvals and audit can survive container replacement through explicit volumes.

Verified

Multi-arch

Buildx paths support linux/amd64 and linux/arm64.

Governed runtime

The same rules, wherever the container runs.

Agent intent still crosses task state, policy, approval and audit boundaries before sensitive capabilities can act.

KINGAI OS Container governed execution flow
Where it fits

Run KINGAI where packaging matters.

Cloud & CI

Reproducible KINGAI runtime services for development, integration and automation without installing a full OS image.

Homelab & private AI

Run beside local model servers and private infrastructure while keeping state and authority boundaries explicit.

Portable agent services

Carry the same task, policy, approval and audit semantics across environments.

KINGAI OS Container

Take the runtime with you, not unrestricted authority.

Official production registry publication and signing remain separate release gates.

Official registry distribution, signing and some connected runtime adapters remain in development.