Your cluster
Specialized agents on your Kubernetes.
Nested deploys coding agents into the Kubernetes you already run. Packs, tasks, and connectors stay inside that boundary. Nothing about your code has to live on a vendor cloud.
The whole platform, inside your boundary.
One control plane, three surfaces — all installed into the Kubernetes you already operate.
The app
Talk to agents like you talk to your team.
The Nested app is chat-first: assign a task to a specialized agent, watch it work in durable threads, and pick the conversation back up days later. Knowledge centers give every agent your docs, your runbooks, your conventions.
The console
Operate the catalog from one console.
Operators register clusters, publish the agent catalog, and manage packs — skills, subagents, formulas, and MCP servers — from a single ops console. Helm stays the source of truth; the console is its face.
The runtime
Agents run as deployments in your cluster.
Every agent is a cloud-agent deployment next to your own workloads. The control plane, queue, and datastores install into the same boundary — so prompts, code context, and connector tokens never leave it.
How it works
01
Register the cluster
Point Nested at a kubeconfig you control. The control plane and platform services install there.
02
Attach packs
Give each agent the skills, subagents, formulas, and MCP servers it needs — GitHub, Slack, docs, the debugger, and the rest.
03
Talk to the agents
People work from the Nested app. Operators keep the catalog and Helm in the console. Agents run as deployments in your cluster.
Privacy
Data stays in your cluster.
Your prompts, repo context, and connector tokens stay on the cluster you host. Read the policy.
Privacy policyPut agents on your cluster.
Register a cluster, attach packs, and talk to your first agent — inside your own boundary.