Run your fleet of AI agents on Kubernetes
# Install from the published Helm chart. Nothing to pin, no fork.
helm install kyber oci://ghcr.io/matty-v/charts/kyber \
--namespace kyber-system --wait
# 15 minutes from an empty cluster to a live fleet console
A real machine for every agent, not a chat window
Kyber treats agents as infrastructure: each one gets a durable, isolated environment it fully controls, and you get one console to run them all.
Long-lived, sandboxed agents
Each agent owns a whole pod with a persistent disk. Installed packages, cloned repos, credentials, and memory all survive restarts, upgrades, and preemption.
Any Kubernetes cluster
A Windows laptop, a spare box, a Mac, or any cloud. On GCP, Kyber provisions the VMs for you, preemptible instances included.
Chat from your phone
Two-way Telegram and Discord conversations with any agent in the fleet. Assign work, approve decisions, and get results without opening a terminal.
Own the whole environment
Choose each agent's machine, VM type, disk, CPU, and memory. Reboot it, stop it, or open a shell into the running agent straight from the console.
Schedules and handoffs
Cron inside each agent survives restarts. Agents send each other signed messages, so one agent's output becomes another's next prompt, and can wake it from sleep.
Your subscription, not per-token
Claude Code agents sign in with your Claude subscription, Codex agents with your ChatGPT subscription. API keys work too, but you do not need them.
From empty cluster to working fleet
Install the chart
One Helm install from the published OCI chart brings up the control plane, the console, and the API on any Kubernetes cluster, local k3d included.
Create your agents
Define each agent in the console: its runtime (Claude Code or Codex), its resources, its git-backed identity. Kyber schedules a sandboxed pod with a persistent disk.
Put them to work
Chat over Telegram or Discord, watch the fleet from the dashboard, put agents on cron schedules, and let them hand work to each other while you are away.
What people run on Kyber
Kyber is the platform layer under the agents. Here is what fleets look like in practice.
A personal agent fleet
Long-lived assistants that keep their tools, repos, and memory. Always on, on hardware you control.
Read more →An autonomous dev team
A team of agents that takes GitHub issues to reviewed, merged pull requests: planner, builders, and reviewers, each in its own pod.
Read more →Ops from your phone
Run infrastructure through a conversation: assign work from Telegram, approve decisions, and get results without opening a laptop.
Read more →Scheduled automation
Agents on cron: nightly audits, weekly reports, monitors that investigate before they page you. The schedules survive restarts.
Read more →Give your agents somewhere to live
Fifteen minutes from an empty cluster, or a k3d one-liner, to a fleet console with a live agent. No cloud account required.