Why Kubemoot
Where Kubemoot fits, the problems it solves, and how it differs from other approaches.
Install Kubemoot and get a crew answering questions.
New to Kubernetes, or unsure how your machines connect to the machine that runs the model? Start with How the Pieces Fit Together.
Kubemoot’s release images are amd64 only today, so the cluster needs amd64 nodes
(Intel and AMD PCs). They do not run on arm64 nodes such as a Raspberry Pi or Apple
silicon; see Install the Operator and the
Roadmap.
Where Kubemoot fits, the problems it solves, and how it differs from other approaches.
What Kubemoot is, its building blocks, and how a question becomes an answer.
Frameworks build an agent and Kubernetes runs a container, but neither operates a multi-agent AI workflow as infrastructure. That gap is Kubemoot’s lane.
One cluster, your machines as its nodes, a model server on the accelerator node, and Kubemoot finding it through a ModelServer.
Try Kubemoot on a laptop, no accelerator required, in one script.
Prerequisites and the Helm install of the Kubemoot operator; other components install separately.
The questions people ask first, answered briefly, with where to read more.
How Kubemoot relates to nearby projects: Kubernetes-native agent platforms, agent frameworks, model serving, tool gateways, memory interchange, and evaluation tools.
The major capabilities being considered, so you can see where Kubemoot is going before you judge what it lacks today.
Where “Kubemoot” comes from - a moot is an assembly that deliberates to a decision.